Oracle^® Solaris Cluster Data Service for Oracle E-Business Suite up to Release 12.1 Guide

Configuration Restrictions

The configuration restrictions in the subsections that follow apply only to HA for Oracle E-Business Suite up to release 12.1.

---

Caution  -  Your data service configuration might not be supported if you do not observe these restrictions.

---

Restriction for the Supported Configurations of HA for Oracle E-Business Suite up to Release 12.1

The HA for Oracle E-Business Suite up to release 12.1 data service can be configured as a failover service or, when using Concurrent Parallel Processing, as a scalable service.

Oracle E-Business Suite up to release 12.1 can be deployed in the global zone. Oracle E-Business Suite up to release 12.1 is installed by using rapidwiz onto a single-node, two-node or multi-node installation.

• In a single-node installation, you install the Database, Web, Forms, and Concurrent Manager Servers onto a single node.

• In a two-node installation, one node contains the Database and Concurrent Manager Servers, and the other node contains the Forms and Web Servers.

• In a multi-node installation, you can specify any combination of up to five nodes to install the Database, Web, Forms, and Concurrent Manager Servers.

• The following are the components of an Oracle E-Business Suite up to release 12.1 configuration:

  • Database Server – Using rapidwiz, install the Database Server as a single database instance. The Database Server must be managed by Oracle Solaris Cluster HA for Oracle as a failover service in the cluster.

  • Web Server – Using rapidwiz, install the Web Server (Apache) onto a node. If this will run in the cluster, then the Web Server is managed by Oracle Solaris Cluster HA for Apache and can be deployed as either a failover or scalable service in the cluster.

  • Forms and Concurrent Manager Server – Depending on how you install using rapidwiz, you can install the Forms and Concurrent Manager Servers onto the same node or onto different nodes. All of these components are managed by HA for Oracle E-Business Suite up to release 12.1 as a failover service in the cluster.

• Parallel Concurrent Processing – HA for Oracle E-Business Suite up to release 12.1 support for Parallel Concurrent Processing requires a minimum of Oracle E-Business Suite up to release 12.1. When using rapidwiz, you must specify the physical hostnames that will be used within the Parallel Concurrent Processing deployment.

• Clustered Oracle Process Manager and Notification (OPMN) – OPMN is supported with at least Oracle E-Business Suite up to release 12.1. When you use the rapidwiz installer, you must install an OPMN instance as a single Web Entry Point (an HTTP_Server) using a logical host. Other OPMN instances must provide just OC4J services (oafm, forms, and oacore) and must specify the physical hostnames. Refer to MOS Note 380489.1 for more information about setting up a single Web Entry Point OPMN instance.

  The following example shows Clustered OPMN OC4J instances on physical servers pcastor3 and pcastor4, in addition to a single Web Entry Point OPMN instance using logical host ebiz.lh that can fail over between physical servers pcastor3 and pcastor4.

  -bash-3.00$ ./adopmnctl.sh @cluster status
  
  You are running adopmnctl.sh version 120.4.12000000.3
  Checking status of OPMN managed processes in a cluster...
  
  Processes in Instance: PROD_pcastor4.pcastor4.sfbay.com
  -------------------+--------------------+---------+---------
  ias-component      | process-type       |     pid | status
  -------------------+--------------------+---------+---------
  OC4J               | oafm               |   11020 | Alive
  OC4J               | forms              |   10892 | Alive
  OC4J               | oacore             |   10672 | Alive
  HTTP_Server        | HTTP_Server        |     N/A | Down
  
  Processes in Instance: PROD_pcastor3.pcastor3.sfbay.com
  -------------------+--------------------+---------+---------
  ias-component      | process-type       |     pid | status
  -------------------+--------------------+---------+---------
  OC4J               | oafm               |   29657 | Alive
  OC4J               | forms              |   29535 | Alive
  OC4J               | oacore             |   29413 | Alive
  HTTP_Server        | HTTP_Server        |     N/A | Down
  
  Processes in Instance: PROD_ebiz-lh.ebiz-lh.sfbay.com
  -------------------+--------------------+---------+---------
  ias-component      | process-type       |     pid | status
  -------------------+--------------------+---------+---------
  OC4J               | oafm               |     N/A | Down
  OC4J               | forms              |     N/A | Down
  OC4J               | oacore             |     N/A | Down
  HTTP_Server        | HTTP_Server        |   16905 | Alive  

  To implement clustered OPMN within Oracle Solaris Cluster, perform the following steps.

  1. Ensure that each OPMN instance is deployed using a shared file system.

  2. Install or clone the AppsTier Services for the OPMN OC4J instances where each OPMN OC4J instance uses the hostname of the node within the global cluster or the zone node of a zone cluster.

  3. Install or clone the AppsTier Services for the OPMN Web Entry Point instance so that a logical host is used, regardless if the deployment of the OPMN Web Entry Point is within the global cluster or zone cluster. Using the example above, the OPMN Web Entry Point instance PROD_ebiz-lh.ebiz-lh.sfbay.com is deployed using a logical host (ebiz-lh) and can fail over between physical hosts pcastor3 and pcastor4.

  4. Follow Metalink note-id 380489.1, section and subsection 3.1.1 for a Single Web Entry Point. When you use the example above, each OPMN instance context file should define the following context variable as follows.

     <oc4j_cluster_nodes oa_var="s_oc4j_cluster_nodes">pcastor3.sfbay.com:6200,
     pcastor4.sfbay.com:6200,ebiz-lh.sfbay.com:6200</oc4j_cluster_nodes>
     <webentryhost oa_var="s_webentryhost">ebiz-lh</webentryhost>
     <login_page oa_var="s_login_page">http://ebiz-lh.sfbay.com:8000/OA_HTML
     /AppsLogin</login_page>
     <externURL oa_var="s_external_url">http://ebiz-lh.sfbay.com:8000</externURL>

     Refer to Metalink note-id 380489.1 for a description of these context variables and other context variables that can be changed.

  5. When installing or cloning the AppsTier for the OPMN instances, ensure that the OPMN Web Entry Point instance uses different port numbers that are used by the OPMN OC4J instances for ONS-related variables. For example:

     • ons_localport

     • ons_remoteport

     • ons_requestport

     Failing to use different port numbers for the ONS-related variables prevents the OPMN Web Entry Point instance from starting.

Restriction for the Location of Oracle E-Business Suite up to Release 12.1 Files

The Oracle E-Business Suite up to release 12.1 files are the data files that are created when you install Oracle E-Business Suite up to release 12.1 using the rapidwiz installer.

The Oracle E-Business Suite up to release 12.1 files must be placed on shared storage as either a cluster file system or a highly available local file system. The following tables show the mount points and acceptable file system types.