Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user Former user

Saved on

Key

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

This guide takes you through the steps for upgrading product versions from BRS 2.0.0 to BRS 2.1.0. For more information on release versions, see the Release Matrix.

...

The following are the limitations of upgrading:

  • This upgrading process can only be done for some database types. For example, if you are using MySQL currently and you need to migrate to Oracle in the new version, these scripts will not work.
  • You cannot rollback the upgrading process. It is impossible to restore a backup of the previous server and retry the upgrading progress.

Downtime

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

...

Upgrade Procedure

  1. Stop the current Governance registry server.

    Note

    Before discarding the old GREG instance, please take a backup of the GREG_HOME/solr directory. Solr-based index is required to re-index all the resources once migrated.

  2. Download WSO2 Governance Registry 4.6.0 from http://wso2.com/products/governance-registry/. 
  3. Select the relevant script for the upgrade from here. Select the migration.sql script corresponding to your database type. E.g., If your database is MySQL, you need to execute mysql-migration.sql.Note that there are three migration scripts available: migration-service-provider.sql, migration-identity.sql and migration.sql. However, for all Carbon products except WSO2 IS, only the migration.sql script is required to be executed.  
  4. To connect the new product version to the migrated database, configure the following files: 
    • Configure <PRODUCT_HOME>/repository/conf/datasources/master-datasources.xml. 
    • Go to the <PRODUCT_HOME>/repository/conf directory and update datasource references in user-mgt.xml, registry.xml and api-manager.xml. 

Migrating the configurations

  1. Open the GREG_HOME/repository/conf/user-mgt.xml file and add the following property to the existing AuthorizationManager configuration as shown below.

    Code Block
    <Property name=“CaseSensitiveAuthorizationRules">true</Property>

  2. In the new product version, open GREG_HOME/repository/conf/registry.xml and change the value of this indexing configuration as shown below.

    Code Block
    <lastAccessTimeLocation>/_system/local/repository/components/org.wso2.carbon.registry/indexing/lastaccesstime460</lastAccessTimeLocation>

  3. Perform any configurations required for the server, e.g., external user stores, clustering, caching, mounting.

    Note

    Note that configurations should not be copied directly between servers.

  4. Start the server.Business Rules Server.

    Add Text