9/11

5 Oracle Healthcare Foundation Middle-Tier

OHF Middle-Tier installs the following Web applications:

• Administration Console

• Data Pipeline Services

You can install these on the following nodes:

• Installing on Primary Node:

  Installer must be run in primary node configuration first to create a new WebLogic domain named oh_domain with a cluster named oh_cluster. All managed servers that installer created will be part of this cluster. Installer deploys and configures all Healthcare products and services, such as Omics Data loader service and File Upload service.

• Installing on Secondary Node:

  Once the primary node installation is successful, you can run the installer in the secondary node configuration on multiple different machines other than primary node machine to scale the cluster oh_cluster. However, this node is optional and is required only if you want to create a WebLogic domain spread across multiple machines. Installer can be run in this node at any time to add more machines to WebLogic domain.

This chapter contains the following sections:

• Section 5.1, "Supported Upgrade"

• Section 5.2, "Prerequisite Checklist"

• Section 5.3, "Installation Log Files"

• Section 5.4, "Installing the Oracle Healthcare Foundation Middle-Tier on Primary Node"

• Section 5.5, "Installing the Oracle Healthcare Foundation Middle-Tier on Secondary Node"

• Section 5.6, "Upgrading the Oracle Healthcare Foundation on the Middle-Tier on the Primary Node"

• Section 5.7, "Troubleshooting"

• Section 5.8, "Uninstalling the Oracle Healthcare Foundation Middle-Tier"

5.1 Supported Upgrade

The following are the supported upgrade path:

• OHF 7.0.1 to OHF 7.1

5.2 Prerequisite Checklist

	WebLogic domain with name "oh_domain" should not exist for fresh installation. The installer must be on the machine where WebLogic is installed for both primary and secondary node configuration.
	All OHF Data Model schemas exist.
	Oracle external table DIRECTORY object is created for Omics Data Bank.

5.3 Installation Log Files

While installing OHF Middle-Tier, the installer generates the following log files:

Table 5-1 Installation Log Files

File Name	Description
installActions<timestamp>.log	Records the action of the installer and can be used to diagnose issues with the installer.
oraInstall<timestamp>.out	Records the output of all the scripts run by the installer.
oraInstall<timestamp>.err	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>/reports/dps_install_<timestamp>.html

While reporting any problems that occur during Middle-Tier installation, make sure that you include all the above log files

5.4 Installing the Oracle Healthcare Foundation Middle-Tier on Primary Node

To install the Middle-Tier on the primary node:

1. Extract the contents of the OHF media pack to your system.

2. Navigate to the <media_pack_location>/ folder.

3. Unzip the OHF_V71_Linux-x64.zip file where you want to launch the installer using the following command:

   unzip -a OHF_V71_Linux-x64.zip

4. Navigate to the Disk1/install folder.

5. Change the protection on files as follows:

   chmod 755 *

6. Start the Oracle Universal Installer (OUI) by running the following command. WebLogic should be installed on the same machine where installer is running.

   ./runInstaller -local

   where, the -local option is to install on the local node irrespective of the cluster nodes specified on the installer machine.

   The Welcome screen appears.

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

8. Select the Oracle Healthcare Foundation Middle-Tier 7.1.0.0.0 option and click Next.

   The Specify Home Details screen appears.

9. Enter the Middle-Tier install home name and location and click Next.

   The Choose Install Type screen appears.

10. Select Yes to perform a fresh install and click Next.

    The Verify Install Prerequisites screen appears.

11. Verify if all the prerequisites are met before proceeding and click Next.

    The Java Home screen appears.

12. Specify the JDK installation path. The installer validates this path.

    Click Next. The Fusion Middleware Home screen appears.

13. Specify the WebLogic with ADF installation path. The installer validates this path.

    Click Next. The Cluster Configuration screen appears.

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

    Click Next. The AdminServer Configuration screen appears.

15. Enter values for the following fields:

    • Listen Address

    • Listen Port

    • SSL Listen Port

    • User name - WebLogic administrator user

    • Password - WebLogic administrator password

    • Verify password

16. Click Next. The NodeManager Configuration screen appears.

17. Enter values for the following fields:

    • Listen Address

    • Listen Port

    • User name - Node manager administrator user

    • Password - Node manager administrator password

    • Verify password

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

