Upgrading from a Previous Release

This page takes you through the steps for upgrading the product version from DSS 3.1.1 to DSS 3.2.0. For more information on release versions, see the Release Matrix .

Preparing to upgrade

Complete the following prerequisites.

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

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 <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.

Limitations

This upgrade 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 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.

Upgrading the database

To migrate from the existing production database to the new database (staging database):

Stop the current server.
Select the relevant migration script from here. Select the migration.sql script corresponding to your database type. For example, 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.
Download and run the migration.sql script.

Upgrading from DSS 3.1.1 to DSS 3.2.0

To connect the latest production server to the new database and to migrate the configurations:

Download DSS 3.2.0 and connect it to the staging database you created when upgrading the database.
Connect the latest production server to the database as described below:
- Configure the <DSS_HOME>/repository/conf/datasources/master-datasources.xml file. See configuring master-datasources.xml.
- Go to the <DSS_HOME>/repository/conf directory and update datasource references in the user-mgt.xml and registry.xml files. See configuring user-mgt.xml and configuring registry.xml.
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_DOMAIN
UM_SYSTEM_USER
UM_SYSTEM_ROLE
UM_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.