This section contains the information you need to plan your Sun Cluster HA for Oracle E-Business Suite installation and configuration.
This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for Oracle E-Business Suite only.
Your data service configuration might not be supported if you do not observe these restrictions.
For restrictions that apply to all data services, see the Sun Cluster Release Notes.
Sun Cluster HA for Oracle E-Business Suite data service deployment – Consists of three components, Forms Server, Concurrent Manager Server and Reports Server. These components are installed using the Rapid Wizard Installation tool (rapidwiz).
You can install Oracle E-Business Suite using rapidwiz onto a single-node, two-node or multi-node installation.
In a single-node installation, you install the Database, Web, Forms, Concurrent Manager, and Reports Server onto a single node.
In a two-node installation, one node contains the Database, Concurrent Manager and Reports server; and the other node contains the Forms and Web Server.
In a multi-node installation, you can specify any combination of up to five nodes to install the Database, Web, Forms, Concurrent Manager, and Reports Server.
Database Server – Using rapidwiz, install the Database Server as a single database instance. The Database Server must be managed by Sun Cluster HA for Oracle as a failover service with Sun Cluster.
Web Server – Using rapidwiz, install the Web Server (Apache) onto a node. If this will run in Sun Cluster, then the Web Server is managed by Sun Cluster HA for Apache and can be deployed as either a failover or scalable service within Sun Cluster.
Forms, Concurrent Manager and Reports Server — Depending on how you install using rapidwiz, you can install the Forms, Concurrent Manager and Reports Server onto the same node or onto different nodes. However, all these components can be managed only by Sun Cluster HA for Oracle E-Business Suite as a failover service within Sun Cluster.
Installing Oracle E-Business Suite onto Cluster File Systems — When installing Oracle E-Business Suite using rapidwiz, you must adhere to these restrictions.
The following tables show the mount points and acceptable file system types, for example, Local, Failover File System (FFS), or Global File System (GFS).
Mount Point |
Filesystem Type |
---|---|
<dbname>DATA |
FFS or GFS |
<dbname>DB |
Local, FFS or GFS |
<dbname>ORA |
Local, FFS or GFS |
Mount Point |
Filesystem type |
---|---|
<dbname>COMN_TOP |
FFS or GFS |
<dbname>APPL_TOP |
FFS or GFS |
<dbname>APPLCSF |
FFS or GFS |
It is considered best practice when mounting Global File Systems to mount them with the /global prefix and to mount Failover File Systems with the /local prefix.
These requirements in this section apply to Sun Cluster HA for Oracle E-Business Suite only. You must meet these requirements before you proceed with your Sun Cluster HA for Oracle E-Business Suite installation and configuration.
Your data service configuration might not be supported if you do not adhere to these requirements.
Oracle E-Business Suite components and their dependencies – You can configure the Sun Cluster HA for Oracle E-Business Suite data service to protect an Oracle E-Business Suite instance and its respective components. These components and their dependencies are described.
If every case, the SUNW.HAStoragePlus resource manages the Oracle E-Business Suite File System Mount points and ensures that Oracle E-Business Suite is not started until these are mounted.
Component |
Description |
---|---|
Forms Server |
-> SUNW.HAStoragePlus resource |
Concurrent Manager Listener |
-> SUNW.HAStoragePlus resource |
Concurrent Manager Server |
-> SUNW.HAStoragePlus resource -> Concurrent Manager Listener resource -> Oracle Database Server resource |
Reports Server |
-> SUNW.HAStoragePlus resource |
As shown in Table 4 the Concurrent Manager Server is dependent on the Oracle Database Server. If you choose the Rapid Install single-node or two-node installation method, then the Database and Concurrent Manager will be within the same node (Resource Group).
If you choose multi-node, then you might have installed the Database Server and Concurrent Manager Server on different nodes (Resource Groups). To preserve the dependency listed above, the Sun Cluster HA for Oracle E-Business Suite data service manages the start/restart dependencies between the Concurrent Manager Server and Database Server.
Each Oracle E-Business Suite component has a configuration and registration file in /opt/SUNWscebs/xxx/util, where xxx is a three-character abbreviation for the respective Oracle E-Business Suite component. These files allow you to register the Oracle E-Business Suite components with Sun Cluster.
Within these files, the appropriate dependencies have been applied.
# cd /opt/SUNWscebs # # ls -l cmg/util total 16 -rwxr-xr-x 1 root sys 1410 Jun 11 17:17 cmg_config -rwxr-xr-x 1 root sys 840 Jun 11 17:17 cmg_register -rwxr-xr-x 1 root sys 4105 Jun 11 17:17 copy_env # ls -l frm/util total 4 -rwxr-xr-x 1 root sys 701 Jun 11 17:17 frm_config -rwxr-xr-x 1 root sys 619 Jun 11 17:17 frm_register # ls -l rep/util total 4 -rwxr-xr-x 1 root sys 701 Jun 11 17:17 rep_config -rwxr-xr-x 1 root sys 619 Jun 11 17:17 rep_register # more cmg/util/cmg* :::::::::::::: cmg_config :::::::::::::: # # Copyright 2003 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # This file will be sourced in by cmg_register and the parameters # listed below will be used. # # These parameters can be customized in (key=value) form # # RS - name of the resource for the application # RG - name of the resource group containing RS # HAS_RS - name of the HAStoragePlus SC resource # LSR_RS - name of the Concurrent Manager Listener SC resource # CON_HOST - name of the Concurrent Manager logical hostname # CON_COMNTOP - name of the Concurrent Manager COMMON_TOP directory # CON_APPSUSER - name of the Concurrent Manager application userid # APP_SID - name of the application SID # APPS_PASSWD - name of the password for the APPS userid # ORACLE_HOME - name of the Oracle home directory # CON_LIMIT - Minimum number of Concurrent Managers # represented as a percentage i.e. 70 = 70% # (Note - Omit the % sign) # MODE - Specifies if Oracle E-Business Suite is running # 32|64-bit code and if the LD_PRELOAD pathname # will have a symlink in /usr/lib/secure # Default value = 32/Y # (Note - Refer to the Sun Cluster 3.1 Data Service # for Oracle E-Business Suite for more information) # RS= RG= HAS_RS= LSR_RS= CON_HOST= CON_COMNTOP= CON_APPSUSER= APP_SID= APPS_PASSWD= ORACLE_HOME= CON_LIMIT= MODE=32/Y :::::::::::::: cmg_register :::::::::::::: # # Copyright 2003 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # . `dirname $0`/cmg_config scrgadm -a -j $RS -g $RG -t SUNW.gds \ -x Start_command="/opt/SUNWscebs/cmg/bin/start_cmg \ -R $RS -G $RG -C $CON_COMNTOP -U $CON_APPSUSER -P $APPS_PASSWD \ -S $APP_SID -H $CON_HOST -O $ORACLE_HOME -L $CON_LIMIT -M $MODE" \ -x Stop_command="/opt/SUNWscebs/cmg/bin/stop_cmg \ -R $RS -G $RG -C $CON_COMNTOP -U $CON_APPSUSER -P $APPS_PASSWD \ -S $APP_SID -H $CON_HOST -O $ORACLE_HOME -L $CON_LIMIT -M $MODE" \ -x Probe_command="/opt/SUNWscebs/cmg/bin/probe_cmg \ -R $RS -G $RG -C $CON_COMNTOP -U $CON_APPSUSER -P $APPS_PASSWD \ -S $APP_SID -H $CON_HOST -O $ORACLE_HOME -L $CON_LIMIT -M $MODE" \ -y Port_list=23/tcp -y Network_resources_used=$LSR_RS \ -x Stop_signal=9 \ -y Resource_dependencies=$HAS_RS,$LSR_RS # |