| Oracle® Healthcare Foundation Installation Guide Release 7.0.1 E70997-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Healthcare Foundation Installation Guide Release 7.0.1 E70997-03 |
|
|
PDF · Mobi · ePub |
Oracle Healthcare Foundation Data Pipeline Services installer configures WebLogic application server for the Oracle Healthcare Foundation products and services installation and configuration. You can install Data Pipeline Services 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.3, "Installing the Oracle Healthcare Foundation Data Pipeline Services on Primary Node"
Section 5.4, "Installing the Oracle Healthcare Foundation Data Pipeline Services on Secondary Node"
Section 5.6, "Uninstalling the Oracle Healthcare Foundation Data Pipeline Services"
The following are the prerequisites to install Oracle Healthcare Foundation Data Pipeline Services:
WebLogic domain with name "oh_domain" should not exist. The installer must be on the machine where WebLogic is installed for both primary and secondary node configuration.
All Oracle Healthcare Foundation Data Model schemas should exist.
Oracle external table DIRECTORY object must be created for Omics Data Bank.
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 issues with the installer.
oraInstall<timestamp>.out - this output file records the output of all the scripts run by the installer.
oraInstall<timestamp>.err - this error 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>/reports/Oracle_Healthcare_Data_Pipeline_Services_7.0.1_install_<timestamp>.html
While reporting any problems that occur during Oracle Healthcare Foundation Data pipeline services installation, make sure that you include all the above log files
To install Oracle Healthcare Foundation Data pipeline services on the primary node, perform the following steps:
Extract the contents of the Oracle Healthcare Foundation media pack to your system.
Navigate to the <media_pack_location>/ folder.
Unzip the OHF_V701_Linux-x64.zip file where you want to launch the installer using the following command:
unzip -a OHF_V701_Linux-x64.zip
Navigate to the Disk1/install folder.
Change the protection on files as follows:
chmod 755 *
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.
Click Next. Select a Product to Install screen appears.
Select the Oracle Healthcare Foundation Data Pipeline Services 7.0.1.0.0 option and click Next.
The Specify Home Details screen appears.
Select the data pipeline services install home name and location.
Click Next. The Verify Installation Prerequisites screen appears.
Verify if all the prerequisites are met before proceeding.
Click Next. The Java Home screen appears.
Specify the JDK installation path. The installer validates this path.
Click Next. The Fusion Middleware (FMW) screen appears.
Specify the WebLogic with ADF installation path. The installer validates this path.
Click Next. The Cluster Configuration screen appears.
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.
Enter values for the following fields:
Listen Address
Listen Port
SSL Listen Port
User name - WebLogic administrator user
Password - WebLogic administrator password
Click Next. The Node Manager Configuration screen appears.
Enter values for the following fields:
Listen Address
Listen Port
User name - Node manager administrator user
Password - Node manager administrator password
Click Next. The Managed Server Configuration screen appears.
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 8001, three managed servers with listen ports 8001, 8002, 8003 are created.
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.
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
Click Next. The Oracle Healthcare Foundation Data Model Configuration screen appears.
Enter values for the following fields:
Database Host name
Database Port
Service Name
Omics Databank schema name
Omics Databank schema password
Services Schema name
Services Schema password
Click Next. The Service Configuration screen appears.
Select Yes to provide service configuration.
Select No to provide service configuration post installation.
Click Next. The File Upload Service Configuration screen appears.
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
Use bucket and object name
Click Next. The Omics Loader Service Configuration screen appears.
Enter values for the following fields:
Oracle data directory object
Ensembl and SwissProt directory
Click Next. The Summary screen appears.
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.
See the log file located in ORACLE_BASE/oraInventory/logs.
Review the generated installation log files for errors. For details, Section 5.5.
Contact Oracle support, if necessary, to resolve any errors.
To install Oracle Healthcare Foundation Data pipeline services on the secondary node, perform the following steps:
Extract the contents of the Oracle Healthcare Foundation media pack to your system.
Navigate to the <media_pack_location>/ folder.
Unzip the OHF_V701_Linux-x64.zip file where you want to launch the installer using the following command:
unzip -a OHF_V701_Linux-x64.zip
Navigate to the Disk1/install folder.
Change the protection on files as follows:
chmod 755 *
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.
Click Next. Select a Product to Install screen appears.
Select the Oracle Healthcare Foundation Data Pipeline Services 7.0.1.0.0 option and click Next.
The Specify Home Details screen appears.
Select the data pipeline services install home name and location.
Click Next. The Verify Installation Prerequisites screen appears.
Verify if all the prerequisites are met before proceeding.
Click Next. The Java Home screen appears.
Specify the JDK installation path. The installer validates this path.
Click Next. The Fusion Middleware (FMW) screen appears.
Specify WebLogic with ADF installation path. The installer validates this path.
Click Next. The Cluster Configuration screen appears.
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.
Click Next. The AdminServer Configuration screen appears.
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
Administrator User name
Administrator Password
Click Next. The Node Manager Configuration screen appears.
Enter values for the following fields:
Listen Address
Listen Port
Administrator User name
Administrator Password
Click Next. The Managed Server Configuration screen appears.
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 8001, three managed servers with listen ports 8001, 8002, 8003 are created.
Click Next. The Summary screen appears.
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.
See the log file located in ORACLE_BASE/oraInventory/logs.
Review the generated installation log files for errors. For details, Section 5.5.
Contact Oracle support, if necessary, to resolve any errors.
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.
If the installer fails, de-install the domain oh_domain. Make sure all secondary node machines are uninstalled first before uninstalling the primary node. Restart the AdminServer after every secondary node uninstall.
|
 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
