Omni-Patient Management Central (OPMC) Components Configuration Overview

How to:

Install Omni-Patient Management Central on Windows / Apache Tomcat

Omni-Patient Management Central (OPMC) is distributed as a .zip archive (for example, OPMC_2.5.0.zip). The release .zip file contains:

Web Archive Files:
- omni360.war
  The web archive for the user interface (UI).
- OmniDomain.war
  RESTful Domain layer services.
- OmniService.war
  RESTful JPA services.
- RemediationService.war
  The Remediation Server, which includes an embedded iWay Service Manager (iSM) server.
- OmniDictInstall.war
  A web application for loading database objects on a Windows/SQL Server instance.
OmniDictInstall_lx.war
A web application for loading database objects on a Linux/Postgres instance.
MData.xml
Pre-defined screen layout definition metadata (templates). The templates are defined in the MData.xml file, which is located in:
```
omni360.war\WEB-INF\classes
```

Unless a file named prodDB.h2.db is already present in the [catalina_home] directory, it will be created as follows.

After starting Apache Tomcat with the OPMC war set deployed, when the first user with a System_Administrator role logs in, that user will be prompted to upload metadata. For more information, see Uploading Metadata.

In subsequent Apache Tomcat startups, if the prodDB.h2.db file already exists in the [catalina_home]\bin directory, the defaults in the existing or new MData.xml file are not accessed or loaded. Rather the definitions in the prodDB.h2.db file are used.

OmniDictImport.zip
This archive contains the following dictionary builder components for the Data Dictionary application:
- OmniDictDeployAndOperate.pdf
  Instructions on installing the Data Dictionary application.
- Other Omni Data Dictionary loading artifacts and the OMNI_HOME/directory folders with scripts and other documents that can be used to load customer-specific, custom RDM Database Objects into the Data Dictionary.

Procedure: How to Install Omni-Patient Management Central on Windows / Apache Tomcat

Note that this configuration of Omni-Patient Management Central (OPMC) through version 2.5.0 requires that the five OPMC .war file all be deployed on the same Windows system and same Tomcat\webapps folder. Many installation and configuration references specify localhost as part of a URL or property description. Use localhost not the host name, unless otherwise instructed to explicitly use the host name opmc_hostname.

The OMNI and OPMC databases, as well as Omni-Patient Server, can exist on the same system or separate systems.

Extract the opmc_version.zip file (for example, opmc_2.5.0.zip) to the root location on your drive.
The following root directory is created:
```
drive:\OPMC_2.5.x
```
Perform the steps in Installing and Configuring the WSO2 Identity Server to install and configure the WSO2 Identity Server (WSO2 IS).
Perform the steps in How to Configure Apache Tomcat/OPMC to Access the WSO2 Identity Server to connect Apache Tomcat and its OPMC web applications to the WSO2 Identity Server.
Perform the steps in Installing a New Version of Omni-Patient Management Central to install and configure Omni-Patient Management Central (OPMC).