SGeSAP Product Files

All the files that are available after the installation of SGeSAP can be found in /opt/cmcluster/sap. The files that are installed are:

The standard SGeSAP run-time functions and configurable functions repository container in /opt/cmcluster/sap:
sap.functions—contains standard SAP R/3 functions. Do not edit this file!
customer.functions—contains functions that can be modified for special setups.
The run-time configuration options and control logic in /opt/cmcluster/sap/SID:
sap.conf—contains configuration and options for SGeSAP
sapci.cntl—contains SAP R/3 specific control logic for two package configurations
sapdb.cntl—contains database specific control logic for two package configurations
sapdbci.cntl—contains database and SAP R/3 specific control logic for one package configurations
sapap.cntl—contains the Application specific control logic for an application server package
startdb.sql—contains SQL sample that has to be merged into the SAP "startdb" script.
The /opt/cmcluster/CCmon directory contains the file needed for the setup of the Cluster Consitancy monitor for SGeSAP. Refer to Cluster Consitancy Chapter within this documentation for more details.

Figure 1-8 “Configuration Files” shows that the configuration files are used as input for the standard MC/ServiceGuard cmapplyconf command to generate the cmclconfig file that is used to manage the cluster.

Figure 1-8 Configuration Files

The SGeSAP files work in tandem with standard MC/ServiceGuard files to monitor the health of the cluster and packages, and to move packages to another node in case of failure. Figure 1-9 “Control Files Containing Run-time Logic” shows the relationship between the standard MC/ServiceGuard files and the SGeSAP scripts and control logic.

Figure 1-9 Control Files Containing Run-time Logic

SGeSAP and SCM High Availability - APO/LiveCache Configuration

SGeSAP supports customers who choose to run their Supply Chain Management (SCM) systems in a High Available system environment.

The SAP SCM environment consists of two systems: the APO system and the LiveCache. Considering only the database and application server, an APO system looks like an standard R/3 system. It uses the same basic technology like R/3 (kernel, databases, executables) but with different business logic.

Additional components like the liveCache and optimization server further enhance the system. The liveCache server consists of an SAP database running in memory. Disk space is required to host the operating system of the node while liveCache is running, pagefiles, executables and dev spaces for an filesystem image of a consistent DB image.

Figure 1-10 “3 Node SGeSAP Cluster for APO/LiveCache” illustrates a sample LiveCache scenario:

Figure 1-10 3 Node SGeSAP Cluster for APO/LiveCache

The LiveCache package is required to run on a separate server. Therefore the 3-node cluster is an appropriate setup to run a customer SCM system in a high available environment. The adoptive node that can run an additional Application server or a development system under normal condition is able to run either the LiveCache-package or the APO-package in case of a system failure. The additional APO Application-server or a development system will be shut down in case of a failover.Additonal scenarios are a four node cluster where both LiveCache primary and APO primary node have a dedicated backup node each. The requirement is that the LiveCache package always runs on a node where no other application, such as a database or an additional SAP system is running.Setting up the APO package in SGeSAP is standard as the APO is based on a standard R/3 kernel. For details about the setup of a liveCache package refer to the step by step installation guide in chapter 2 "SGeSAP configuration for SCM High Availability - APO/LiveCache" of this book.




	NOTE: For all High Availability configurations of APO and LiveCache it is required to follow SAP's latest recommendations and requirements. Check all SAP OSS notes and appropriate documentation regarding HA scenarios and Recovery for APO/LiveCache before setting up a HA scenario for APO / LiveCache! Configuring a HA LiveCache system requires some additional task that differ from a standard R/3 configuration. The APO system itself can be treated as an additional SAP R/3 system and therefore can be configured in SGeSAP using the standard installation steps. The LiveCache concept described in this documenatation is based on the SAP documentation "LiveCache and High Availability on Unix platforms" and "Backup and Recovery for APO 3.0". It is recommended to follow these documents before configuring LiveCache with the SGeSAP.

SGeSAP Product Files

Technical documentation

» Table of Contents

» Index

SGeSAP and SCM High Availability - APO/LiveCache Configuration