Managing Serviceguard Extension for SAP, December 2007

Understanding Serviceguard Extension for SAP
Designing SGeSAP Cluster Scenarios
Chapter 1 21
A sample configuration in Figure 1-2 shows node1 with a failure, which
causes the package containing the database and central instance to fail
over to node2. A Quality Assurance System and additional Dialog
Instances get shut down, before the database and Central Instance are
restarted.
Figure 1-2 One-Package Failover Scenario
NOTE A J2EE Engine might be part of the Central Instance. The JAVA
instance will then be moved with the package automatically.
SGeSAP Cluster
One-Package Concept
shared disks
node1
node2
Application servers not part of cluster
dbci<SID>
QAS System
Dialog Instances
DBCI package
moved and
required
resources
freed up in the
event of a failure