Skip to main content
Version: On prem: 15.0.1

Upgrade guides

Planning the upgrade​

There are three rules you need to follow:

  • You can't skip a major version. For example, if you want to upgrade from v11.1 to last Omada Identity, you must first upgrade to Omada Identity v12.2 or 12.3. You must upgrade one major version at a time.
  • You must always be on the latest patch version before upgrading to a new major version.
  • Migration from Role Engine to Role & Policy Engine is required.

Handling installed hotfixes and changed files​

During the upgrade, the installer will overwrite any versioned files, for example, *.DLL files as well as the ODW 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, these changesets can't be imported to the updated version. This means that you should import the changeset in the original environment and only then update Omada Identity to the newer version.

note

Moving changesets between versions isn't supported. However, it was previously possible to do so without errors in some cases.

important

To use the Access Request or the Approvals feature, you must install the Extend Access package.

Providing unique names of configuration objects​

Before upgrading, navigate to Setup > Master Data> Other> More > Configuration Objects and ensure that all configuration objects in the Enterprise Server have unique names. If not, change the names, so that each is unique.

The NAME property of the configuration data object type is now the property of the data object type and must be unique. Before upgrading to the latest version of Omada Identity verify that the names of the configuration data objects are unique. To see how many duplicated names you have in the system, use the following SQL query to get a list of all configuration data objects with duplicated names.

select DisplayName from tbldataobject
where DataObjectTypeID = 908 
GROUP BY DisplayName
HAVING COUNT(*) > 1

Completing OPS jobs​

Before performing an upgrade, it is recommended to ensure that there are no pending OPS jobs. You can do it by stopping the 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​

  1. Make sure you have information on service accounts and your credentials available.

  2. Stop all running Omada Identity services, as well as any scheduled SSIS import jobs. In IIS, stop all Omada related Application Pools and Websites. You should stop the following services:

    • Omada Identity Suite Timer Service
    • Omada Provisioning Service
    • Omada Role and Policy Engine Service

  3. Stop the Omada Identity Enterprise Server portal.

  4. Create a backup of the Omada Provisioning Service installation folder.

  5. Create a backup of the Omada Role and Policy Engine installation folder.

  6. 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
    • Omada Data Warehouse
    • Omada Data Warehouse Master
    • Omada Data Warehouse Staging
    • Provisioning Service
    • RoPE

Click on the available upgrade guide to upgrade your Omada Identity solution to the desired version: