Upgrade guides
Planning the upgrade
Ensure that you follow the correct upgrade path (all viable upgrade scenarios are determined in the procedure title/description):
- To upgrade to Omada Identity versions 15.0.0 - 15.0.6, the minimum required version is Omada Identity 14.0.16.
- To upgrade to Omada Identity version 16.0.0, the minimum required version is Omada Identity 15.0.5 or 15.0.6.
- To upgrade to Omada Identity version 16.0.1, the minimum required version is Omada Identity 16.0.0.
Also, ensure that you copy your PswEncryptionKey.
Handling installed hotfixes and changed files
During the upgrade, the installer will overwrite any versioned files, for example, *.DLL files as well as the Omada Data Warehouse (ODW) Microsoft SQL Server Integration Services (SSIS) packages. Hence, all hotfixes installed previously will be overwritten. If non-versioned files (for example *.JS or web.config) are changed, either due to a hotfix or manual editing, these files won't be overwritten automatically by the installer during the upgrade procedure.
You should remove the modified files (or restore the original ones) from the installation folder before running the upgrade. After the upgrade, apply your changes again to the files which you changed manually.
Note on changesets
If you recorded any changesets before the update, you cannot import them into the updated version. To transfer these changesets:
- Download all changesets from the source environment before upgrading it.
- Import the downloaded changesets into each target environment while it is still running the original version.
- Upgrade the target environment only after you have imported the changesets.
Moving changesets between different versions is not supported. Although the system may not report an error in some cases, importing changesets between different versions can lead to unexpected results.
To use the Access Request or Approvals feature, you must install the Extend Access package.
Completing OPS jobs
Before performing an upgrade, it is recommended to ensure that there are no pending Omada Provisioning Service (OPS) jobs. You can do it by stopping the Role and Policy Engine (RoPE) service and waiting for any OPS jobs to complete before upgrading.
After upgrading, the settings must be committed to OPS from the system onboarding page for one of the onboarded systems.
Stopping services and creating backups
-
Make sure you have information on service accounts and your credentials available.
-
Stop all running Omada Identity services, as well as any scheduled SSIS import jobs. In Internet Information Services (IIS), stop all Omada related Application Pools and Websites. You should stop the following services:
- Omada Identity Suite (OIS) Timer Service
- OPS
- Omada RoPE Service
-
Stop the Omada Identity Enterprise Server (ES) portal.
-
Create a backup of the OPS installation folder.
-
Create a backup of the Omada RoPE installation folder.
-
Create a backup of all the Omada Identity databases. Below you can find the default names of the relevant databases:
- OIS
- ES Audit database
- Omada Source System Data DB
- ODW
- ODW Master
- ODW Staging
- Provisioning Service
- RoPE
Click on the available upgrade guide to upgrade your Omada Identity solution to the desired version:
Upgrade guide from 16.0.0 to 16.0.1
3 items