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.
Tables 1–4 and 1–5 show the mount points and acceptable file system types, for example, Local, Failover File System (FFS), or Global File System (GFS).
Table 1–4 Database Tier
Mount Point |
Filesystem Type |
---|---|
<dbname>DATA |
FFS or GFS |
<dbname>DB |
Local, FFS or GFS |
<dbname>ORA |
Local, FFS or GFS |
Table 1–5 Application Tier
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.