Versions Compared

Old Version 6

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Rukshani Weerasinha

Saved on

Key

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

...

  1. Stop the current BRS 2.0.0 server.

    Note

    Before discarding the old BRS instance, make a backup of the BRS_Home/solr directory. Solr-based index is required to re-index all the resources once migrated.

  2. Select the relevant script for the upgrade from here on the production database. The script you use will depend on the type of database you are using, for instance, if your database is MySQL you need to run the execute mysql-migration.sql command in MySQL (you would use Oracle or MSSQL to run the script if that is the database you are using). Running this script will ensure that the database is upgraded with the additional tables and schemas which are required for BRS 2.1.0.

    Info

    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.

  3. Once you run the migration script on the production database, copy the data from your production database to the staging database you created when preparing to upgrade. This becomes the new database for your new version of BRS.
  4. Download WSO2 Business Rules Server 2.1.0 from http://wso2.com/products/business-rules-server/.
  5. To connect the new product version to the upgraded (staging) database, configure the following files:  
    1. Configure <PRODUCT_HOME>/repository/conf/datasources/master-datasources.xml. See here for more information on how to do this for your database.

    2. Go to the <PRODUCT _HOME>/repository/conf directory and update the datasource references in user-mgt.xml, xml and registry.xml and api-manager.xml to  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
      languagexml
      titleregistry.xml
      <dbConfig name="wso2registry">
    <dataSource>jdbc/WSO2CarbonDB</dataSource>
</dbConfig>
      Code Block
      languagexml
      titleuser.mgt.xml
      <UserManager>
  <Realm>
  <Configuration>
  ...
  <Property name="dataSource">jdbc/WSO2CarbonDB</Property>
  </Configuration>
  ...
  </Realm>
</UserManager>
      Code Block
      languagexml
      titleapi.manager.xml
      <DataSourceName>jdbc/WSO2CarbonDB</DataSourceName>
    6. Replace the BRS_HOME/solr  directory with the backup you made in step 1. Note that this step is not a must but will make the re-indexing process faster.
Recommended checkpoints
The databases should contain the newly added tables, which are namely as follows:
  • UM_DOMAIN
  • UM_SYSTEM_USER
  • UM_SYSTEM_ROLE
  • UM_SYSTEM_USER_ROLE
Going into production
Recommended tests
The following are the recommended tests to run on the staging system: 
  • Create multiple user stores and try adding users to different user stores.
  • Create multiple tenants and add different user stores to the different tenants. Thereafter, add users to the various user stores.
  • The staging database should be used as the new production database with the new Carbon server. The staging server should have the configurations equivalent to the production server. Map the production domain to the staging environment, once the staging environment is running smoothly. This migration should be done during a period when there is low traffic on the system.
Once the above tests are run successfully, it is safe to consider that the migration is ready for production. However, it is always advised to carryout testings on features that are being used in production.