Migrating the APS 2.x Provisioning Gateway

This step is a part of the service nodes migration to Azure.

To migrate the APS 2.x Provisioning Gateway from a source to a target node:

Step 1. Migrate application-specific modules and scripts from the source to the target endpoint node.
Step 2. Change the endpoint URL in CloudBlue Commerce and test the target installation.

Step 1. Migrate Application-Specific Modules and Scripts from the Source to the Target Endpoint Node

For each APS 2.x application, contact the application vendor and request a migration solution for the application endpoint.

Follow the solution to migrate the application distributive to the target node.

Step 2. Change the Endpoint URL in CloudBlue Commerce and Test the Target Installation

Copy the switch-endpoint.py script to Operations Management Node.
For each application instance:
1. Obtain the instance ID to pass it to the script:
  1. In the Provider Control Panel, go to Operations > Services > Applications. Click the necessary APS 2.x application.
  2. In the Instances tab, find the necessary instance ID.
2. Create a test subscription for the application (or use an existing test subscription).
3. Perform the following testing and post-migration steps:
  1. To make sure that the target endpoint responds correctly to standard requests, call the switch-endpoint.py script as follows:
    Note: The script sends GET requests to the target endpoint for subscription application resources.
```
# python switch-endpoint.py --app-instance-id <INSTANCE ID> --test-subscription <TEST SUBSCRIPTION ID> --endpoint-url <TARGET ENDPOINT URL>
```
    For example:
```
python switch-endpoint.py --app-instance-id 22 --test-subscription 1000003 --endpoint-url https://endpoint.test.com/newendpoint
...
...################## Tests are completed successfully
```
  2. To make sure that the target endpoint works and then, if successful, update the application endpoint URL in Operations database, call the switch-endpoint.py script and pass the --change-endpoint flag as follows:
    Note: As a result of this step, the endpoint URL will be changed for the application instance in Operations database. These changes will affect all subscriptions related to the instance.
```
# python switch-endpoint.py --app-instance-id <INSTANCE ID> --test-subscription <TEST SUBSCRIPTION ID> --endpoint-url <TARGET ENDPOINT URL> --change-endpoint
```
    For example:
```
python switch-endpoint.py --app-instance-id 22 --test-subscription 1000003 --endpoint-url https://endpoint.test.com/newendpoint --change-endpoint
...
...################## Tests are completed successfully
...
...################## Endpoint URL of instance #22 is set to https://endpoint.test.com/newendpoint
```
4. To make sure that the application instance works correctly with the target endpoint, create or modify some application resources in the test subscription.