This page takes you through the steps for upgrading from EMM 1.0.1 version to EMM 1.1.0. For more information on release versions, see the Release Matrix.
| Table of Contents | ||||
|---|---|---|---|---|
|
Preparing to upgrade
The following are the specific prerequisites you must complete before you upgrade from EMM 1.0.1 to EMM 1.1.0:
Before you upgrade to the latest version of WSO2 EMM, you create a staging database, which is essentially an empty database.
Stop all the Carbon servers connected to the database.
Note 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 (EMM 1.0.1) to the staging database you created. This becomes the new database for your new version of WSO2 EMM.
- Download EMM 1.1.0 and connect it to your staging database.
- Configure the following files for the new production server.
- Go to the
<EMM_HOME>/repository/conf/datasources/directory and update themaster-datasources.xmlfile. See configuring master-datasources.xml. - Go to the
<EMM _HOME>/repository/conf/directory and update datasource references in theuser-mgt.xmland registry.xml files. See configuring user-mgt.xml and configuring registry.xml.
- Go to the
- Run the attached mysql_migration.sql script in to the EMM MySQL DB.
- Navigate to the
<EMM_HOME>/repository/deployment/server/jaggeryapps/publisher/upload/directory in the WSO2 EMM 1.0.1 pack and copy the content in that folder to the same location in the WSO2 EMM 1.1.0 pack. Perform any configurations required for the server (e.g., external user stores, clustering, caching, mounting etc.).
Note Note that configurations should not be copied directly between servers.
- Start the server.
Going into production
Create tenants and test WSO2 EMM throughly. Once the 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.