This topic provides instructions on how you can upgrade from WSO2 G-Reg 5.2.0 to WSO2 G-Reg 5.3.0.
The following are the limitations of upgrading.
- This upgrading process can only be done for the same database types. For example, if you are using MySQL currently and you wish to use Oracle in the new version of G-Reg, these scripts will not work.
- You cannot roll back the upgrading process. However, it is possible to restore a backup of the previous database and redo the upgrading progress.
The downtime is limited to the time taken for switching databases when in the production environment.Upgrading
Follow the steps below to update the WSO2 G-Reg database.
- Database update
- Data migration
Updating the database
Download WSO2 Governance Registry 5.3.0.
Stop all running server instances of WSO2 Governance Registry 5.2.0.
- Make sure that you have taken a backup of all the databases and existing configurations.
- To connect the new product version, to the database of the previous version, configure the following files:
<G-REG_HOME>/repository/conf/datasources/master-datasources.xml. For more information on how to do this for your database, see Working with Databases.
Navigate to the
<G-REG _HOME>/repository/confdirectory, and update the datasource references in
api-manager.xmlfiles, to 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
G-REG_HOME>/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>
Once the server is completely started, and you are done with the migration tasks, restart the server by executing the following commands: