This page takes you through the steps for upgrading to DSS 3.2.0. For more information on release versions, see the Release Matrix .Table of Contents maxLevel 3 minLevel 3
...
Before you upgrade to the latest version of WSO2 DSS, you create a staging database, which is essentially an empty database. Note that you should NOT connect a new version of WSO2 DSS to an older database that has not been upgraded.
Make a backup of the database and the <DSS_HOME> directory prior to upgrading. The <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 Note that the upgrade should be done during a period when there is low traffic on the system.
Limitations
- This The database upgrade can only be done for some if the database types are the same. 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 roll back an upgrade. It is impossible to restore a backup of the previous server and retry the upgrade process.
Downtime
The downtime is limited to the time taken for switching databases when the staging database is promoted to the actual production status.
...
- Configure the following files for the new production server.
- Go to the
<DSS_HOME>/repository/conf/datasources directory and update themaster-datasources.xml file. See configuring master-datasources.xml. - Go to the
<DSS_HOME>/repository/confdirectory and update datasource references in theuser-mgt.xmlandregistry.xml files.See configuring user-mgt.xml and configuring registry.xml.
- Go to the
- Copy the following directories from the old database to the staging database.
- To migrate the super tenant settings, copy the
<DSS_HOME>/repository/deployment/serverdirectory. - If multitenancy is used, copy the
<DSS_HOME>/repository/tenantsdirectory.
- To migrate the super tenant settings, copy the
- 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.