Upgrading Omni-Gen to Version 3.16

While the Omni-Gen Server (OGS) and the Omni Governance Console (OGC) Version 3.8.3 or Version 3.12 are started, save a copy of the existing OGC MData.

Sign in to the OGC with a user name that has the System_Administrator role.
Select Administration from the menu bar.
Scroll down to the bottom of the page and click Download Metadata.
The MData.xml file will be saved to your local Downloads folder. Rename this file accordingly to indicate that it corresponds to your latest Version 3.8.3 or Version 3.12 (for example, MDataFrom383.xml).
Sign out of the OGC.

Stop Omni-Gen.

Note: Before stopping Omni-Gen, ensure no work orders are currently running.

On Windows:

If you have installed Omni-Gen as a Windows service, stop the service. Otherwise, navigate to the Omni-Gen home directory, and from a command prompt, run the following command using the Run as Administrator option:
```
cd \omnigen\omniserver
```
To stop the Omni-Gen services, type:
```
omni stop-all
```

On Linux:

Navigate to the OmniServer home directory. For example:
```
/data/omni/product/omnigen/OmniServer
```
To stop all services, type:
```
./omni.sh stop-all
```

Rename the Version 3.8.3 or Version 3.12 omnigen installation directory from \omnigen to correspond to your version, either 3.8.3 or 3.12. For example:

\omnigen383_backup

Note: In case you need the configuration parameters from your previous 3.8.3 or 3.12 version for reference, they will be saved in a properties files. For example:

\omnigen383_backup\OmniGenInstall.properties

Back up the Omni-Gen databases as a precaution.

Run the Omni-Gen Version 3.16 installer. For more information, see Installing the Omni-Gen Server and the Omni Governance Console on Linux Platforms.

Note: Install Omni-Gen into the \omnigen directory and configure it for the same database as the Version 3.8.3 or Version 3.12 installation. If needed, you can refer to the configuration parameters in the properties file for step 3.

On Windows, you must install the same way as you installed the version from which you are upgrading. For example, if you installed as a Windows service, you must install Version 3.16 as a Windows service.

During installation, select No when prompted about creating new Remediation tables. This is so that your existing Remediation schema and content tables will be maintained and used in the new Version 3.16 instance.
Select Yes when prompted about installing WSO2.
After you complete all of the prompts in the installer, click Install to run the installation.

As part of the upgrade, use your existing version 3.8.3 or 3.12 WSO2 policies and roles with the version 3.16 WSO2 certificates.

Note: This upgrade consideration applies only to those upgrading to Version 3.16.

Rename the \omnigen\wso2_is\repository directory to c:\omnigen\wso2_is_repository_316_backup.
Copy the \omnigen383_backup\wso2_is\repository directory to c:\omnigen\wso2_is\repository.
Copy the \omnigen\wso2_is\repository_316_backup\resources\security directory to \omnigen\wso2_is\repository\resources\security.