Migrate API Portal
1. If the new and old API Portals are on the same machine, make sure the old API Portal is shut down.
2. If you installed the new API Portal in a clustered, high-availability setup, make sure all nodes are running and accessible to the Zookeeper ensemble. Then register all the nodes with the parent node by invoking the REST service shown below. The default for the load balancer port is 18007.
Parameter | Value |
End point | http://load_balancer_host:load_balancer_port/acc/rest/nodes/ |
Method type | POST |
Content type | application/json |
Payload | {"nodename": "host_name", "hostname": "host_name", "port": "cloud_agent_port", "username": "Clous", "password": "g3h31m“} |
3. Start the new API Portal Cloud Controller.
4. Run this command:
acc> startall
5. Restore the old master tenant into the new API Portal from the backup file you created earlier.
For | Run these commands... |
9.7 | acc> set acc config backup.restore.tenant.app.types = UMC acc> restore tenant master from full_path_to_backup_file
username=your_user_name password=your_password
|
9.8 | acc> set acc config backup.restore.tenant.app.types=ECP,ADS,UMC acc> restore tenant master from full_path_to_backup_file
username=your_user_name password=your_password
|
9.9 9.10 9.12 | acc> set acc config backup.restore.tenant.app.types=ECP,ADS,UMC acc> restore tenant master from full_path_to_backup_file
username=your_user_name password=your_password
|
10.0 | acc> restore tenant master from full_path_to_backup_file
username=your_user_name password=your_password
|
6. Earlier in this guide, you generated a list of tenants in the old API Portal. For each old tenant on the list except the default tenant and the master tenant, create a corresponding tenant in the new API Portal by running this command:
cmd> cd new_Software_AG_directory/API_Portal/server/bin/work/
work_apiportalbundle_s/tools/bin
cmd> y-tenantmgmt.bat -s http://load_balancer_host:load_balancer_port
-t tenant_name createTenant -u your_user_name -p your_password
7. In the User Management Component at http://host:port/umc, import the license for each tenant you created.
8. In the new API Portal Cloud Controller, run these commands:
acc> stop apiportalbundle_s
acc> start apiportalbundle_s
9. For each new tenant you created, restore the data for the corresponding old tenant into the new API Portal from the backup file you created earlier by running the commands below. Each file has the file extension .acb.
Important: | Inform API Portal users that they cannot work on the tenants during the restoration process. |
Important: | If the new tenant contains any data, the data will be replaced by the data you restore from the old tenant. |
For | Run these commands... |
9.7 9.8 9.9 9.10 9.12 | acc> set acc config backup.restore.tenant.app.types = UMC, ABS, ADS, ECP acc> restore tenant tenant_name from full_path_to_backup_file username=your_user_name password=your_password
|
10.0 | acc> restore tenant tenant_name from full_path_to_backup_file
username=your_user_name password=your_password
|
10. Run these commands:
acc> stop apiportalbundle_s
acc> start apiportalbundle_s
11. If you created a customized view of your old API Portal, you backed up the view. For instructions on restoring the customized view from the backup, see the backup and restore section in the webMethods API Portal Customization Guide.
Contact Support
|
Community
|
Feedback