Best practices for connector migration

Best practices for the most optimal performance and minimal down-time of your applications, directories while performing the connector migration.

  1. If your organization has few applications (for example, less than ten) and not many connectors (for example, less than three), you can use the manual process for connector migration.
  2. If your organization has many applications and connectors, you can adopt the EAA connector migration using python script. Connector update for each directory should be done manually.
  3. Install the new connectors prior to the maintenance window and make sure they are deployed successfully. You should see this message on the EAA management portal for the connector running successfully:
  4. If you plan to adopt the EAA connector migration using python script ensure that all the prerequisites are met, EAA SDK setup is working prior to the maintenance window.
  5. For the most optimal performance keep your existing connectors currently running. First add the new connectors to the applications. Next add the new connectors to directories. If both of these are working fine then remove the old connectors. This ensures the least service disruption. After monitoring this for a few days, remove the old connectors. Consider migration scenarios described below and adopt a similar process.
  6. Plan on a maintenance window for the connector migration. Running the connector migration script takes about 5 minutes to migrate a batch of ten applications. If you are doing it manually, deployment of the application takes about 3 to 5 minutes. Also account for the time to test each application after the migration. Updating the directories with the new connector takes about 3 minutes. Depending on the number of applications, number of connectors, number of directories, and testing time, your down-time will be different.
  7. Distribute applications evenly between connectors to provide uniform load.
  8. Set up redundancy for the applications by having more than one connector to ensure load balancing and high availability.
  9. Install additional connectors based on the number of applications and load on existing connectors. For optimal performance, follow the guideline of hundred applications per connector with an additional connector for high availability.
  10. If the applications are connected to more than one connector, for redundancy, and you have resource limitations, then install the first new connector, assign the new connector to all applications, and deploy all applications. Make sure it works. Then delete the old connector. Repeat this process for the next connector. See Migration Scenario 2.
  11. If you have resource limitations and cannot install more than one connector, you will experience a down-time if the connector is removed before installing the new connector. The application and directory associated with the old connector will not work till re-deployed after the new connector installation. If you are not sure, Contact support for further assistance.
  12. When you use the EAA Application Connector Toolbox, to assign connector to applications, or remove connector from applications, limit it to a maximum of fifty applications.
  13. When you use the EAA Application Connector Toolbox, if you accidentally assigned the wrong connector to the application and exited out of the toolbox, then relaunch it, and revert your changes by removing the wrong connector and assigning the correct one.
  14. While migrating from old to new connectors, after deploying the applications on the new connector, if the old connector is removed while it is still serving requests, users may experience a short disruption. They may need to re-login the application or refresh the browser page.
  15. After you are finished with connector migration, if you do not plan to use the EAA-SDK, you must delete the api keys. Leaving the keys on a shared machine, provides access to other users to EAA-SDK.
Migration Scenario 1 : No resource restrictions in production environment.

You have three applications app1, app2 and app3 currently assigned to connectorA and connectorB. You have two applications app4 and app5 currently assigned to connectorC. You have two directories directory1 and directory2 currently assigned to connectorA and connectorB.

Assuming that you do not have any resource restrictions and can add any number of connectors in your production environment. The most optimal migration method for this scenario is:
  1. Install three new connectors: connectorA1, connectorB1 and connectorC1.
  2. Assign connectorA1 and connectorB1 to app1, app2 and app3 and deploy the applications. Now the applications have four connectors.
  3. Assign connectorC1 to app4 and app5 and deploy the applications. Now the applications have two connectors.
  4. Verify the applications are working with new connectors. If you have problems, test connector to application connectivity. If it works, retry to login to the application and try different operations. If you have problems, contact support.
  5. Remove connectorA, connectorB and connectorC from all the applications.
  6. Deploy the applications.
  7. Verify the applications are working with new connectors. If you have problems, test connector to application connectivity. If it works, retry to login to the application and try different operations. If you have problems, contact support.
  8. Add connectorA1 and connectorB1 to directory1 and directory2. Now both the directories have four connectors.
  9. Wait for 5 to 10 minutes. Verify you can login to both directories.
  10. Remove connectorA, connectorB from directory1 and directory2.
  11. Wait for 5 to 10 minutes. Verify you can login to both directories.
  12. Wait for a few days and monitor all of the applications work with the new connectors.
  13. Delete the connectorA, connectorB and connectorC from management portal.
  14. Delete the connector virtual-machines (VM) from your environment.
Note: For redundancy, install another connector connectorD1 and assign to applications app4 and app5.
Migration Scenario 2 : Resource restriction in production environment.

You have two applications app1 and app2 currently assigned to connectorA and connectorB. Since both the applications are connected to two connectors, you have redundancy and high availability.

Assume you have resource restrictions and cannot add more connectors in your production environment. Then the most optimal migration method for this scenario is:

  • Step1. ConnectorA removal.
    1. Remove connectorA from both the applications.
    2. Deploy the applications.
    3. Verify the applications are working with connectorB. If you have problems, test connector to application connectivity. If it works, retry to login to the application and try different operations. If you have problems, contact support.
    4. Delete the connectorA from EAA management portal.
    5. Delete the connectorA virtual-machine (VM) from your environment.
  • Step2. ConnectorA1 addition.
    1. Install the first new connector, connectorA1
    2. Assign connectorA1 to app1 and app2.
    3. Deploy the applications.
    4. Verify the applications are working with connectorA1 and connectorB. If you have problems, test connector to application connectivity. If it works, retry to login to the application and try different operations. If you have problems, contact support.
  • Step3. ConnectorB removal.
    1. Remove connectorB from both the applications.
    2. Deploy the applications.
    3. Verify the applications are working with connectorA1. If you have problems, test connector to application connectivity. If it works, retry to login to the application and try different operations. If you have problems, contact support.
    4. Delete the connectorB from EAA management portal.
    5. Delete the connectorB virtual-machine (VM) from your environment.
  • Step4. ConnectorB1 addition.
    1. Install the second new connector, connectorB1
    2. Assign connectorB1 to app1 and app2.
    3. Deploy the applications.
    4. Verify the applications are working with connectorB1. If you have problems, test connector to application connectivity. If it works, retry to login to the application and try different operations. If you have problems, contact support.
Note: If you have many connectors, then repeat the step1 and step2 for each connector, till all applications and all new connectors are working. We have shown for two connectors only.
Migration Scenario 3: Some resource restrictions in production environment.

You have twenty applications currently assigned to five connectors. You have thirty more applications currently assigned to another five connectors. You have two directories directory1 and directory2 assigned to two connectors.

Assume you have resource restrictions and can have no more than fourteen connectors in your production environment. So, you cannot add twelve new connectors along with the existing twelve connectors. But can add only two additional connectors at a time to your production environment.

The most optimal migration method for this scenario is:
  1. Remove two connectors from set of twenty applications.
  2. Deploy the applications.
  3. Verify the applications are working. If you have problems, test connector to application connectivity. If it works, retry to login to the application and try different operations. If you have problems, contact support.
  4. Delete the removed connectors from the EAA management portal.
  5. Delete the connector virtual-machines (VMs) from your environment.
  6. Install two new connectors.
  7. Assign new connectors to the set of twenty applications.
  8. Deploy the applications.
  9. Verify the applications are working. If you have problems, test connector to application connectivity. If it works, retry to login to the application and try different operations. If you have problems, contact support.
  10. Repeat above steps, two connector at a time, until you replace all the old connectors from all the applications
  11. Repeat above steps, two connector at a time, until you replace all the old connectors from all the directories.