This page walks you through the process of upgrading to BRS 2.2.0 from a previous BRS versionBRS 2.1.0. Go to the required tab for step by step instructions based on the upgrade you need to perform. For more information on release versions, see the Release Matrix.
| Note |
|---|
You cannot roll back the upgrade process. However, it is possible to restore a backup of the previous database so that you can restart the upgrade progress. |
Preparing to upgrade
The following prerequisites need to be completed before upgrading.
...
| Info |
|---|
The downtime is limited to the time taken for switching databases in the production environment. |
Upgrading the database
The instructions in this section describe how you can perform a data migration to upgrade the 2.1.0 database for use in BRS 2.2.0.
...
Once you run the migration scripts on the new database, it becomes the upgraded database for BRS 2.2.0.
Migrating the configurations
Follow the procedure below to migrate configurations from BRS 2.1.0 to BRS 2.2.0.
Check the configurations in the following files in BRS 2.1.0, and apply same configurations in BRS 2.2.0 manually.
Note Configurations should not be copied directly from BRS 2.1.0 to BRS 2.2.0 because the configuration files have new properties added to them as well as obsolete properties removed from them between the two releases.
Configuration File Location axis2.xml<BRS_HOME>/repository/conf/axis2axis2_client.xml<BRS_HOME>/repository/conf/axis2carbon.xml<BRS_HOME>/repository/confmaster-datasources.xml<BRS_HOME>/repository/conf/datasourcesidentity.xml<BRS_HOME>/repository/conflog4j.properties<BRS_HOME>/repository/confregistry.xml<BRS_HOME>/repository/confcatalina-server.xml<BRS_HOME>/repository/conf/tomcatweb.xml<BRS_HOME>/repository/conf/tomcatIf the Cipher tool was configured for BRS 2.1.0, check the configurations in the following files and apply the same changes in BRS 2.2.0 manually.
Configuration File Location cipher-text.properties<BRS_HOME>/repository/conf/securitycipher-tool.properties<BRS_HOME>/repository/conf/security- Check the configurations in the other files located in the
<BRS 2.1.0_HOME>/repository/confdirectory and apply the same changes to BRS 2.2.0 manually. - If there are any third party libraries used with BRS 2.1.0 that you want to migrate, copy the following directories as applicable from BRS 2.1.0 to BRS 2.2.0:
- If you have used JMS libraries, JDBC libraries etc, copy
<BRS_HOME>/repository/components/lib. - If you have used OSGi bundles such as SVN kit etc, copy
<BRS_HOME>/repository/components/dropins.
- If you have used JMS libraries, JDBC libraries etc, copy
- Start the BRS 2.2.0 server. For more information, see Running the Product.
Migrating artifacts
You should manually deploy Composite Application Archive (CAR) files that you have in BRS 2.1.0 to BRS 2.2.0. For more information, see Creating and Deploying Carbon Applications.
| Info | ||
|---|---|---|
| ||
To migrate deployment artifacts:
|
Testing the upgrade
- When the database upgrade scripts are executed, the following are some of the new tables that will be created in the database:
- UM_DOMAIN
- UM_SYSTEM_USER
- UM_SYSTEM_ROLE
- UM_SYSTEM_USER_ROLE
- Verify that all the required scenarios are working as expected. This confirms that the upgrade is successful.