Versions Compared


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


  1. Download WSO2 Governance Registry 5.4.0

  2. Stop all running server instances of WSO2 Governance Registry 5.3.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 Changing the default database
    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
      <dbConfig name="wso2registry">
      Code Block
        <Property name="dataSource">jdbc/WSO2CarbonDB</Property>
      Code Block
  5. Follow the below steps to update the database scripts.

    1. Download the migration resources and unzip it to a local directory. This folder is referred to as <MIGRATION_TOOL_HOME>.


      If you are using MySQL 5.7, rename the <MIGRATION_TOOL_HOME>/dbscripts/identity/migration-5.2.0_to_5.3.0/mysql.sql file to mysql_56.sql.

    2. Copy the DB script files in the <IS5.3.0_MIGRATION_<MIGRATION_TOOL_HOME>/dbscripts/identity/migration-5.2.0_to_5.3.0 directory to the <G-REG_5.4.0_HOME>/dbscripts/identity/ directory.

    3. Copy the <MIGRATION_TOOL_HOME>/dropins/ file in the <IS5.3.0_MIGRATION_TOOL_HOME>/dropins/ directory to the  file to the <G-REG_5.4.0_HOME>>/components/dropins/ directory.


      Alternatively, if you are using Oracle, either provide the database owner credentials in the datasource configurations (identity and user management databases). Else, pass the identity database owner name with the -DidentityOracleUser command and user management database owner name with ­the -DumOracleUser command.

  6. If there are thousands 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
    <!--number of resources submit for given indexing thread -->
    <!--number of worker threads for indexing -->
    <!-- location storing the time the indexing took place-->
  7. Once you are done with the migration tasks, restart the server as follows:


    Execute both commands one after the other.

    For Linux: 

    • sh -Dmigrate -Dcomponent=identity -DmigratePermissionData
    • sh -Dmigrate -Dcomponent=identity -DmigrateIdentityDB

    For Windows: 

    • wso2server.bat -Dmigrate -Dcomponent=identity -DmigrateIdentityDB
    • wso2server.bat -Dmigrate -Dcomponent=identity -DmigratePermissionData