Upgrade from 10.1: Prepare the Old API Gateway
In this section you will do the following:
Create a ZIP file containing backups of the configurations for the old
Integration Server that hosts
API Gateway, the
API Gateway UI and dashboard (Kibana), and for one
API Gateway instance. You can migrate only one
API Gateway instance.
Create a snapshot of the Event Data Store. The Event Data Store contains the following:
APIs.
Applications.
Policies and policy actions.
Configurations and administrator settings.
Aliases.
Users, groups, and access profiles.
Plans, packages, and subscriptions.
API events for transactions, monitoring, policy violations, threat protection, lifecycle, and errors.
Performance metrics.
Follow the steps below to migrate create the configuration backups and the Event Data Store snapshot.
1. Start the old API Gateway.
2. Open a command window or shell and go to the old_Software AG_directory/IntegrationServer/instances/instance_name/packages/WmAPIGateway/cli/bin directory, where instance_name is the API Gateway instance to migrate. Then run the command below.
The -backupDestinationDirectory parameter is the directory in which to store the ZIP file containing the configuration backups, and the Event Data Store snapshot. The directory must already exist and you must have write permissions to it. The snapshot will be stored in a sub-directory named default. The ZIP file and the snapshot will be named apigw_upgrade_backup.zip and apigw_upgrade_backup, respectively.
apigw-upgrade-backup.[bat|sh]
-backupDestinationDirectory full_path_to_directory_for_
configuration_backups_ZIP_file_and_EDS_snapshot
3. If the old and new API Gateway installations are on different machines, copy the -backupDestinationDirectory to the new machine.