This section contains the procedures you need to install and configure Oracle E-Business Suite up to release 12.1.
For Oracle E-Business Suite software starting with release 12.2, follow procedures in Oracle Solaris Cluster Data Service for Oracle E-Business Suite as of Release 12.2 Guide .
This section contains the procedures you need to install and configure Oracle E-Business Suite up to release 12.1.
Refer to Determine Which Oracle Solaris Zone Oracle E-Business Suite up to Release 12.1 Will Use for more information.
Refer to Introduction to Oracle Solaris Zones for complete information about installing and configuring a zone.
Refer to Oracle Solaris Cluster 4.3 Software Installation Guide for information about creating a cluster file system and to Oracle Solaris Cluster 4.3 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.
# metaset -s disk-set -t
# mount highly-available-local-filesystem
# zpool import -R / HAZpool
Perform this step in the global zone on one node of the cluster for each logical hostname being used by Oracle E-Business Suite up to release 12.1.
# 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.
Perform this step on all cluster nodes where Oracle E-Business Suite up to release 12.1 will run.
To provide logical host interpositioning for Oracle E-Business Suite up to release 12.1, you must create the following symbolic links:
# cd /usr/lib/secure # ln -s /usr/cluster/lib/libschost.so.1 libschost.so.1 # cd /usr/lib/secure/sparcv9 # ln -s /usr/cluster/lib/sparcv9/libschost.so.1 libschost.so.1
If you are installing at least Oracle E-Business Suite up to release 12.1, perform the following steps:
# su - oraapp-user # pfedit app-base directory/apps/apps st/appl/customSID_app-logical-host.env
LD_PRELOAD_32=/usr/lib/secure/libschost.so.1 LD_PRELOAD_64=/usr/lib/secure/64/libschost.so.1 SC_LHOSTNAME=app-logical-host export LD_PRELOAD_32 LD_PRELOAD_64 SC_LHOSTNAME
# su - oraapp-user # . app-base_directory/apps/apps_st/appl/customSID_app-logical-host.env # hostname # uname -n
The hostname and uname -n commands should return the value that was set for the environment variable SC_LHOSTNAME.
Perform this step in the 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 up to release 12.1, 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
Perform this step from the global zone where you installed Oracle E-Business Suite up to release 12.1.
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
Perform this step from the global zone on the node where you installed Oracle E-Business Suite up to release 12.1.
# umount 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 up to release 12.1.
# ifconfig interface removeif logical-hostname