Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster Data Service for Oracle E-Business Suite Guide Oracle Solaris Cluster |
Installing and Configuring Oracle Solaris Cluster HA for Oracle E-Business Suite
HA for Oracle E-Business Suite Overview
Overview of Installing and Configuring HA for Oracle E-Business Suite
Planning the HA for Oracle E-Business Suite Installation and Configuration
Restriction for the Supported Configurations of HA for Oracle E-Business Suite
Restriction for the Location of Oracle E-Business Suite Files
Determine Which Solaris Zone Oracle E-Business Suite Will Use
Verifying the Installation and Configuration of Oracle E-Business Suite
How to Verify the Installation and Configuration of Oracle E-Business Suite
Installing the HA for Oracle E-Business Suite Packages
How to Install the HA for Oracle E-Business Suite Packages
Registering and Configuring HA for Oracle E-Business Suite
How to Register and Configure HA for Oracle E-Business Suite
Verifying the HA for Oracle E-Business Suite Installation and Configuration
How to Verify the HA for Oracle E-Business Suite Installation and Configuration
Upgrading HA for Oracle E-Business Suite
How to Upgrade to the New Version of HA for Oracle E-Business Suite
Understanding the HA for Oracle E-Business Suite Fault Monitor
Probing Algorithm and Functionality
Forms Server in Servlet Mode Probe
Forms Server in Socket Mode Probe
Debugging HA for Oracle E-Business Suite
This section contains the procedures you need to install and configure Oracle E-Business Suite.
This section contains the procedures you need to install and configure Oracle E-Business Suite.
Refer to Determine Which Solaris Zone Oracle E-Business Suite Will Use for more information.
Refer to System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones for complete information about installing and configuring a zone.
# zoneadm list -v # zoneadm -z zonename boot
Refer to Oracle Solaris Cluster Software Installation Guide for information about creating a cluster file system and to Oracle Solaris Cluster Data Services Planning and Administration Guide for information about creating a highly available local file system.
Perform this step from the global zone on one node of the cluster.
Note - Ensure that the node has ownership of the disk set or disk group.
For Solaris Volume Manager, type:
# metaset -s disk-set -t
For Veritas Volume Manager, type:
# vxdg -C import disk-group # vxdg -g disk-group startall
# mount highly-available-local-filesystem
# zlogin zonename mkdir highly-available-local-filesystem
Mount the highly available local file system on one of the zones being used.
# mount -F lofs highly-available-local-filesystem \ > /zonepath/root/highly-available-local-filesystem
# zpool import -R / HAZpool
# zpool export -f HAZpool # zpool import -R /zonepath/root HAZpool
Note - If you are using Parallel Concurrent Processing, omit this step. Parallel Concurrent Processing requires physical hostnames.
Perform this step in the global zone on one node of the cluster for each logical hostname being used by Oracle E-Business Suite.
# ifconfig interface addif logical-hostname up
# ifconfig interface addif logical-hostname up zone zonename
If you are deploying Clustered OPMN OC4J instances, omit this step. Clustered OPMN OC4J instances require physical hostnames. If you are installing a Clustered OPMN single Web Entry Point server, you must still specify a logical hostname.
Note - If you are using Parallel Concurrent Processing, omit this step. Parallel Concurrent Processing requires physical hostnames.
Perform this step on all cluster nodes where Oracle E-Business Suite will run.
To provide logical host interpositioning for Oracle E-Business Suite you must create a symbolic link from /usr/lib/secure/libschost.so.1 to /usr/cluster/lib/libschost.so.1
# cd /usr/lib/secure # ln -s /usr/cluster/lib/libschost.so.1 libschost.so.1
If you are deploying Clustered OPMN OC4J instances, omit this step. Clustered OPMN OC4J instances require physical hostnames. If you are installing a Clustered OPMN single Web Entry Point server, you must still specify a logical hostname.
Perform this step in the global zone or non-global zone on one node of the cluster.
When running the rapidwiz installer, unless you are installing Parallel Concurrent Processing or Clustered OPMN OC4J instances, you must enter the logical hostname as the node name for the Database, Administration, Concurrent Manager, Forms, and Web Server. If you are performing a two-node or multi-node installation, you must specify the appropriate logical hostname as the appropriate node for the Database, Administration, Concurrent Manager, Forms, and Web Server.
If you are installing Parallel Concurrent Processing, do not specify a logical hostname. Instead, specify the physical hostname for the Concurrent Manager (Batch services). Using rapidwiz, add a server and configure batch services for each physical hostname that will participate in Parallel Concurrent Processing.
If you are installing Clustered OPMN OC4J instances, do not specify a logical hostname. Instead, specify the physical hostname. Using rapidwiz, add a server for each physical hostname that will participate in Clustered OPMN OC4J instances. If you are installing a Clustered OPMN single Web Entry Point server, you must still specify a logical hostname.
When executing rapidwiz, save the config.txt file in a permanent location, for example, /var/tmp/config.txt. If you are installing at least Oracle E-Business Suite Version 12, save the /var/tmpconf_SID.txt file before clicking OK on rapidwiz message No install actions found.
# cd oracle-ebusiness-suite-install-directory # ./rapidwiz
Execute rapidwiz for each logical hostname that you entered when generating the /var/tmp/config.txt file or /var/tmp/conf_SID file.
# cd oracle-ebusiness-suite-install-directory # ./rapidwiz -servername logical-hostname
If, after installing the Web Server, you encounter the validation error JSP is not responding, waiting 15 seconds and retesting, leave the rapidwiz GUI and follow Step a through Step e to resolve the validation error. Then you must return to the rapidwiz GUI to retry the validation.
Edit the httpd_pls.conf file and add the following entries for each physical cluster node within the VirtualHost _default_:* section.
Allow from cluster-node Allow from cluster-node.fqdn
# su - oraapp-user $ cd base-directory/sidora/iAS/Apache/Apache/conf $ vi httpd_pls.conf $ exit
The following example shows the logical hostname lhost1 and the cluster nodes clnode1 and clnode2 that have been added.
<VirtualHost _default_:*> <Location /> Order deny,allow Deny from all Allow from localhost Allow from lhost1 Allow from lhost1.example.com Allow from clnode1 Allow from clnode1.example.com Allow from clnode2 Allow from clnode2.example.com </Location> </VirtualHost>
Edit the oprocmgr.conf file and add the following entries for each physical cluster node within the VirtualHost _default_:8100 section.
Allow from cluster-node Allow from cluster-node.fqdn
# su - oraapp-user $ cd base-directory/sidora/iAS/Apache/Apache/conf $ vi oprocmgr.conf $ exit
The following example shows logical hostname lhost1 and the cluster nodes clnode1 and clnode2 that have been added.
<IfModule mod_oprocmgr.c> Listen 8000 ProcNode lhost1.example.com 8100 <VirtualHost _default_:8100> <IfDefine SSL> SSLEngine off </IfDefine> Port 8100 <Location /> Order Deny,Allow Deny from all Allow from localhost Allow from lhost1 Allow from lhost1.example.com Allow from clnode1 Allow from clnode1.example.com Allow from clnode2 Allow from clnode2.example.com </Location>/base-directory/sidappl/admin/SID_lhost1.xml <Location /oprocmgr-service> SetHandler oprocmgr-service </Location> <Location /oprocmgr-status> SetHandler oprocmgr-status </Location> </VirtualHost> </IfModule>
Edit the jserv.properties file and add the following entries for all physical cluster node within the security.allowedAddresses entry.
security.allowedAddresses=127.0.0.1, \ lhost.fqdn,clnode1.fqdn,clnode2.fqdn
# su - oraapp-user $ cd base-directory/sidora/iAS/Apache/Jserv/etc $ vi jserv.properties $ exit
The following example shows logical hostname lhost1 and the cluster nodes clnode1 and clnode2 that have been added.
security.allowedAddresses=127.0.0.1,lhost1.example.com,clnode1.example.com,clnode2.example.com
# su - oraapp-user $ cd base-directory/sidcomn/admin/scripts/SID_logical-hostname $ ./adstpall.sh apps/apps $ exit # su - oradb-user $ cd base-directory/siddb/9.2.0/appsutil/scripts/SID_logical-hostname $ ./addlnctl.sh stop SID $ ./addbctl.sh stop immediate $ ./addbctl.sh start $ ./addlnctl.sh start SID $ exit # su - oraapp-user $ cd base-directory/sidcomn/admin/scripts/SID_logical-hostname $ ./adstrtal.sh apps/apps $ exit
The JSP check should now work.
Note - If you are using Parallel Concurrent Processing, omit this step. Parallel Concurrent Processing requires physical hostnames.
Perform this step from the global zone or non-global zone where you installed Oracle E-Business Suite.
# su - oraapp-user $ vi app-base_directory/apps/apps_st/appl/customSID_app-logical-host.env
LD_PRELOAD_32=/usr/lib/secure/libschost.so.1 SC_LHOSTNAME=app-logical-host export LD_PRELOAD_32 SC_LHOSTNAME
envs='LD_LIBRARY_PATH=/usr/dt/lib:/user/openwin/lib:basedir/sidora/8.0.6/lib, \ LD_PRELOAD_32=/usr/lib/secure/libschost.so.1,SC_LHOSTNAME=lhost,MYAPPSORA=... # su - oraapp-user $ cd base-directory/sidora/8.0.6/network/admin/SID_logical-hostname $ vi listener.ora
The following example shows the LD_PRELOAD_32 and SC_LHOSTNAME entries that have been added.
SID_LIST_APPS_PROD = (SID_LIST = ( SID_DESC = ( SID_NAME = FNDSM ) ( ORACLE_HOME = /base-directory/sidora/8.0.6 ) ( PROGRAM = /base-directory/sidappl/fnd/11.5.0/bin/FNDSM ) ( envs='LD_LIBRARY_PATH=/usr/dt/lib:/user/openwin/lib:basedir/sidora/8.0.6 \ /lib,LD_PRELOAD_32=/usr/lib/secure/libschost.so.1,SC_LHOSTNAME=lhost1,MYAPPS=
Perform this step from the global zone or non-global zone where you installed Oracle E-Business Suite.
Note - If you installed Parallel Concurrent Processing, you installed batch services on the physical hostname. Therefore, to stop the Concurrent Manager, you must specify the physical-host pathname for the admin scripts. To stop other application-tier components that you installed by using a logical host, you must use the logical-host pathname for the admin scripts.
If you installed Clustered OPMN OC4J instances, you installed on the physical hostname. Therefore, to stop the Clustered OPMN OC4J instance, you must specify the physical-host pathname for the admin scripts. To stop other application-tier components that you installed by using a logical host, you must use the logical-host pathname for the admin scripts.
# su - oraapp-user $ cd app-base-directory/inst/apps/SID_app-logical-hostname/admin/scripts $ ./adstpall.sh apps/apps $ exit # su - oradb-user $ cd db-base-directory/SID/db/tech_st/*/appsutil/scripts/SID_db-logical-hostname $ ./addlnctl.sh stop SID $ ./addbctl.sh stop immediate
# su - oraapp-user $ cd app-base-directory/SIDcomn/admin/scripts/SID_app-logical-hostname $ ./adstpall.sh apps/apps $ exit # su - oradb-user $ cd db-base-directory/SID/db/9.2.0/appsutil/scripts/SID_db-logical-hostname $ ./addlnctl.sh stop SID $ ./addbctl.sh stop immediate
Perform this step from the global zone on the node where you installed Oracle E-Business Suite.
# umount highly-available-local-filesystem
# umount /zonepath/root/highly-available-local-filesystem
# zpool export -f HAZpool
Perform this step from the global zone on one node of the cluster for each logical hostname being used by Oracle E-Business Suite.
# ifconfig interface removeif logical-hostname