Installing and Configuring Oracle E-Business Suite

This section contains the procedures you need to install and configure Oracle E-Business Suite.

How to Install and Configure Oracle E-Business Suite

This section contains the procedures you need to install and configure Oracle E-Business Suite.

On a cluster member, assume a role that provides solaris.cluster.modify RBAC authorization.
Determine which Solaris zone to use.
Refer to Determine Which Solaris Zone Oracle E-Business Suite Will Use for more information.
If a Solaris zone will be used, create the zone.
Refer to Oracle Solaris 11.1 Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management for complete information about installing and configuring a zone.
Create a cluster file system or highly available local file system for the Oracle E-Business Suite files.
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.
Mount the highly available local file system.
Perform this step from the global zone on one node of the cluster.
- If a non-ZFS highly available local file system is being used for Oracle E-Business Suite, perform the following step.
  Note - Ensure that the node has ownership of the disk set or disk group.
  - For Solaris Volume Manager, type:
```
# metaset -s disk-set -t
```
  - If the global zone is being used for Oracle E-Business Suite, type the following command.
```
# mount highly-available-local-filesystem
```
- If a ZFS highly available local file system is being used for Oracle E-Business Suite, perform one of the following steps.
  - If the global zone is being used for Oracle E-Business Suite, type the following command.
```
# zpool import -R / HAZpool
```
Plumb the Oracle E-Business Suite logical hostname.
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.
- If the global zone is being used for Oracle E-Business Suite, type the following command.
```
# ifconfig interface addif logical-hostname up
```
- If a Solaris zone is being used for Oracle E-Business Suite, type the following command.
```
# 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.
Enable logical host interpositioning.
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 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 Version 12, perform the following steps:
1. Create a customSID_app-logical-host.env file.
```
# su - oraapp-user
# vi app-base directory/apps/apps st/appl/customSID_app-logical-host.env
```
2. Add the following lines to the customSID_app-logical-host.env file:
```
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
```
3. Test the setup of the logical host interpositioning.
```
# 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.
Install the Oracle E-Business Suite software.
Perform this step in the global zone on one node of the cluster.
1. As the root role, execute rapidwiz.
  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
 
```
2. As the root role, execute rapidwiz for each logical hostname.
  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
 
```
Stop Oracle E-Business Suite.
Perform this step from the 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.
- For Oracle E-Business Suite Version 12, type the following commands.
```
# 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
```
Unmount the highly available local file system.
Perform this step from the global zone on the node where you installed Oracle E-Business Suite.
- To unmount a non-ZFS highly available local file system that is being used for the Oracle E-Business Suite, perform one of the following steps.
  - If the global zone is being used for Oracle E-Business Suite, type the following command.
```
# umount highly-available-local-filesystem
```
- If a ZFS highly available local file system is being used for Oracle E-Business Suite, type the following command.
```
# zpool export -f HAZpool
```
Unplumb the Oracle E-Business Suite logical hostname.
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
```

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Data Service for Oracle E-Business Suite Guide Oracle Solaris Cluster 4.1