This page takes you through the steps for upgrading from DSS 3.1.1 to DSS 3.2.0. For more information on release versions, see the Release Matrix .
Preparing to upgrade
The following are the specific prerequisites you must complete before you upgrade from DSS 3.1.1 to DSS 3.2.0:
Before you upgrade to the latest version of WSO2 DSS, you create a staging database, which is essentially an empty database.
Stop all the Carbon servers connected to the database.
Note that the upgrade should be done during a period when there is low traffic on the system.
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 configurations
To migrate the configurations to the staging database:
Copy the data from the old database to the staging database you created. This becomes the new database for your new version of WSO2 DSS.
- Download DSS 3.2.0 and connect it to your staging database.
- 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.
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.