United States-English

Managing MC/ServiceGuard Extension for SAP R/3:

Chapter 1 Understanding MC/ServiceGuard Extension for SAP

»

Technical documentation


	Complete book in PDF


»	Feedback

» Table of Contents

» Index

Table of Contents

Overview of SGeSAP

One-Package Configuration Model
Two-Package Configuration Model

Application Servers

SAP Application Server Packages

Highly Available NFS

Directory Structures

Common Directories that are Kept Locally
Directories that Reside on Shared Disks
Directories that are Handled by the Automounter

SAP R/3 Local Executables

MC/ServiceGuard Package Concepts

Extension Files for the One Package Model
Extension Files For the Two-Package Model

SGeSAP and HP Somersault

HP Somersault Machine Sets

Server Consolidation

Dialog Instance Handling
Shared Memory Resource Handling

SGeSAP Product Files

SGeSAP and SCM High Availability - APO/LiveCache Configuration

Cluster Consistency Monitor for SGeSAP Environments

Why Cluster Consistency Monitor is Needed
Features of the Cluster Consistency Monitor for SGeSAP Environments
Installation and Setup of the Cluster Consistency Monitor

Metropolitan Clusters and SGeSAP

What is a Metropolitan Cluster?
What is a MetroCluster doing?
MetroCluster and SGeSAP: Supported Configurations
MetroCluster: Cluster Architecture Constraints
Combining MetroCluster and SGeSAP

HP MC/ServiceGuard Extension for SAP R/3 (SGeSAP) extends MC/ServiceGuard's powerful failover capabilities to SAP R/3 environments. It continuously monitors the health of each SAP R/3 node and automatically responds to failures or threshold violations. It can also minimize planned downtime when performing SAP R/3 upgrades. MC/ServiceGuard protects the SAP R/3 central instance and database by defining them in MC/ServiceGuard packages.

This chapter provides an overview of how SGeSAP works. Topics are as follows:

Printable version


Privacy statement	Using this site means you accept its terms	Feedback to webmaster

© Hewlett-Packard Development Company, L.P.