Back up all databases in your API Manager instances along with the synapse configs of all the tenants and super tenant.
You find the synapse configs of the super tenant in the
<CURRENT_API-M_HOME>/repository/deployment/server/synapse-configs/defaultdirectory. Synapse configs of tenants are in the
If you use a clustered/distributed API Manager setup, back up the available configurations in the API Gateway node.
- Download API Manager 2.0.0 from http://wso2.com/products/api-manager/.
<API-M_2.0.0_HOME>/repository/conf/datasources/master-datasources.xmlfile and provide the datasource configurations for the following databases. You can copy the configuration values from the same file in the current API Manager instance already being used.
- User Store
- Registry database/s
- API Manager Databases
Edit the registry configurations in the
<API-M_2.0.0_HOME>/repository/conf/registry.xmlfile and the user database in the
<API-M_2.0.0_HOME>/repository/conf/user-mgt.xmlfile similar to the configurations of the current API Manager.
Note that in a clustered/distributed API Manager setup, step 5 and 6 need to be done on the Gateway node.
Move all your synapse configurations except the files mentioned below by copying and replacing the
<CURRENT_API-M_HOME>/repository/deployment/server/synapse-configs/defaultdirectory to the
NOTE: Do not replace the files listed below from the
<CURRENT_API-M_HOME>/repository/deployment/server/synapse-configs/defaultfolder to APIM 2.0.0. These are application-specific APIs and sequences. If you made any custom changes to the files below, please merge them to the corresponding files in 2.0.0.
Move all your tenant synapse configurations by updating the configurations made in the
<CURRENT_API-M_HOME>/repository/tenantsdirectory to the
NOTE: Get the files listed below from the
<API-M_2.0.0_HOME>/repository/deployment/server/synapse-configs/default/sequencesdirectory and replace the corresponding files in the
If you have documentation defined for your APIs, make sure you add a value to the Documentation Summary field.
Documentation summary is mandatory in APIM 2.0 onwards. Trying to migrate with an empty documentation summary field from an older version can cause issues in the migration.
Upgrading the API Manager to 2.0.0