6/8

3 Installation on the Middle Tier

This section describes the installation and configuration steps for the middle tier. This chapter includes the following topics:

• Section 3.1, "Prerequisites"

• Section 3.2, "Installation Log Files"

• Section 3.3, "Installing on the Primary Node"

• Section 3.4, "Installing on Secondary Node"

• Section 3.5, "Installing Oracle Healthcare Precision Medicine on the Middle Tier"

• Section 3.6, "Upgrading Oracle Healthcare Precision Medicine on the Middle Tier"

• Section 3.7, "Troubleshooting"

• Section 3.8, "Uninstalling Oracle Healthcare Precision Medicine"

3.1 Prerequisites

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.7 is installed.

• Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 7 are installed in JDK 1.7.

• Oracle Fusion Middleware Infrastructure (FMW) 12.1.3 is installed using JDK 1.7.

• Oracle Fusion Middleware is installed in the same system path on all machines in a distributed domain configuration.

• Patch 21983457—WebLogic Patch set update 12.1.3.0.6—is applied.

• WebLogic domain named ohf_opm_domain does not exist.

• OHPM database schemes are installed.

3.2 Installation Log Files

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.0.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.

3.3 Installing on the Primary Node

The installer must be run first in the primary node configuration to create a new WebLogic domain named ohf_opm_domain with a cluster named ohf_opm_cluster. All managed servers that the installer creates will be part of this cluster. The installer deploys and configures the OHPM application.

3.4 Installing on Secondary Node

After the primary node installation is successful, you can run the installer in the secondary node configuration on different machines other than the primary node machine to scale the cluster ohf_opm_cluster.

However, this node is optional and required only if you want to create a WebLogic domain spread across multiple machines. The installer can be run in this node at any time to add more machines to the WebLogic domain.

3.5 Installing Oracle Healthcare Precision Medicine on the Middle Tier

Perform the following steps to install OHPM on the middle tier.

1. Download the OHPM installation package from the Media Pack and extract the files into a directory.

2. Navigate to the <media_pack_location>/ folder.

3. 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
    
   

4. Navigate to the Disk1/install folder.

5. Change the protection on files using the following command:

   chmod 755 *

6. 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.

7. Click Next. The Select a Product to Install screen appears.

8. Select the Oracle Healthcare Precision Medicine Middle Tier 1.0.0.0.0 option and click Next.

   The Specify Home Details screen appears.

9. Enter the installation home name and location.

10. Click Next. The Choose Install Type screen appears.

11. Select Yes for a new install.

    Select No and upgrade your existing installation. You can only upgrade from a successful installation. If the installation fails, follow the instructions in Section 3.8, "Uninstalling Oracle Healthcare Precision Medicine" and restart installation.

12. Click Next. The Verify Install Prerequisites screen appears.

13. Verify if all the prerequisites are met before proceeding.

14. Click Next. The Java Home configuration screen appears.

15. Specify the Java home path. The installer validates this path.

16. Click Next. The Oracle Fusion Middleware Home screen appears.

17. Specify the Fusion Middleware path. The installer validates this path.

18. Click Next. The Cluster Configuration screen appears.

19. Select Yes to create a domain and make the machine as primary node where the WebLogic AdminServer is located.

    Select No to migrate an existing domain created by running this installer on the primary node to scale the cluster and add more machines to the domain.

20. Click Next. The AdminServer configuration screen appears.

21. Enter values for the following fields:

    • Listen address

    • Listen Port

    • SSL Listen Port

    • Username - WebLogic administrator user

    • Password - WebLogic administrator password

    • Verify password

22. Click Next. The Node Manager Configuration screen appears.

23. Enter values for the following fields:

    • Listen address

    • Listen port

    • Username - Node manager administrator user

    • Password - Node manager administrator password

    • Verify Password

24. Click Next. The Managed Server Configuration screen appears.

25. Enter values for the following fields:

    • Number of servers managed on this machine

    • Managed servers listen port start index - This is used to increment the port number. For example, if the number of managed servers is 3 and the listen port start index is 8001, three managed servers with listen ports 8001, 8002, 8003 are created.

26. Click Next. The FMW Repository Creation Utility (RCU) Configuration screen appears. Fusion Middleware (FMW) RCU requires Oracle Database user with DBA or SYSDBA. Using the installer, you can create new RCU repositories or use pre-created repositories using the WebLogic RCU utility.

27. Enter values for the following fields:

    • Database host

    • Database port

    • Service name

    • Schema prefix - Should be OPM

    • DBA username - This field is optional if the RCU repositories are pre-created using the RCU utility.

    • DBA password - This field is optional if the RCU repositories are pre-created using the RCU utility.

    • Schemas common password

    • Verify schemas password