19. Enter values for the following fields:

    • Number of Managed Servers on this machine

    • Managed Servers listen port start index - This is used to increment port number. For example, if number of managed servers is 3, and listen port start index is 8081, three managed servers with listen ports 8081, 8082, and 8083 are created.

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

    Note:

    For Exadata or ASM group, create the RCU schema outside the installer. While creating the RCU, select all MDS, IAU, IAU_APPEND, IAU_VIEWER, OPSS, UMS, WLS, UCSCC, and STB schemas.

    For more details on RCU creation, see https://docs.oracle.com/middleware/1213/core/RCUUG/overview.htm#RCUUG101.

    • Database host

    • Database port

    • Service name

    • Schema prefix

    • DBA user name - 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

21. Click Next. The Oracle Healthcare Foundation Data Model Configuration - part 1 screen appears.

22. Enter values for the following fields:

    • Database host name

    • Database port

    • Service name

23. Click Next. The Oracle Healthcare Foundation Data Model Configuration - part 2 screen appears.

24. Enter values for the following fields:

    • Omics Data Bank schema name

    • Omics Data Bank schema password

    • Services schema name

    • Services schema password

    • HDM schema name

    • HDM schema password

    • Enterprise schema name

    • Enterprise schema password

25. Click Next. The Service Configuration screen appears.

    • Select Yes to provide service configuration and go to step 26.

    • Select No to provide service configuration post installation and go to step 31.

26. Click Next. The File Upload Service Configuration screen appears.

27. Enter values for the following fields:

    • File retention period in days

    • File storage location

    • Max file size in bytes

    • Max zip extract size in bytes

    • Simultaneous upload limit

28. Click Next. The Omics Loader Service Configuration screen appears.

29. Enter values for the following fields:

    • Oracle data directory object

    • Ensembl and SwissProt directory

30. Click Next. The Summary screen appears.

31. Click Install.

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

33. Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer.

34. See the log file located in ORACLE_BASE/oraInventory/logs.

35. Review the generated installation log files for errors. For details, Section 5.7.

36. Contact Oracle support, if necessary, to resolve any errors.

5.5 Installing the Oracle Healthcare Foundation Middle-Tier on Secondary Node

To install the Middle-Tier on the secondary node:

1. Extract the contents of the OHF media pack to your system.

2. Navigate to the <media_pack_location>/ folder.

3. Unzip the OHF_V71_Linux-x64.zip file where you want to launch the installer using the following command:

   unzip -a OHF_V71_Linux-x64.zip

4. Navigate to the Disk1/install folder.

5. Change the protection on files as follows:

   chmod 755 *

6. Start the Oracle Universal Installer (OUI) by running the following command. WebLogic should be installed on the same machine where installer is running.

   ./runInstaller -local

   where, the -local option is to install on the local node irrespective of the cluster nodes specified on the installer machine.

   The Welcome screen appears.

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

8. Select the Oracle Healthcare Foundation Middle-Tier 7.1.0.0.0 option and click Next.

   The Specify Home Details screen appears.

9. Enter the Middle-Tier install home name and location and click Next.

   The Choose Install Type screen appears.

10. Select Yes to perform a fresh installation and click Next.

    The Verify Install Prerequisites screen appears.

11. Verify if all the prerequisites are met before proceeding and click Next.

    The Java Home screen appears.

12. Specify the JDK installation path. The installer validates this path.

    Click Next. The Fusion Middleware Home screen appears.

13. Specify WebLogic with ADF installation path. The installer validates this path.

    Click Next. The Cluster Configuration screen appears.

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

15. Click Next. The AdminServer Configuration screen appears.

16. Enter values for the following fields:

    • Listen address - Running AdminServer listen address provided as part of primary node installation

    • Listen port - Running AdminServer listen port provided as part of primary node installation

    • SSL listen port - Running AdminServer SSL listen port provided as part of primary node installation

    • User name

    • Password

17. Click Next. The NodeManager Configuration screen appears.

18. Enter values for the following fields:

    • Listen address

    • Listen port

    • User name

    • Password

    • Verify password

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

20. Enter values for the following fields:

    • Number of Managed Servers on this Machine

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

21. Click Next. The Summary screen appears.

22. Click Install.

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

24. Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer.

25. See the log file located in ORACLE_BASE/oraInventory/logs.

