This guide takes you through the steps for upgrading product versions from DSS 3.1.0 to DSS 3.1.1. For more information on release versions, see the Release Matrix.
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Following are the limitations of upgrading:
- 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 rollback an upgrade. It is impossible to restore a backup of the previous server and retry the migration progress.
Downtime
The downtime is limited to the time taken for switching databases when the migrating environment is connected to the production.
...
- Stop the current server.
- Select the relevant script for the upgrade from here. Select the
migration.sqlscript corresponding to your database type. E.g., If your database is MySQL, you need to executemysql-migration.sql.Note that there are three migration scripts available:migration-service-provider.sql,migration-identity.sqlandmigration.sql. However, for all Carbon products except WSO2 IS, only themigration.sqlscript is required to be executed. - 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. - 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 - Recommended Tests
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.
The staging database should be used as the new production database with the new Carbon server. The staging server should have the configurations equivalent to the production server. Map the production domain to the staging environment, when the staging environment is running smoothly. This upgrade should be done during a period when there is low traffic on the system.
Once the above tests are run successfully, it is safe to consider that the upgrade is ready for production. However, it is always advised to carryout testing on features that are being used in production.
...