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, become superuser or 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 zone will be used, create the zone.
Refer to System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones for complete information about installing and configuring a zone.
If a non-global zone is being used, ensure that the non-global zone is booted.
1. Boot the non-global zone if it is not running.
```
# zoneadm list -v
# zoneadm -z zonename boot
```
2. Repeat this step on all nodes of the cluster if a non-global zone is being used.
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 one of the following steps.
  Note - Ensure that the node has ownership of the disk set or disk group.
  - For Solaris Volume Manager, type:
```
# metaset -s disk-set -t
```
  - For Veritas Volume Manager, type:
```
# vxdg -C import disk-group
# vxdg -g disk-group startall
```
  - If the global zone is being used for Oracle E-Business Suite, type the following command.
```
# mount highly-available-local-filesystem
```
  - If a non-global zone is being used for Oracle E-Business Suite, create the mount point on all non-global zones of the cluster that are being used for Oracle E-Business Suite.
```
# zlogin zonename mkdir highly-available-local-filesystem
```
    Mount the highly available local file system on one of the zones being used.
```
# mount -F lofs highly-available-local-filesystem \
> /zonepath/root/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
```
  - If a non-global zone is being used for Oracle E-Business Suite, type the following command.
```
# zpool export -f HAZpool
# zpool import -R /zonepath/root 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 zone is being used for Oracle E-Business Suite, type the following command.
```
# ifconfig interface addif logical-hostname up zone zonename
```
Enable logical host interpositioning.
Note - If you are using Parallel Concurrent Processing, omit this step. Parallel Concurrent Processing requires physical hostnames.

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 a symbolic link from /usr/lib/secure/libschost.so.1 to /usr/cluster/lib/libschost.so.1
```
# cd /usr/lib/secure
# ln -s /usr/cluster/lib/libschost.so.1 libschost.so.1
```
Install the Oracle E-Business Suite software.
Perform this step in the global zone or non-global zone on one node of the cluster.
1. As superuser, execute rapidwiz.
  When running rapidwiz, unless you are installing Parallel Concurrent Processing, 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.
  When executing rapidwiz, save the config.txt file in a permanent location, for example, /var/tmp/config.txt. If you are installing Oracle E-Business Suite version 12 or later, 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 superuser, 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
 
```

(Optional) If encountered, resolve validation error JSP is not responding, waiting 15 seconds and retesting.

If, after installing the Web Server, you encounter the validation error JSP is not responding, waiting 15 seconds and retesting, leave the rapidwiz GUI and follow Step a through Step e to resolve the validation error. Then you must return to the rapidwiz GUI to retry the validation.

Edit the httpd_pls.conf file.

Edit the httpd_pls.conf file and add the following entries for each physical cluster node within the VirtualHost _default_:* section.

Allow from cluster-node
Allow from cluster-node.fqdn

# su - oraapp-user
$ cd base-directory/sidora/iAS/Apache/Apache/conf
$ vi httpd_pls.conf
$ exit

The following example shows the logical hostname lhost1 and the cluster nodes clnode1 and clnode2 that have been added.

<VirtualHost _default_:*>
  <Location />
    Order deny,allow
    Deny from all
    Allow from localhost
    Allow from lhost1
    Allow from lhost1.example.com
    Allow from clnode1
    Allow from clnode1.example.com
    Allow from clnode2
    Allow from clnode2.example.com
  </Location>
</VirtualHost>

Edit the oprocmgr.conf file.

Edit the oprocmgr.conf file and add the following entries for each physical cluster node within the VirtualHost _default_:8100 section.

Allow from cluster-node
Allow from cluster-node.fqdn

# su - oraapp-user
$ cd base-directory/sidora/iAS/Apache/Apache/conf
$ vi oprocmgr.conf
$ exit

The following example shows logical hostname lhost1 and the cluster nodes clnode1 and clnode2 that have been added.

<IfModule mod_oprocmgr.c>
   Listen 8000
   ProcNode lhost1.example.com 8100

  <VirtualHost _default_:8100>
<IfDefine SSL>
     SSLEngine off
