Sun Cluster Data Service for Oracle E-Business Suite Guide for Solaris OS

ProcedureHow to Install and Configure Oracle E-Business Suite

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

  1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.

  2. Determine which Solaris zone to use.

    Refer to Determine which Solaris zone Oracle E-Business Suite will use for more information.

  3. If a zone will be used, create the zone.

    Refer to System Administration Guide: Solaris Containers-Resource Management and Solaris Zones for complete information about installing and configuring a zone.

  4. If a zone is being used, ensure the zone is booted.

    Repeat this step on all nodes of the cluster if a zone is being used.

    Boot the zone if it is not running.


    # zoneadm list -v
    # zoneadm -z zonename boot
    
  5. Create a cluster file system or highly available local file system for the Oracle E-Business Suite files.

    Refer to Sun Cluster Software Installation Guide for Solaris OS for information about creating a cluster file system and to Sun Cluster Data Services Planning and Administration Guide for Solaris OS for information about creating a highly available local file system.

  6. Mount the highly available local file system.

    Perform this step from the global zone on one node of the cluster.

    1. If a non ZFS highly available local file system is being used for Oracle E-Business Suite.

      Ensure the node has ownership of the disk set or disk group.

      For Solaris Volume Manager.


      # metaset -s disk-set -t
      

      For Veritas Volume Manager.


      # vxdg -C import disk-group
      # vxdg -g disk-group startall
      
      1. If the global zone is being used for Oracle E-Business Suite.


        # mount highly-available-local-filesystem
        
      2. If a zone is being used for Oracle E-Business Suite.

        Create the mount point on all 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
        
    2. If a ZFS highly available local file system is being used for Oracle E-Business Suite.

      1. If the global zone is being used for Oracle E-Business Suite.


        # zpool import -R / HAZpool
        
      2. If a zone is being used for Oracle E-Business Suite.


        # zpool export -f HAZpool
        # zpool import -R /zonepath/root HAZpool
        
  7. Plumb the Oracle E-Business Suite logical hostname.

    Perform this step in the global zone on one node of the cluster for each logical hostname being used by Oracle E-Business Suite.

    1. If the global zone is being used for Oracle E-Business Suite.


      # ifconfig interface addif logical-hostname up
      
    2. If a zone is being used for Oracle E-Business Suite.


      # ifconfig interface addif logical-hostname up zone zonename
      
  8. 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 a symbolic link from

    /usr/lib/secure/libschost.so.1 to /usr/cluster/lib/libschost.so.1

    On all cluster nodes where Oracle E-Business Suite will run.


    # cp /usr/cluster/lib/libschost.so.1 /usr/lib/libschost.so.1
    # cd /usr/lib/secure
    # ln -s /usr/lib/libschost.so.1 libschost.so.1
    
  9. Install the Oracle E-Business Suite software.

    Perform this step in the global zone or zone on one node of the cluster.

    1. As root, execute rapidwiz.

      When running rapidwiz 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.

      When executing rapidwiz save the config.txt file in a permanent location, for example /var/tmp/config.txt. This will be required for the next step.


      # cd oracle-ebusiness-suite-install-directory
      # ./rapidwiz
       
      
    2. As root, execute rapidwiz for each logical hostname.

      Executing rapidwiz for each logical hostname that you entered when generating /var/tmp/config.txt.


      # cd oracle-ebusiness-suite-install-directory
      # ./rapidwiz -servername logical-hostname
       
      
  10. (Optional) Resolving 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 the steps below to resolve the validation error. Afterwards you must return to the rapidwiz GUI to retry the validation.

    1. Edit httpd_pls.conf.

      Edit httpd_pls.conf and add the following entries for each physical cluster nodes 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 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>
    2. Edit oprocmgr.conf.

      Edit oprocmgr.conf and add the following entries for each physical cluster nodes 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>
    3. Edit jserv.properties.

      Edit jserv.properties and add the following entries for all physical cluster nodes 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
      
    4. 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
      
    5. Return to the rapidwiz GUI.

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

  11. Post Oracle E-Business Suite Installation, edit listener.ora.

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

    Edit listener.ora 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>/<sid>ora/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>/<sid>ora/8.0.6 \
    /lib,LD_PRELOAD_32=/usr/lib/secure/libschost.so.1,SC_LHOSTNAME=lhost1,MYAPPS=
  12. Stop Oracle E-Business Suite.

    Perform this step from the global zone or zone where you installed 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
    
  13. Unmount the highly available local file system.

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

    1. If a non ZFS highly available local file system is being used for the Oracle E-Business Suite.

      1. If the global zone is being used for Oracle E-Business Suite.


        # umount highly-available-local-filesystem
        
      2. If a zone is being used for Oracle E-Business Suite.


        # umount /zonepath/root/highly-available-local-filesystem
        
    2. If a ZFS highly available local file system is being used for Oracle E-Business Suite.


      # zpool export -f HAZpool
      
  14. 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