Installing and Configuring Oracle E-Business Suite 12.2 or Later

Language:

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 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. For example, 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(5) and SUNW.ScalMountPoint(5) 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.

Note - The Primary Applications Node will host the WebLogic Administration Server that is required when patching Oracle E-Business Suite 12.2. As such, installing the Primary Applications Node on an Oracle Solaris Cluster logical host provides high availability for the WebLogic Administration Server if a node failure occurs.

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

Note - You must ensure that the customglobal_db_name_logical host.env is created on the run and patch file system. You must also add those environment variables to the following file for the Primary Applications Node or any Applications Tier Node, that uses an Oracle Solaris Cluster logical host.

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

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

For example:

# /usr/cluster/bin/clresource disable resource

When executing the cutover phase, you must specify the mtrestart=no parameter and then manually start the Oracle E-Business Suite services using the Oracle Solaris Cluster commands.

For example:

$ adop phase=cutover mtrestart=no

Once the cutover phase has completed successfully, start the Oracle Solaris Cluster resources.

# /usr/cluster/bin/clresource enable resource