This section contains the information you need to plan your Sun Cluster HA for SAP liveCache installation and configuration.
If you have not already done so, read your SAP documentation before you begin planning your Sun Cluster HA for SAP liveCache installation and configuration because your SAP documentation includes configuration restrictions and requirements that are not outlined in Sun Cluster documentation or dictated by Sun Cluster software.
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 liveCache. These requirements apply to Sun Cluster HA for SAP liveCache only. You must meet these requirements before you proceed with your Sun Cluster HA for SAP liveCache installation and configuration.
For requirements that apply to all data services, see Sun Cluster 3.1 Data Service Planning and Administration Guide.
Use an SAP liveCache version 7.4 or higher.
Configure SAP xserver so that SAP xserver starts on all nodes that the liveCache resource can failover to. To implement this configuration, ensure that the nodelist of the SAP xserver resource group and the liveCache resource group contain the same nodes. Also, the value of desired_primaries and maximum_primaries of the SAP xserver resource must be equal to the number of nodes listed in the nodelist parameter of the liveCache resource. For more information, see How to Register and Configure Sun Cluster HA for SAP liveCache.
Use the standard configurations in this section to plan the installation and configuration of Sun Cluster HA for SAP liveCache. Sun Cluster HA for SAP liveCache supports the standard configurations in this section. Sun Cluster HA for SAP liveCache might support additional configurations. However, you must contact your Sun service provider for information on additional configurations.
Figure 1–2 illustrates a four-node cluster with SAP APO Central Instance, APO application servers, a database, and liveCache. APO Central Instance, the database, and liveCache are configured as failover data services. APO application servers and SAP xserver can be configured as scalable or failover data services.
Use the information in this section to plan the installation and configuration of Sun Cluster HA for SAP liveCache. The information in this section encourages you to think about the impact your decisions have on the installation and configuration of Sun Cluster HA for SAP liveCache.
Install liveCache on its own global device group, separate from the global device group for the APO Oracle database and SAP R/3 software. This separate global device group for liveCache ensures that the liveCache resource can depend on the HAStoragePlus resource for liveCache only.
If you want to run SAP xserver as any user other than user root, create that user on all nodes on which SAP xserver runs, and define this user in the Xserver_User extension property. SAP xserver starts and stops based on the user you identify in this extension property. The default for this extension property is user root.
Configure SAP xserver as a failover resource unless you are running multiple liveCache instances that overlap.
Use the questions in this section to plan the installation and configuration of Sun Cluster HA for SAP liveCache. Insert the answers to these questions into the data service worksheets in the Sun Cluster Data Services 3.1 Release Notes. See Configuration Considerations for information that might apply to these questions.
What resource groups will you use for network addresses and application resources and the dependencies between them?
What is the logical hostname (for liveCache resource) for clients that will access the data service?
Where will the system configuration files reside?
See Sun Cluster 3.1 Data Service Planning and Administration Guide for the advantages and disadvantages of placing the liveCache binaries on the local file system as opposed to the cluster file system.