Upgrade steps from 12.2 to 12.3

You can upgrade from any version of Omada Identity 12.2 to 12.3. It is recommended that you read the release notes version 12 to understand the details of the release.

When upgrading to a new major or minor version, you must have any custom extension compiled and present before you start the upgrade. Do not start an upgrade before receiving the new custom extension.

If you have made any customizations to the Services menu dashboard, and wish to upgrade to version 12.3, you need to back up the configuration, and manually merge the customizations after the upgrade procedure is done (that is, when all the packages in ES have been upgraded).

Upgrade Omada Identity Enterprise Server

To upgrade Omada Identity Enterprise Server:

1. Uninstall the old version of Omada Identity Enterprise Server first, and then install the new version of Enterprise Server. After installation is completed, select the Show the Windows Installer log option and if necessary, save the log file.

2. Run the Omada Enterprise Configuration Utility.

   • When you are prompted, enter the connection string that you saved. Then, click OK.

   • Click OK again to upgrade the database to version 12.3, then when the Setup complete message appears, click OK, and close the configuration utility.

     info

     At this point, in the Windows registry, in the \HKLM\Software\Omada\Omada Identity Suite\12.3 registry path, ensure you enter the PswEncryptionKey that you copied.

3. To upgrade OPS, run the OPS installer and follow the upgrade procedure.

   note

   This is an important step as this procedure updates the OPS-related .dll files. If these files are not updated at this point, the old files can cause breaking changes. Ensure that after installation has been completed, that you select the Show the Windows Installer log option and if necessary, save the log file.

4. To upgrade RoPE, run the RoPE installer and follow the upgrade procedure.

   note

   Ensure that after installation has been completed, that you select the Show the Windows Installer log option and if necessary, save the log file.

5. Apply the upgrade script UpdateDB_12_3.sql. You can find the script in the following location: C:\Program Files\Omada Identity Suite\Role and Policy Engine\Support Files.

6. Upgrade code extensions with the following steps:

   • Uninstall previous version.

   • Verify that any custom extensions or .dll is removed, for example,** C:\Program Files\Omada Identity Suite\Enterprise Server 12\bin\Omada.OE.Custom.(Customer name).(type).dll**.

   • Install the new code extension.

     info

     You must compare the Role and Policy Engine’s EngineConfiguration.config file, with the previous version. This is due to the file having been altered by the code extension update.

     Comparing time stamps is not considered enough and you must examine the contents of the file.

     For the same reason, you must also compare the Omada Provisioning Service’s Omada.OPS.Service.exe.config file with the previous version.

7. In IIS, start Omada-related Application Pools and web-sites.

8. After you install Enterprise Server and upgrade OPS, you must upgrade to the latest version, all standard application packages that you have already installed on your system.

   This is necessary for the application logic to work as expected.

   To do this, open the Enterprise Server website, and apply updates to the standard application. To begin, click the link in the yellow notification bar.

9. In the Omada Identity Portal, go to Setup > Administration > More > Code Assemblies, and open the Code Assemblies list. You must now verify that the custom assembly is installed correctly by opening the assembly in a text editor, and verifying that the classes do exist.

Upgrade Omada Data Warehouse

To upgrade Omada Data Warehouse:

1. Create a backup of the Omada ODW WebService.dtsConfig and Omada ODW ConnectionString.dtsConfig files.

2. Uninstall the current version and install the new Omada Data Warehouse. After installation is completed, select the Show the Windows Installer log and if needed, save the log file for later inspection.

3. Reapply the previously backed-up files Omada ODW WebService.dtsConfig and Omada ODW ConnectionString.dtsConfig.

4. On the Enterprise Server Audit database, re-apply the script CreateObjects.OISAudit.sql located in C:\Program Files\Omada Identity Suite\Datawarehouse\Support files.

5. In the Omada Identity Enterprise Server Database, run the SystemInfo.sql script. You can find the script in the following folder C:\Program Files\Omada Identity Suite\Enterprise Server\Script files.

   The script can detect the use of deprecated components. It is recommended that you keep track and are aware of these components. Examples of components are FormParts and CodeMethods.

   info

   A number of code methods and other APIs have been removed from the product. If the system cannot find a configured code method, it reports this in the system event log. When you have restarted the browser, ensure you check the event log.

6. Run Windows Services.

   • Start the OIS Timer Service and check the event log for errors.
   • Start the OPS service and check the event log for errors.
   • Start the RoPE service and check the event log for errors.

7. From Enterprise Server, queue an identity.

8. Check the event log and the calculation log for errors.

9. In Enterprise Server, in the Omada Identity Portal, go to Setup > Administration > Connectivity > Import profiles.

   • Start Import configuration profile, and wait for this to finish.
   • Start Import profile and wait for it to finish.