This section describes the installation and configuration steps for the middle tier. This chapter includes the following topics:
The following list points out the prerequisites for installing OHPM on the middle tier. Check that these are completed before you start installation.
JDK 1.8 is installed.
Oracle Fusion Middleware Infrastructure (FMW) 12.2.1.2 is installed using JDK 1.8.
Oracle Fusion Middleware is installed in the same system path on all machines in a distributed domain configuration.
Oracle® Healthcare Foundation middle tier is installed in the same middleware.
OHPM database schemes are installed.
While installing Oracle Healthcare Foundation Data pipeline services, the installer generates the following log files:
installActions<timestamp>.log - this log file records the action of the installer and can be used to diagnose any installer issues.
oraInstall<timestamp>.out - this file records the output of all the scripts run by the installer.
oraInstall<timestamp>.err - this file records the errors from all the scripts run by the installer.
The log files are time stamped and each installation session creates a new log file.
On a Linux machine, the log files are located at $ORACLE_BASE/oraInventory/logs. For example, /u01/app/oraInventory/logs.
The installation summary with all parameters provided for the installer will be available at:
<INSTALL_HOME>/opmmt/ Oracle_Healthcare_Precision_Medicine_Middle_Tier_1.1.0.0.0_install_<timestamp>.html
While reporting any problems that might occur during OHPM installation, make sure that you include all the above log files in your report.
Perform the following steps to install OHPM on the middle tier.
Download the OHPM installation package from the Media Pack and extract the files into a directory.
Navigate to the <media_pack_location>/ folder.
Using the following command, unzip the opm_Linux-x64.zip file to the folder where you want to launch the installer:
unzip -a opm_Linux-x64.zip
Navigate to the Disk1/install folder.
Change the protection on files using the following command:
chmod 755 *
Start the Oracle Universal Installer (OUI) using the following command. WebLogic should be installed on the same machine where installer is running.
./runInstaller
The Welcome screen appears.
Click Next. The Select a Product to Install screen appears.
Select the Oracle Healthcare Precision Medicine Middle Tier 1.1.0.0.0 option and click Next.
The Specify Home Details screen appears.
Enter the installation home name and location.
Click Next. The Verify Install Prerequisites screen appears.
Verify if all the prerequisites are met before proceeding.
Click Next. The Java Home configuration screen appears.
Specify the Java home path. The installer validates this path.
Click Next. The Oracle Fusion Middleware Home screen appears.
Specify the Fusion Middleware home path. The installer validates this path.
Click Next. The AdminServer configuration screen appears.
Enter values for the following fields:
Listen address
Listen Port
SSL Listen Port
Username - WebLogic administrator user
Password - WebLogic administrator password
Verify password
Click Next. The OHPM Schema Details configuration screen appears.
Enter values for the following fields using the OHPM schema details created while installing OHPM on the database tier.
Database host name
Database port
Service name
OHPM schema name
OHPM schema password
Click Next. The EMR Keystore Configuration screen appears.
If you want to publish genomic reports to EMR from OHPM application, select Yes.
Enter the location of the SSL certificate to be used for communicating with EMR.
Note:
After installation, specify the connection details for EMR using the EMR configuration API available athttp://docs.oracle.com/health-sciences/opm-11/admin-guide/emrconfig.htm#OHPAG445.Click Next. The Network Proxy Configuration screen appears.
Select Yes.
Click Next. The Network Proxy Configuration details screen appears. Network proxy configuration is required to connect to OHPM Service Providers.
Enter values for the following fields:
HTTPS proxy host
HTTPS proxy port
Click Next. The Summary screen appears.
Verify all the details. To make changes, click Back.
Click Install.
After the installation is complete, the End of Installation screen appears.
Click Exit after reviewing the installation information.
At the confirmation prompt, click Yes to exit the installer.
Review the generated installation log files for errors. Contact Oracle support, if necessary, to resolve any errors.
If the managed servers fail due to the following errors, start the servers manually from the Admin Console.
Critical subsystem DatabaseLessLeasing has failed. Setting server state to FAILED. Reason: Server is not in the majority cluster partition>
Server health failed. Reason: health of critical service 'DatabaseLessLeasing' failed.
If the installer fails due to the time taken by the node manager process to start, check the machine network configuration to make sure other processes are listening on the same port, and the user running the installer has the required file system permissions.
If the AdminServer fails to start due to the node manager process not being available, verify if the node manager process is still running.
If an incorrect database configuration is provided, modify it from the WebLogic Admin console.