Oracle^® Solaris Cluster Data Service for Oracle E-Business Suite as of Release 12.2 Guide

Installing and Configuring Oracle E-Business Suite 12.2 or Later

This section contains information you need to install and configure Oracle E-Business Suite 12.2 or later. Before proceeding with the installation, refer to the Oracle E-Business Suite documentation and relevant MOS notes that are listed in the References to Oracle E-Business Suite 12.2 or Later section.

Configuration Requirements

The configuration requirements in this section apply only to HA for Oracle E-Business Suite 12.2 or later.

---

Caution  -  If your data service configuration does not conform to these requirements, the data service configuration might not be supported.

---

Configuration Requirements While Installing or Upgrading Oracle E-Business Suite 12.2 or Later

Note the following configuration requirements, if you are installing or upgrading to a new Oracle E-Business Suite 12.2.4 or later system.

• The Primary Applications Node must be installed using an Oracle Solaris Cluster logical host.

• The Apps Base Dir must use a Shared Application Tier File System, such as a Cluster File System or NFS from a NAS storage system. An example is the Oracle ZFS Storage Appliance.

• The Shared Application Tier File System must be managed within Oracle Solaris Cluster by either the SUNW.HAStoragePlus (Cluster File System) or SUNW.ScalMountPoint (NFS) resource type. For more information, see the SUNW.HAStoragePlus(7) and SUNW.ScalMountPoint(7) man pages.

• Furthermore, Applications Nodes must be installed after the system has been upgraded to Oracle E-Business Suite 12.2.4 and AD/TXK C.Delta.6 or later.

Additional Configuration Information

This section describes additional configuration requirements that you must follow while installing or upgrading Oracle E-Business Suite 12.2 or later.

Interpose Logical Host

Symbolic links - You must create the symbolic links as the Primary Applications Node is installed with a logical hostname.

As the root user on each Oracle Solaris Cluster node, create the following symbolic links:

# ln -s /usr/cluster/lib/libschost.so.1 /usr/lib/secure/libschost.so.1
# ln -s /usr/cluster/lib/64/libschost.so.1 /usr/lib/secure/64/libschost.so.1

Environment variables - If you need to source Apps Base Dir/EBSapps.env run|patch for the Primary Applications Node or any Applications Node, that uses an Oracle Solaris Cluster logical host, you must ensure that the following environment variables are set.

As the Oracle E-Business Suite Apps user, set the following environment variables:

$ export SC_LHOSTNAME=logical host
$ export LD_PRELOAD_32=/usr/lib/secure/libschost.so.1
$ export LD_PRELOAD_64=/usr/lib/secure/64/libschost.so.1

In the following command, replace logical host with the Oracle Solaris Cluster logical hostname used for the Primary Applications Node. Replace global_db_name with the entry from the context file.

${INST_TOP}/appl/admin/customglobal_db_name_logical host.env

WebLogic Administrator and APPS User Passwords

The Oracle Solaris Cluster resource type ORCL.ebs needs to retrieve passwords for the WebLogic Administrator and APPS user. These passwords must be saved by issuing the following command as the root user from an Oracle Solaris Cluster node. For the WebLogic Administrator password, provide the WebLogic Administrator password when prompted to enter a string value.

# /usr/cluster/bin/clpstring create -b db_name -t resource global_db_name_WLS
Enter string value: 
Enter string value again: 
#

For the APPS password, provide the APPS password when prompted to enter a string value. In the following command, replace global_db_name with the entry from the context file.

# /usr/cluster/bin/clpstring create -b db_name -t resource global_db_name_APPS 
Enter string value: 
Enter string value again: 
#

Online Patching

# /usr/cluster/bin/clzc reboot -w <zone-cluster>

# /usr/cluster/bin/clzc reboot <zone-cluster>

Whenever an online patch is being applied, before running the cutover phase you must stop all Oracle E-Business Suite services using Oracle Solaris Cluster commands.

For example:

# /usr/cluster/bin/clresource disable resource

Furthermore, before running the cutover phase, ensure that all Oracle E-Business Suite services are stopped on the Primary Applications Node and any further Secondary Application Nodes. Once verified, you must manually start the Primary Applications Node Manager and WebLogic Admin Server on the node that is hosting the Primary Applications Node Oracle Solaris Cluster logical host.

For example:

root@node1:~# clrs status ebs-fo-lh-rs 

=== Cluster Resources ===

Resource Name       Node Name      State        Status Message
-------------       ---------      -----        --------------
ebs-fo-lh-rs        node2	         Offline      Offline - LogicalHostname offline.
                    node1          Online       Online - LogicalHostname online.

root@node1:~#
root@node1:~# su - <applmgr>
Oracle Corporation      SunOS 5.11      11.3    July 2017
You have new mail.
-bash-4.4$
-bash-4.4$ export LD_PRELOAD_32=/usr/lib/secure/libschost.so.1
-bash-4.4$ export LD_PRELOAD_64=/usr/lib/secure/64/libschost.so.1
-bash-4.4$ export SC_LHOSTNAME=<Primary Applications Node logical host>
-bash-4.4$ 
-bash-4.4$ . <Apps Base Dir>/EBSapps.env run
-bash-4.4$ 
-bash-4.4$ $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh start
-bash-4.4$ 
-bash-4.4$ $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

When executing the cutover phase, you must specify the mtrestart=no parameter.

For example:

$ adop phase=cutover mtrestart=no

Once the cutover phase has completed successfully, the Primary Applications Node Manager and WebLogic Admin Server will have been stopped by the cutover session. It will then be possible to start all Oracle E-Business Suite services again using Oracle Solaris Cluster commands.

For example:

# /usr/cluster/bin/clresource enable resource