Completing Upgrade Prerequisites

This section describes the upgrade prerequisites, which consist of the following steps:

1. Backup your MData using the Omni-HealthData Governance Console (OHDGC).

   For more information, see How to Backup Your MData in Omni-HealthData Governance Console.

2. Stop all services and the Omni-HealthData Controller.

   For more information, see How to Stop All Services and the Controller.

3. Navigate to the Configuration section in the Omni Console.
4. Take note of all configuration parameters that have been edited in your local deployment, specifically the current memory settings, which will be required when installing Omni-HealthData™ version 3.11.

   Note: Edited (modified) configuration parameters are identified by the icon.

5. Stop OHDGC (Apache Tomcat and WSO2 Identity Server).

   For more information, see How to Stop Omni-HealthData Governance Console (Apache Tomcat and WSO2 Identity Server).

6. Backup your Omni-HealthData™ databases.

   For more information, see How to Backup the Omni-HealthData Databases.

7. Backup your omnigen home directory.

   For more information, see How to Backup the Omnigen Home Directory.

8. Verify the recommended port values.

   Note: The recommended port values may have changed with Omni-HealthData™ version 3.11. Review the following recommended port value tables (Omni Server Port Usage and Omni-HealthData Governance Console Port Usage) before installing Omni-HealthData™ version 3.11.

   Default Port Numbers

   Component	Type	Version 3.1 Ports	Version 3.11 Ports	Security
   Omni-Gen Controller/Console	external	9500	9500	TLS 1.2
   Omni-Gen Server	internal	9512	9514	TLS 1.2
   Omni-Gen Server DQ High Speed TCP	internal	n/a	9532	none
   Data Quality Cleanse	external	9502	9504	none
   Data Quality Cleanse	internal	9503	9505	none
   Data Quality Match	external	9504	9506	none
   Data Quality Match	internal	9505	9507	none
   Data Quality Merge	external	9506	9508	none
   Data Quality Merge	internal	9507	9509	none
   Data Quality Remediation	external	9508	9510	none
   Data Quality Remediation	internal	9509	9511	none
   OGC Tomcat Shutdown	internal	9005	9024	none
   OGC Tomcat Console	external	9090	9501	Tomcat Config
   OGC Tomcat AJP	internal	9009	9525	Tomcat Config
   OGC WS02	external	9443	9503	WS02 Config
   OGC Redirect	internal	n/a	9526	none
   WS02 RMI Registry	internal	n/a	9534	WS02 Config
   WS02 RMI Server	internal	n/a	9535	WS02 Config
   WS02 LDAP Server	internal	n/a	9536	WS02 Config
   WS02 KDC Server	internal	n/a	9537	WS02 Config
   WS02 Thrift Entitlement Receiver	internal	n/a	9538	WS02 Config

9. For Postgres Only: verify pgcrypto installation.

   As of version 3.11, Omni-HealthData™ requires the Postgres pgcrypto functions to be available. Pgcrypto is included in most Postgres 8.4 and higher distributions, and is enabled for use by the following command:

   CREATE EXTENSION pgcrypto;

   To see if pgcrypto is available, issue the following command:

   select * from pg_available_extensions

   For earlier versions of Postgres, or its derivatives, the appropriate pgcrypto package must be installed. Where CREATE EXTENSION is not supported, the function definitions will need to be installed manually.

   For example:

   psql -d databasename -f $PGHOME/share/postgresql/contrib/pgcrypto.sql