Throughout the following next sections, references will be made to certain values for the deployment of Oracle E-Business Suite. The following list shows these values used in subsequent examples.
<dbname> - PROD
<dbname>COMN_TOP - /global/mnt10/d01
<dbname>CON_APPSUSER - ebs
<Logical Hostname> - lhost1
Determine how Oracle E-Business Suite will be deployed in Sun Cluster.
Depending on how Oracle E-Business Suite is deployed using rapidwiz ensure that each Logical Hostname used by rapidwiz is available.
To do this, complete steps 1–9 in section How to Register and Configure Sun Cluster HA for Oracle E-Business Suite as a Failover Service.
Mount the Oracle E-Business Suite Cluster File Systems.
If Failover File Systems will be used by the Oracle E-Business Suite instance, you must mount these manually.
Install Oracle E-Business Suite using rapidwiz onto a Global File System.
For a discussion of the advantages and disadvantages of installing the software on local versus cluster files systems, see “Determining the Location of the Application Binaries” on page 3 of the Sun Cluster Data Services Installation and Configuration Guide.
Run rapidwiz to build the config.txt file for the Oracle E-Business Suite deployment you have chosen, for example, single-node, two-node, or multi-node.
Save the config.txt file for Oracle E-Business Suite, for example, /var/tmp/config.txt.
Run rapidwiz for each Logical Hostname that you used when building the config.txt file, using the -servername parameter.
# rapidwiz -servername <Logical Hostname>
After you install the Concurrent Manager using rapidwiz, amend the Concurrent Manager Listener listener.ora file so that it can listen on the Logical Hostname. This step needs to be completed before continuing with rapidwiz for the Web Server and Forms Server installation of Oracle E-Business Suite.
Amend the Concurrent Manager Listener listener.ora file so that it recognizes the Logical Hostname.
The output from the following grep commands is used as input to subsequent commands.
# grep PROD.CON_COMNTOP /var/tmp/config.txt PROD.CON_COMNTOP=/global/mnt10/d01/oracle/prodcomn # # su ebs # cd /global/mnt10/d01/oracle/prodcomn/admin/scripts/PROD # # ./adalnctl.sh stop # ./adcmctl.sh stop apps/apps # # grep ORA_ENVFILE= adalnctl.sh ORA_ENVFILE="/global/mnt10/d01/oracle/prodora/8.0.6/PROD.env" # # grep TNS_ADMIN= /global/mnt10/d01/oracle/prodora/8.0.6/PROD.env TNS_ADMIN="/global/mnt10/d01/oracle/prodora/8.0.6/network/admin/PROD" # # vi /global/mnt10/d01/oracle/prodora/8.0.6/network/admin/PROD/listener.ora # Add LD_PRELOAD_32=/usr/lib/secure/libloghost.so.1 and LHOSTNAME=<Logical Hostname> to the envs= parameter for the SID_NAME=FNDSM_<SID> enrty
The following code shows the contents of the listener.ora file after it has been modified. If autoconfig is used after listener.ora has been modified, you will need to reapply these changes, that is autoconfig will back out these changes so you will need to reapply them.
# more /global/mnt10/d01/oracle/prodora/8.0.6/network/admin/PROD/listener.ora # $Header: admk80ln_ux.sql 115.7 2002/05/17 10:10:59 pkm ship $ # LISTENER.ORA For Oracle Applications # This file is automatically generated APPS_PROD = (ADDRESS_LIST = (ADDRESS= (PROTOCOL= TCP)(Host= lhost1)(Port= 1626)) ) SID_LIST_APPS_PROD = (SID_LIST = ( SID_DESC = ( SID_NAME = FNDSM_PROD ) ( ORACLE_HOME = /global/mnt10/d01/oracle/prodora/8.0.6 ) ( PROGRAM = /global/mnt10/d01/oracle/prodappl/fnd/11.5.0/bin/FNDSM ) ( envs='LD_PRELOAD_32=/usr/lib/secure/libloghost.so.1, \ LHOSTNAME=lhost1, \ MYAPPSORA=/global/mnt10/d01/oracle/prodappl/APPSORA.env, \ DISPLAY=clusterix1:0.0,PATH=/usr/bin:/usr/ccs/bin:/bin, \ FNDSM_SCRIPT=/global/mnt10/d01/oracle/prodappl/fnd/11.5.0/bin/gsmstart.sh' ) ) ( SID_DESC = ( SID_NAME = FNDFS ) ( ORACLE_HOME = /global/mnt10/d01/oracle/prodora/8.0.6 ) ( PROGRAM = /global/mnt10/d01/oracle/prodappl/fnd/11.5.0/bin/FNDFS ) ( envs='EPC_DISABLED=TRUE,NLS_LANG=AMERICAN_AMERICA.US7ASCII, \ LD_LIBRARY_PATH=/usr/dt/lib:/usr/openwin/lib: \ /global/mnt10/d01/oracle/prodora/8.0.6/lib, \ SHLIB_PATH=/usr/lib:/usr/dt/lib:/usr/openwin/lib: \ /global/mnt10/d01/oracle/prodora/8.0.6/lib, \ LIBPATH=/usr/dt/lib:/usr/openwin/lib: \ /global/mnt10/d01/oracle/prodora/8.0.6/lib' ) ) ) STARTUP_WAIT_TIME_APPS_PROD = 0 CONNECT_TIMEOUT_APPS_PROD = 10 TRACE_LEVEL_APPS_PROD = OFF LOG_DIRECTORY_APPS_PROD = /global/mnt10/d01/oracle/prodora/8.0.6/network/admin LOG_FILE_APPS_PROD = APPS_PROD TRACE_DIRECTORY_APPS_PROD = /global/mnt10/d01/oracle/prodora/8.0.6/network/admin TRACE_FILE_APPS_PROD = APPS_PROD
Create a symbolic link for libloghost.so.1.
To facilitate Oracle E-Business Suite working with a Logical Hostname the program libloghost.so.1 is supplied to interrupt the system call when retrieving the hostname and instead return the Logical Hostname.
The interrupted system call is made only when the Concurrent Manager Listener is running and when the Concurrent Manager Server is started or stopped.
The library that contains the libloghost.so.1 program must reside in a secure library to prevent warning messages whenever such a system call is made.
To facilitate the library being within a secure directory, create the following symbolic link on all nodes within Sun Cluster that will host the Sun Cluster HA for Oracle E-Business Suite data service.
# cd /usr/lib/secure # # ln -s /opt/SUNWscebs/cmg/lib/32/libloghost.so.1 libloghost.so.1
If you do not want to have /opt/SUNWscebs/cmg/lib/32/libloghost.so.1 running from a secure library, you will need to do the following.
Amend the previous step (step 4d) to replace
/opt/SUNWscebs/cmg/lib/32/libloghost.so.1. For example:
When registering the Concurrent Manager Resource, specify that you are not using a secure library. This is explained in step 13 in How to Register and Configure Sun Cluster HA for Oracle E-Business Suite as a Failover Service
Running /opt/SUNWscebs/cmg/lib/32/libloghost.so.1 outside of a secure library will cause similar warning messages to appear. You can ignore these.
ld.so.1: <cmd>: warning: /opt/SUNWscebs/cmg/lib/32/libloghost.so.1: open failed: illegal insecure pathname
Copy the <Logical_hostname>_<dbname>.bdc file to prefix the physical hostname of the Sun Cluster nodes, instead of the logical hostname. This is required for Client access. In this example, the logical hostname is lhost1 and the physical Sun Cluster nodes are clusterix1 and clusterix2.
# grep PROD.FRM_APPLTOP= /var/tmp/config.txt PROD.FRM_APPLTOP=/global/mnt11/d01/oracle/prodappl # # cd /global/mnt11/d01/oracle/prodappl/fnd/11.5.0/secure # # cp lhost1_prod.dbc clusterix1_prod.dbc # cp lhost1_prod.dbc clusterix2_prod.dbc