This section contains the information you need to plan your Sun Cluster HA for Oracle E-Business Suite installation and configuration.
The configuration restrictions in the subsections that follow apply only to Sun Cluster HA for Oracle E-Business Suite.
Your data service configuration might not be supported if you do not observe these restrictions.
The Sun Cluster HA for Oracle E-Business Suite data service can only be configured as a failover service.
Oracle E-Business Suite can be deployed in the global zone or non-global zone.
Oracle E-Business Suite is installed 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 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 Sun Cluster HA for Apache and can be deployed as either a failover or scalable service in the 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. All of these components are managed by Sun Cluster HA for Oracle E-Business Suite as a failover service in the cluster.
The Oracle E-Business Suite files are the data files that are created when you install Oracle E-Business Suite using the rapidwiz installer.
The Oracle E-Business Suite 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.
Mount Point |
Filesystem Type |
---|---|
<dbname>DATA |
Cluster file system or highly available file system. |
<dbname>DB |
Local, cluster file system or highly available file system. |
<dbname>ORA |
Local, cluster file system or highly available file system. |
Mount Point |
Filesystem type |
---|---|
<dbname>COMN_TOP |
Cluster file system or highly available file system. |
<dbname>APPL_TOP |
Cluster file system or highly available file system. |
<dbname>APPLCSF |
Cluster file system or highly available file system. |
The configuration requirements in this section apply only to Sun Cluster HA for Oracle E-Business Suite.
If your data service configuration does not conform to these requirements, the data service configuration might not be supported.
Solaris zones provides a means of creating virtualized operating system environments within an instance of the Solaris 10 OS. Solaris zones allow one or more applications to run in isolation from other activity on your system. For complete information about installing and configuring a Solaris Container, refer to System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.
You must determine which Solaris zone Oracle E-Business Suite will use. Oracle E-Business Suite can run within a global zone or non-global zone configuration.