</IfDefine>
     Port 8100
     <Location />
       Order Deny,Allow
       Deny from all
       Allow from localhost
       Allow from lhost1
       Allow from lhost1.example.com
       Allow from clnode1
       Allow from clnode1.example.com
       Allow from clnode2
       Allow from clnode2.example.com
     </Location>/base-directory/sidappl/admin/SID_lhost1.xml
     <Location /oprocmgr-service>
       SetHandler oprocmgr-service
     </Location>
     <Location /oprocmgr-status>
       SetHandler oprocmgr-status
     </Location>
   </VirtualHost>
</IfModule>

Edit the jserv.properties file.

Edit the jserv.properties file and add the following entries for all physical cluster node within the security.allowedAddresses entry.

security.allowedAddresses=127.0.0.1, \
lhost.fqdn,clnode1.fqdn,clnode2.fqdn

# su - oraapp-user
$ cd base-directory/sidora/iAS/Apache/Jserv/etc
$ vi jserv.properties
$ exit

The following example shows logical hostname lhost1 and the cluster nodes clnode1 and clnode2 that have been added.

security.allowedAddresses=127.0.0.1,lhost1.example.com,clnode1.example.com,clnode2.example.com

Restart Oracle E-Business Suite.

# su - oraapp-user
$ cd base-directory/sidcomn/admin/scripts/SID_logical-hostname
$ ./adstpall.sh apps/apps
$ exit
# su - oradb-user
$ cd base-directory/siddb/9.2.0/appsutil/scripts/SID_logical-hostname
$ ./addlnctl.sh stop SID
$ ./addbctl.sh stop immediate
$ ./addbctl.sh start
$ ./addlnctl.sh start SID
$ exit
# su - oraapp-user
$ cd base-directory/sidcomn/admin/scripts/SID_logical-hostname
$ ./adstrtal.sh apps/apps
$ exit

Return to the rapidwiz GUI and click Retry.
The JSP check should now work.

When Oracle E-Business Suite installation is complete, edit listener.ora.

Note - If you are using Parallel Concurrent Processing, omit this step. Parallel Concurrent Processing requires physical hostnames.

Perform this step from the global zone or non-global zone where you installed Oracle E-Business Suite.

If you are installing Oracle E-Business Suite version 12 or later, perform the following steps.

Create a customSID_app-logical-host.env file.

# su - oraapp-user
$ vi app-base_directory/apps/apps_st/appl/customSID_app-logical-host.env

Add the following lines to the customSID_app-logical-host.env file:

LD_PRELOAD_32=/usr/lib/secure/libschost.so.1 SC_LHOSTNAME=app-logical-host export LD_PRELOAD_32 SC_LHOSTNAME

If you are installing Oracle E-Business Suite version 11.5.10 or earlier, edit the listener.ora file and add the following entries to the envs= parameter for the SID_NAME=FNDSM entry.

envs='LD_LIBRARY_PATH=/usr/dt/lib:/user/openwin/lib:basedir/sidora/8.0.6/lib, \ LD_PRELOAD_32=/usr/lib/secure/libschost.so.1,SC_LHOSTNAME=lhost,MYAPPSORA=...

# su - oraapp-user
$ cd base-directory/sidora/8.0.6/network/admin/SID_logical-hostname
$ vi listener.ora

The following example shows the LD_PRELOAD_32 and SC_LHOSTNAME entries that have been added.

SID_LIST_APPS_PROD =
  (SID_LIST =
   ( SID_DESC = ( SID_NAME = FNDSM )
      ( ORACLE_HOME = /base-directory/sidora/8.0.6 )
      ( PROGRAM = /base-directory/sidappl/fnd/11.5.0/bin/FNDSM )
      ( envs='LD_LIBRARY_PATH=/usr/dt/lib:/user/openwin/lib:basedir/sidora/8.0.6 \ /lib,LD_PRELOAD_32=/usr/lib/secure/libschost.so.1,SC_LHOSTNAME=lhost1,MYAPPS=

Stop Oracle E-Business Suite.
Perform this step from the global zone or non-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 are installing Oracle E-Business Suite version 12 or later, 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
```
- If you are installing Oracle E-Business Suite version 11.5.10 or earlier, type the following commands.
```
# su - oraapp-user
$ cd app-base-directory/SIDcomn/admin/scripts/SID_app-logical-hostname
$ ./adstpall.sh apps/apps
$ exit
# su - oradb-user
$ cd db-base-directory/SID/db/9.2.0/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 non-global zone is being used for Oracle E-Business Suite, type the following command.
```
# umount /zonepath/root/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