26. Review the generated installation log files for errors. For details, Section 5.7.

27. Contact Oracle support, if necessary, to resolve any errors.

5.6 Upgrading the Oracle Healthcare Foundation on the Middle-Tier on the Primary Node

For the list of supported upgrade path, see Section 5.1.

Before upgrading OHF 7.0.1 to 7.1, make sure that the WebLogic JDK version is 1.8 u91 or above. If not:

1. Stop all servers and node manager on primary and secondary nodes.

2. Take a backup of WebLogic installation.

3. Upgrade the existing OHF 7.0.1 WebLogic version to JDK 1.8 u91 or above using the following instructions:

   1. Point ORACLE_HOME to the WebLogic install directory and DOMAIN_HOME to the domain directory.

   2. Update JDK references in below files:

      ORACLE_HOME/install/envVars.properties

      ORACLE_HOME/oracle_common/common/bin/commEnv.sh

      ORACLE_HOME/oracle_common/common/bin/setHomeDirs.sh

      ORACLE_HOME/oui/bin/compareInventory.sh

      ORACLE_HOME/oui/bin/install.sh

      ORACLE_HOME/oui/bin/viewInventory.sh

      ORACLE_HOME/wlserver/.product.properties

      DOMAIN_HOME/bin/setDomainEnv.sh

      DOMAIN_HOME/nodemanager/nodemanager.properties

4. Restart all servers and node manager on primary and secondary nodes.

To upgrade OHF on the Middle-Tier on the primary node:

1. Extract the contents of the OHF media pack to your system.

2. Navigate to the <media_pack_location>/ folder.

3. Unzip the OHF_V71_Linux-x64.zip file where you want to launch the installer using the following command:

   unzip -a OHF_V71_Linux-x64.zip

4. Navigate to the Disk1/install folder.

5. Change the protection on files as follows:

   chmod 755 *

6. Start the Oracle Universal Installer (OUI) by running the following command. WebLogic should be installed on the same machine where installer is running.

   ./runInstaller -local

   where, the -local option is to install on the local node irrespective of the cluster nodes specified on the installer machine.

   The Welcome screen appears.

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

8. Select the Oracle Healthcare Foundation Middle-Tier 7.1.0.0.0 option and click Next.

   The Specify Home Details screen appears.

9. Enter the Middle-Tier install home name and location and click Next.

   The Choose Install Type screen appears.

10. Select No to upgrade your existing installation and click Next.

    The Verify Upgrade Prerequisites screen appears.

11. Verify if all the prerequisites are met before proceeding and click Next.

    The Fusion Middleware Home screen appears.

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

    Click Next. The AdminServer Configuration screen appears.

13. Enter values for the following fields:

    • Listen Address

    • Listen Port

    • SSL Listen Port

    • User name - WebLogic administrator user

    • Password - WebLogic administrator password

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

15. Enter values for the following fields:

    • Listen Address

    • Listen Port

    • User name - Node manager administrator user

    • Password - Node manager administrator password

16. Click Next. The Oracle Healthcare Foundation Data Model Configuration - part 1 screen appears.

17. Enter values for the following fields:

    • Database Host name

    • Database Port

    • Service Name

18. Click Next. The Oracle Healthcare Foundation Data Model Configuration - part 2 screen appears.

19. Enter values for the following fields:

    • HDM schema name

    • HDM schema password

    • Enterprise schema name

    • Enterprise schema password

20. Click Next. The Summary screen appears.

21. Click Install.

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

23. Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer.

24. See the log file located in ORACLE_BASE/oraInventory/logs.

25. Review the generated installation log files for errors. For details, Section 5.7.

26. Contact Oracle support, if necessary, to resolve any errors.

5.7 Troubleshooting

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 same port, and user running the installer has the required file system permissions.

• If AdminServer fails to start due to node manager process being not available, verify if the node manager process is still running.

• If wrong database configuration is provided, modify it from the WebLogic Admin console.

Secondary Node

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

• If the installer fails due to wrong FMW path, make sure WebLogic is installed in the same file system location as the primary node.

5.8 Uninstalling the Oracle Healthcare Foundation Middle-Tier

If the installer fails:

• De-install the domain oh_domain.

• Make sure all secondary node machines are uninstalled first before uninstalling the primary node.

• Make sure that no processes related to ports and oh_domain of the previous installation are running.