Download WSO2 Governance Registry 5.0.0.
Log in to the WSO2 G-Reg Management Console and create the
endpointscollection. For instructions, see Adding a Collection.
The endpoints RXT is introduced in WSO2 G-Reg 5.0.0. Therefore, since the migration client might try to migrate data from "
/_system/governance/trunk/endpoints", which is not available in WSO2 G-Reg versions below 5.0.0, you need to manually create this endpoint collection before upgrading.
Stop all running server instances of WSO2 Governance Registry 4.6.0.
- Make sure that you have taken a backup of all the databases and existing configurations.
Follow the steps below to configure the database (in the
master-datasources.xmlfile) and the datasource property values (in the
api-manager.xmlfiles) of the new WSO2 G-Reg version, similar to the previous G-REG version.
<G-REG_5.0.0__HOME>/repository/conf/datasources/master-datasources.xml. For more information on how to do this for your database, see Working with Databases.
Go to the
<G-REG_5.0.0__HOME>/repository/confdirectory and update the datasource references in
api-manager.xmlto match the updated configurations in the
master-datasources.xmlfile which you made in the above step. The following are sample configurations if the datasource is
Code Block language html/xml title registry.xml
<dbConfig name="wso2registry"> <dataSource>jdbc/WSO2CarbonDB</dataSource> </dbConfig>
Code Block language html/xml title user-mgt.xml
<UserManager> <Realm> <Configuration> ... <Property name="dataSource">jdbc/WSO2CarbonDB</Property> </Configuration> ... </Realm> </UserManager>
Code Block language html/xml title api-manager.xml
If there are several 1000s of artifacts in the system, increase the value of the
<indexingFrequencyInSeconds>property (e.g. to 10), or reduce the value of the
<batchSize>property (e.g. to 10) in the
/repository/conf/registry.xmlfile as shown below.
Code Block language xml
<indexingConfiguration> <solrServerUrl>http://192.168.48.220:8983/solr/registry-indexing</solrServerUrl> <startingDelayInSeconds>35</startingDelayInSeconds> <indexingFrequencyInSeconds>3</indexingFrequencyInSeconds> <!--number of resources submit for given indexing thread --> <batchSize>50</batchSize> <!--number of worker threads for indexing --> <indexerPoolSize>50</indexerPoolSize> <!-- location storing the time the indexing took place--> </indexingConfiguration>
- Download the
org.wso2.carbon.greg.migrate.client-5.0.0.jarfile and copy it to the
<G-REG_5.0.0__HOME>/repository/components/dropinsdirectory. If you use a clustered/distributed setup, copy the JAR file to the master nodes.
Start the WSO2 Governance Registry 5.0.0 with the following command options to migrate the registry configurations. If you have a clustered/distributed setup, run the following command options in master node only.
sh wso2server.sh -Dmigrate=5.0.0 -DmigrateReg=true
wso2server.bat -Dmigrate=5.0.0 -DmigrateReg=true
It is recommended to restart all the WSO2 Governance Registry 5.0.0 instances. Check for any other configurations that were done for WSO2 Governance Registry 4.6.0 (based on your solutions), and update the configuration files in WSO2 Governance Registry 5.0.0 accordingly. For example, external user stores, caching, mounting.