This section contains the information you need to plan your HA for SAP liveCache installation and configuration.
Caution - 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 HA for SAP liveCache. These requirements apply to HA for SAP liveCache only. You must meet these requirements before you proceed with your HA for SAP liveCache installation and configuration.
For requirements that apply to all data services, see Planning and Administering Data Services for Oracle Solaris Cluster 4.4.
Use the standard configurations in this section to plan the installation and configuration of HA for SAP liveCache. HA for SAP liveCache supports the standard configurations in this section. HA for SAP liveCache might support additional configurations. However, you must contact your Oracle service provider for information on additional configurations.
Four-Node Cluster 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. SAP xserver can be configured only as a multiple master data service. APO application servers can be configured as scalable or failover data services.
Figure 2 Four-Node Cluster
Use the information in this section to plan the installation and configuration of 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 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.
Use the questions in this section to plan the installation and configuration of HA for SAP liveCache. 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 Planning and Administering Data Services for Oracle Solaris Cluster 4.4 for the advantages and disadvantages of placing the liveCache binaries on the local file system as opposed to the cluster file system.