28. Click Next. The OPM App Schema Configuration screen appears.

29. 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

    • OPM App schema name

    • OPM App schema password

30. Click Next. The EMR Keystore Configuration screen appears.

31. Select Yes.

    For details on EMR configuration, see the section on EMR configuration in the Oracle® Healthcare Precision Medicine Administrator's Guide.

32. Click Next.

33. Enter the location of the SSL certificate.

34. Click Next. The Network Proxy Configuration screen appears.

35. Select Yes.

36. Click Next. The Network Proxy Configuration details screen appears. Network proxy configuration is required to connect to OHPM Service Providers.

37. Enter values for the following fields:

    • Https proxy host

    • Https proxy port

38. Click Next. The Summary screen appears.

39. Verify all the details. To make any changes, click Back.

40. Click Install.

41. After the installation is complete, the End of Installation screen appears.

42. Click Exit after reviewing the installation information.

43. At the confirmation prompt, click Yes to exit the installer.

44. Review the generated installation log files for errors. Contact Oracle support, if necessary, to resolve any errors.

3.6 Upgrading Oracle Healthcare Precision Medicine on the Middle Tier

The Oracle Healthcare Precision Medicine middle tier installer can be used to upgrade an existing installation to:

• set values for EMR configuration and HTTPS Proxy configuration on the primary node

• update HTTP Proxy configuration on all secondary nodes

Primary node upgrade must be run first before running upgrade on all secondary nodes.

Perform the following steps to upgrade OHPM on the middle tier:

1. Download the OHPM installation package from the Media Pack and extract the files into a directory.

2. Navigate to the <media_pack_location>/ folder.

3. 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
    
   

4. Navigate to the Disk1/install folder.

5. Change the protection on files using the following command:

   chmod 755 *

6. 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.

7. Click Next. The Select a Product to Install screen appears.

8. Select the Oracle Healthcare Precision Medicine Middle Tier 1.0.0.0.0 option and click Next.

   The Specify Home Details screen appears.

9. Enter the installation home name and location.

10. Click Next. The Choose Install Type screen appears.

11. Select No to upgrade your existing installation.

12. Click Next. The Verify Upgrade Prerequisites screen appears.

13. Verify if all the prerequisites are met before proceeding.

14. Click Next. The Oracle Fusion Middleware Home screen appears.

15. Specify the Fusion Middleware path. The installer validates this path.

16. Click Next. The Cluster Configuration screen appears.

17. Select Yes to upgrade primary node.

    Select No if upgrading a secondary node and only after upgrading primary node successfully.

18. Click Next. The AdminServer configuration screen appears.

19. Enter values for the following fields:

    • Listen address

    • Listen Port

    • SSL Listen Port

    • Username - WebLogic administrator user

    • Password - WebLogic administrator password

    • Verify password

20. Click Next. The Node Manager Configuration screen appears.

21. Enter values for the following fields:

    • Listen address

    • Listen port

    • Username - Node manager administrator user

    • Password - Node manager administrator password

    • Verify Password

22. Click N ext. The EMR Keystore Configuration screen appears.

23. Select Yes.

    For details on EMR configuration, see the section on EMR configuration in the Oracle® Healthcare Precision Medicine Administrator's Guide.

24. Click Next.

25. Enter the location of the SSL certificate.

26. Click Next. The Network Proxy Configuration screen appears.

27. Select Yes.

28. Click Next. The Network Proxy Configuration details screen appears. Network proxy configuration is required to connect to OHPM Service Providers.

29. Enter values for the following fields:

    • Https proxy host

    • Https proxy port

30. Click Next. The Summary screen appears.

31. Verify all the details. To make any changes, click Back.

32. Click Install.

33. After the installation is complete, the End of Installation screen appears.

34. Click Exit after reviewing the installation information.

35. At the confirmation prompt, click Yes to exit the installer.

36. Review the generated installation log files for errors. Contact Oracle support, if necessary, to resolve any errors.

3.7 Troubleshooting

If the status on any of the managed servers is failed due to the following errors in the log files, start it 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>

Primary Node

• 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.

Secondary Node

• If the installer fails to connect to the AdminServer, verify that the AdminServer is running on the primary node by accessing the WebLogic Admin console from the Secondary node.

• If the installer fails due to an incorrect Fusion Middleware path, make sure that WebLogic is installed in the same file system location as the primary node.

3.8 Uninstalling Oracle Healthcare Precision Medicine

If the installer fails, de-install the domain ohf_opm_domain. Make sure all secondary node machines are uninstalled before uninstalling the primary node. Restart the AdminServer after every secondary node uninstall.