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 maxLevel 3 minLevel 3
...
- Configure the following files for the new production server.
- Go to the
<DSS_HOME>/repository/conf/datasources directory and update the
master-datasources.xml file
. See configuring master-datasources.xml. - Go to the
<DSS
_HOME>/repository/conf
directory and update datasource references in theuser-mgt.xml
andregistry.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/server
directory. - If multitenancy is used, copy the
<DSS_HOME>/repository/tenants
directory.
- 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_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.