Page History
...
- Download the API Manager 1.9.0 from http://wso2.com/products/api-manager.
- Stop all running API Manager server instances.
Back up the databases of your API Manager 1.8.0 server instance.
Download the WSO2 API Migration Client v1.9.0
Copy the downloaded client (org.wso2.carbon.apimgt.migrate.client-1.9.0.jar) into
<APIM_1.9.0_HOME>/repository/components/dropins/
Change the query inside
<APIM_1.9.0_HOME>/dbscripts/migration-1.8.0_to_1.9.0/drop-fk.sql
according to your database typeNote The default file contains sql scripts for mysql and if you use mysql no need to do the 6th step.
Example quaries for H2
SELECT DISTINCT constraint_name FROM information_schema.constraints WHERE table_name = 'AM_APP_KEY_DOMAIN_MAPPING';
ALTER TABLE AM_APP_KEY_DOMAIN_MAPPING DROP CONSTRAINT <temp_key_name>;
Example quaries for Oracle
SELECT DISTINCT constraint_name FROM user_cons_columns WHERE table_name = 'AM_APP_KEY_DOMAIN_MAPPING';
ALTER TABLE AM_APP_KEY_DOMAIN_MAPPING DROP CONSTRAINT <temp_key_name>;
Start the API Manager 1.9.0 with the command
-Dmigrate=1.9
for database, registry and file system migrations. If you need to perform single resource migrations you can use the following commands. If you run-Dmigrate=1.9
earlier , you do not need to run the following commands- For database migrations run -Dmigrate=1.9 -DmigrateDB=true
- For registry migrations run -Dmigrate=1.9 -DmigrateReg=true
- For file system migrations run -Dmigrate=1.9 -DmigrateFS=true
Note Please note that if you run -Dmigrate=1.9 without any additional parameters, it migrates all the resources.
To re-index the artifacts in the registry, perform the two steps given below.
a) Rename the lastAccessTimeLocation in the
<APIM_1.9.0_HOME>
/repository/conf/registry.xml
file. For example, change the/_system/local/repository/components/org.wso2.carbon.registry/indexing/lastaccesstime
registry path to/_system/local/repository/components/org.wso2.carbon.registry/indexing/lastaccesstime_1.
b) Shut down AM 1.9.0, backup and delete the
<APIM_1.9.0_HOME>
/repository/conf/solr
directory and restart the server.Upgrading tenants
- If you have multiple tenants added to your API Manager instance, follow the steps below to migrate tenant configurations:
- Copy the contents from your previous
<APIM_HOME>/repository/tenants
directory to the same directory in the API Manager 1.9.0. Do not replace the_TokenAPI_.xml
,_RevokeAPI_.xml
and_AuthorizeAPI_.xml
files in the/default/api
sub directory. - Start the server
- Execute steps 3 and 4 for all tenants in your system.
- Execute steps 7 to 9 for all tenants in your system.
Upgrading external stores
- Copy the contents from your previous
If you have external stores configured in the registry, follow the steps below:
Log in to APIM 1.9.0 management console and click the Resources -> Browse menu.
Load the
/_system/governance/apimgt/externalstores/external-api-stores.xml
resource in the registry browser UI, configure your external stores and save.
Upgrading Google analytics
If you have Google Analytics configured in the registry, follow the steps below:
Log in to APIM 1.9.0 management console and go to Resources -> Browse menu.
Load the
/_system/governance/apimgt/statistics/ga-config.xml
resource in the registry browser UI, configure the Google analytics and save.
Upgrading workflows
If you have Workflows configured in the registry, follow the steps below:
Log in to APIM 1.9.0 management console and go to Resources -> Browse menu.
Load the
/_system/governance/apimgt/applicationdata/workflow-extensions.xml
resource in the registry browser UI, configure your workflows and save.