This page takes you through the steps for upgrading the product version from DSS 3.1.0 to DSS 3.1.1. For more information on release versions, see the Release Matrix .
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Before you upgrade to the latest version of WSO2 DSS, you should create a staging database. When you upgrade the database, you will be copying the data from the production database to the staging database. Once this data migration is completed, you will install the latest version of WSO2 DSS and point it to the staging database, which then becomes the production database
Note You should NOT connect a new version of WSO2 DSS to an older database that has not been migrated.
Make a backup of the database and the <DSS_HOME> directory prior to upgrading. The <AS<DSS_HOME> directory can simply be copied to the new database.
- Stop all the Carbon servers connected to the database before running the migration scripts.
- Note that the upgrade should be done during a period when there is low traffic on the system.
...
- Connect the latest production server to the database as described below:
- Configure the
<PRODUCT_HOME>/repository/conf/datasources/master-datasources.xml file. Refer configuring master-datasources.xml. - Go to the
<PRODUCT_HOME>/repository/confdirectory and update datasource references in theuser-mgt.xmlandregistry.xml files.Refer configuring user-mgt.xml and configuring registry.xml.
- Configure the
- Since a separate database (staging database) is used for the upgrade, the data that is collected in the actual production system while the upgrade is in progress should be added to the upgraded database using a script.
- Start the server.
Recommended Checkpoints
The databases should contain the newly added tables, which are namely as follows:
UM_DOMAINUM_SYSTEM_USERUM_SYSTEM_ROLEUM_SYSTEM_USER_ROLE
Going into production
The following are 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.
Once the above tests are run successfully, it is safe to consider that the upgrade is ready for production. However, it is advised to test any features that are being used in production.