Versions Compared

Key

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

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 .

Table of Contents
maxLevel3
minLevel3

...

  1. Stop the current server.
  2. Select the relevant migration script from hereSelect 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.sqlmigration-identity.sql and migration.sql. However,  for all Carbon products except WSO2 IS, only the migration.sql script is required to be executed.
  3. Download and run the migration.sql script on the old database.

Upgrading from DSS 3.1.1 to DSS 3.2.0

...

  1. Download DSS 3.2.0 and connect it to the staging database you created when upgrading the database.
  2. Connect the latest production server to the database as described below:
  3. 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.
  4. 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.