This documentation is for WSO2 Governance Registry 5.3.0. View documentation for the latest release.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This

...

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.

Downtime

The downtime is limited to the time taken for switching databases when in the production environment.

Upgrading

Updating the

...

database

Follow the steps below to update the WSO2 G-Reg database.

  • Database update
  • Data migration 

Updating the database

  1. Download WSO2 Governance Registry 5.3.0

  2. Stop all running server instances of WSO2 Governance Registry 5.2.0.

  3. Make sure that you have taken a backup of all the databases and existing configurations.
  4. To connect the new product version, to the database of the previous version, configure the following files:  
    1. Configure <G-REG_HOME>/repository/conf/datasources/master-datasources.xml. For more information on how to do this for your database, see Working with Databases
    2. Navigate to the <G-REG _HOME>/repository/conf directory, and update the datasource references in user-mgt.xmlregistry.xml and api-manager.xml files, to match the updated configurations in the master-datasources.xml file, which you made in the above step. The following are sample configurations if the datasource is jdbc/WSO2CarbonDB.

      Code Block
      languagehtml/xml
      titleregistry.xml
      <dbConfig name="wso2registry">
          <dataSource>jdbc/WSO2CarbonDB</dataSource>
      </dbConfig> 
      Code Block
      languagehtml/xml
      titleuser-mgt.xml
      <UserManager>
        <Realm>
        <Configuration>
        ...
        <Property name="dataSource">jdbc/WSO2CarbonDB</Property>
        </Configuration>
        ...
        </Realm>
      </UserManager>
      Code Block
      languagehtml/xml
      titleapi-manager.xml
      <DataSourceName>jdbc/WSO2CarbonDB</DataSourceName>
  5. 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.xml file as shown below.

    Code Block
    languagexml
    <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>
  6. Once the server is completely started, and you are done with the migration tasks, restart the server by executing the following commands:

    • Linux: sh wso2server.sh 
    • Windows:  wso2server.bat 

...