Your data service configuration might not be supported if you do not adhere to these requirements.
Use the requirements in this section to plan the installation and configuration of Sun Cluster HA for SAP. These requirements apply to Sun Cluster HA for SAP only. You must meet these requirements before you proceed with your Sun Cluster HA for SAP installation and configuration.
For requirements that apply to all data services, see “Planning for Sun Cluster Data Services” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
After you create all of the file systems for the database and for SAP software, create the mount points, and put the mount points in the /etc/vfstab file on all of the cluster nodes – See the SAP installation guides, Installation of the SAP R/3 on UNIX and R/3 Installation on UNIX-OS Dependencies, for details on how to set up the database and SAP file systems.
Create the required groups and users on all of the cluster nodes – See the SAP installation guides, Installation of the SAP R/3 on UNIX and R/3 Installation on UNIX-OS Dependencies, for details on how to create SAP groups and users.
Configure Sun Cluster HA for NFS on the cluster that hosts the central instance if you plan to install some external SAP application servers – See Sun Cluster Data Service for Network File System (NFS) Guide for Solaris OS for details on how to configure Sun Cluster HA for NFS.
Install application servers on either the same cluster that hosts the central instance or on a separate cluster – If you install and configure any application server outside of the cluster environment, Sun Cluster HA for SAP does not perform fault monitoring and does not automatically restart or fail over those application servers. You must manually start and shut down application servers that you install and configure outside of the cluster environment.
Use an SAP software version with automatic enqueue reconnect mechanism capability – Sun Cluster HA for SAP relies on this capability. SAP 4.0 software with patch information and later releases should have automatic enqueue reconnect mechanism capability.