SOLARIS™ CLUSTER FOR SAP

CONFIGURATION GUIDE
September 2007
 Sun Microsystems, Inc.

Table of Contents

Solaris™ Cluster Software and Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Solaris Cluster Software and Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Solaris Cluster Data Service for Scalable SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Solaris Cluster Data Service for SAP Enqueue Server . . . . . . . . . . . . . . . . . . . . . . 2
HA SAP liveCache Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
HA Database Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
SAP Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Central Instance Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Central Instance/SCS Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
ASCS/SCS Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Ordering a Solaris Cluster License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Failover and Scalable Services for Solaris Cluster 3.1 (SPARC® only) . . . . . . . . . 10
Failover and Scalable Services for Solaris Cluster 3.2 (SPARC and x64) . . . . . . . 10
For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
 Sun Microsystems, Inc.

1 Solaris™ Cluster for SAP Configuration Guide

Solaris™ Cluster for SAP Configuration Guide

This configuration guide is intended to help identify the right Solaris™ Cluster agents to
provide high availability for several common SAP implementation scenarios.

Solaris Cluster Software and Agents

The global economy offers huge opportunities in increased customers and revenue, but
also comes with a downside from an IT point of view. Global competition and
international customers mean systems must be available 7x24x365. The Solaris 10
Operating System includes features such as Solaris Predictive Self Healing and Solaris
Fault Manager to keep systems and applications up and running, even in the event of
hardware failures. Solaris Cluster software protect against system failure for even
higher availability.

Solaris Cluster software can be used to improve the availability of SAP components
running on the Solaris OS. Solaris Cluster uses redundant computers to protect against
downtime, eliminating the server as a single point of failure. All tiers of an SAP
NetWeaver platform can be consolidated within a Solaris Cluster environment,
allowing for a single point of management with agents for SAP CI (Central Instance),
SAP enqueue (including enqueue and replication servers, central services, and Web
application server), SAP Java™ 2 Platform, Enterprise Edition (J2EE™) engine, SAP
DB/MaxDB, and SAP liveCache.

Solaris Cluster software provides expanded support for Solaris Containers, enabling
server consolidation even in highly available environments. These virtualization
capabilities allow scalable or fail-over applications and associated Solaris Cluster agents
to run unmodified within Solaris Containers. This type of environment offers multiple
layers of availability. For example, an application can be configured to first try to restart
in its container (zone). If the restart fails, it can attempt to start in another container
using Solaris Cluster failover. If this fails, it can attempt to restart on a different server
using Solaris Cluster failover. Solaris Cluster software is available with a number of
agents for the SAP environment.

Agents for the business logic tier:

• Scalable SAP
• HA SAP Enqueue Server
• HA SAP liveCache

Agents for the database tier:

• HA SAPDB/MaxDB database
• HA Oracle 9i and Oracle 9iRAC
• HA Oracle 10g and Oracle 10gRAC
• IBM DB2+
 Sun Microsystems, Inc.

2 Solaris™ Cluster for SAP Configuration Guide

Solaris Cluster Data Service for Scalable SAP

This agent provides scalable and high availability (restart and failover) capability for the
SAP central instance. The agent allows applications to be distributed across all nodes in
the cluster. It delivers two main functions:
• A failover service that starts, stops, and monitors the SAP central instance
• A scalable function that uses one set up SAP scripts to start, stop, and monitor
multiple SAP dialog instances

Solaris Cluster Data Service for SAP Enqueue Server

For SAP NetWeaver 04 (SAP kernel version 6.40) and above, SAP implements a
replication feature for the enqueue server. The enqueue server runs on one node and
the replicated enqueue server runs on another node. If a failure impacts the enqueue
server, the enqueue server fails over to the other node where a replicated enqueue
server is running. The enqueue server takes over the data from the replication table
that resides in the shared memory segment. This feature can effectively prevent data
loss caused by the enqueue server failure. To implement this feature, The enqueue
server must not be a part of the central instance, it must run independently as a
standalone enqueue server. The replicated enqueue server must run on another node
other than the standalone enqueue server. With SAP NetWeaver 04 the configuration
of standalone enqueue server must be performed manually after the initial installation.
With SAP NetWeaver 2004s the enqueue and the message server are automatically
installed to the ABAP central services (ASCS) Instance.

The Sun Cluster Data Service for SAP Enqueue Server supports three different
installation scenarios:
• ABAP only
• J2EE only
• ABAP and Java combined

HA SAP liveCache Data Service

The HA SAP liveCache data service consists of two agents, liveCache and xserver. The
first one is responsible for making the liveCache database highly available. The second
agent monitors the health of the SAP xserver, which establishes all connections to the
SAP liveCache database. In case of failure, the agent makes the switch to another
xserver process located on a different server that is running in warm standby mode.
The agent also provides scalability, allowing the xserver to be distributed across nodes
for load balancing and better performance. Coexistence between the HA SAP liveCache
data service and the HA SAPDB/MaxDB Database data service is supported.
 Sun Microsystems, Inc.

3 Solaris™ Cluster for SAP Configuration Guide

HA Database Agent
Solaris Cluster provides various database agents, e.g. for Oracle, Oracle RAC,
SAPDB/MaxDB. The HA agent for SAPDB is designed to provide high availability for the
database instances in SAP environments by monitoring and restarting or failing over
the database instance to another available node in case of hardware or software faults.
This eliminates the single point of failure of the SAPDB to help improve service levels.
SAPDB has been renamed to MaxDB ab version 7.5.

SAP Scenarios
There are three different installation scenarios for SAP. Each scenario is highlighted in
this paper to describe single points of failure and the appropriate Solaris Cluster agents
to address these points.
• Central instance scenario (e.g., SAP R/3 4.6C/4.6D, NetWeaver 04 ABAP-only,
NetWeaver 04s ABAP-only)
• Central instance / Java central services (SCS) scenario (e.g,. SAP NetWeaver 04 based
on SAP Web Application Server 6.40)
• ASCS/SCS scenario (e.g., SAP NetWeaver 2004s based on SAP NetWeaver Application
Server 7.00)

Central Instance Scenario

In the central instance scenario the enqueue server and message server are integrated
in the central instance. Only one message server can run on each AS ABAP usage type.
The central instance, the central file share and, the database are single points of failure
(SPOF). Within the Solaris Cluster environment, these services are monitored, and in
case of a failure the Solaris Cluster agents react to restart the services. Figure 1 shows
the single points of failure in this scenario. Note that the central file share (NFS share
for /sapmnt) is not shown in this figure.

Central Instance (CI)

SPOF
ABAP Displatcher

Work Process
Work Process
Work Process

Gateway Database
Enqueue Server
(ABAP)

Message Server ABAP

(ABAP) Schema
SPOF
ABAP

Figure 1. Central Instance single points of failure

 Sun Microsystems, Inc.

4 Solaris™ Cluster for SAP Configuration Guide

This scenario is supported with the Sun Cluster Scalable SAP agent on Sun Cluster 3.1
and 3.2 (both global zones and non-global zones) in Solaris Containers. The global zone
is the master instance of the OS, non-global zones are the virtualized, isolated
environments.

Figure 2 shows a highly available example of an ABAP-only system. It is supported for all
ABAP-only SAP systems with kernel 4.6D, 6.40, and 7.00. The Solaris Cluster agents
required in this example are Scalable SAP, HA NFS, and HA Oracle (or other database).

Dialog Instance Dialog Instance

scalable
(optional) (optional)
ABAP ABAP

failover
Central File Share
/sapmnt

Central Instance
Dispatcher
(ABAP)

Work Processes failover

(ABAP)

Enqueue Server
(ABAP)

Message Server
(ABAP)

Database failover

ABAP Schema

Figure 2. Highly available ABAP-only central instance scenario

 Sun Microsystems, Inc.

5 Solaris™ Cluster for SAP Configuration Guide

Central Instance/SCS Scenario

In SAP NetWeaver 04 with SAP Web Application Server 6.40 it is possible to configure a
standalone message server, enqueue server, and enqueue replication server. For an
ABAP and Java addin system, single points of failure are the central file share, ABAP
message server, ABAP enqueue server, Java message server, Java enqueue server, and
the database. These single points of failure are illustrated in Figure 3.

Central Instance (CI) SCS Instance

Enqueue Server
Internet Communication Manager (ICM)
(Java)
SPOF

ABAP Java Message Server

Displatcher Displatcher (Java)
SPOF
Work Server
Work
Process Server
Process /usr/sap/<SID>/SCS
Work
Process Server
Process
Process Process <Instance_Number>

Gateway SDM
Database
Enqueue Server
(ABAP) SPOF

Message Server ABAP Schema

(ABAP) SPOF
ABAP Java SPOF

Internet Graphics Server (IGS) Java Schema

/usr/sap/<SID>/DVEBMSG<Instance_Number>

Figure 3. Central instance/SCS single points of failure

Solaris Cluster Data Service for SAP Enqueue Server supports this scenario on Sun
Cluster 3.1 update 3 and later, and also on Sun Cluster 3.2 global zones and non-global
zones.

Note that the Java message server and enqueue server are installed as a standalone
SCS instance, but the ABAP message server and ABAP enqueue server must be
configured manually after the initial installation.

Figure 4 shows a highly available configuration for a Java only or ABAP-only system in
the central instance/SCS scenario. It is suitable for Java only or ABAP-only systems with
SAP kernel 6.40, 7.00, and above. Agents required in this configuration are SAP Enqueue
Server, HA NFS, and HA Oracle.

Environments with an ABAP-only system with SAP kernel 6.40 or above, can be
configured for high availability with either the central instance scenario or the CI/SCS
scenario.
 Sun Microsystems, Inc.

6 Solaris™ Cluster for SAP Configuration Guide

scalable
Dialog Instance Dialog Instance
(optional) (optional)
failover
Central Instance
(optional for HA)

failover
Central File Share
/sapmnt

SCS or ASCS
failover
Enqueue Server Enqueue Replication
Server
(optional, recommended)
Message Server

Database failover

Figure 4. Highly available Java only or ABAP-only system in CI/SCS scenario

 Sun Microsystems, Inc.

7 Solaris™ Cluster for SAP Configuration Guide

ASCS/SCS Scenario
The difference between SAP NetWeaver 04s and SAP NetWeaver 2004 is the presence of
the ASCS instance. With SAP NetWeaver 2004s, the enqueue and message servers can
be automatically installed as standalone ASCS instances. Figure 5 shows this scenario.

Central Instance (CI) ASCS Instance SCS Instance

Enqueue Server Enqueue Server
Internet Communication Manager (ICM) (ABAP) (Java)
SPOF SPOF

ABAP Message Server Message Server

Java
Displatcher (ABAP) (Java)
Displatcher SPOF SPOF

Work Server /usr/sap/<SID>/SCS

Work
Process Server
Process <Instance_Number>
Work
Process Server
Process
Process Process

Gateway SDM
Database

ABAP Java
ABAP Schema
Internet Graphics Server (IGS) SPOF

Java Schema
/usr/sap/<SID>/DVEBMSG<Instance_Number>

Figure 5. ASCS/SCS single points of failure

The Sun Cluster Data Service for SAP Enqueue Server supports this deployment scenario
for SAP NetWeaver 2004s, including standalone message servers and replicated
enqueue servers.

Figure 6 illustrates a ABAP and Java system in a Solaris Cluster environment. It is

supported for all ABAP and Java systems with SAP kernel 6.40, 7.00, and above. Agents
required for this configuration are SAP Enqueue Server, HA NFS, and HA Oracle.
 Sun Microsystems, Inc.

8 Solaris™ Cluster for SAP Configuration Guide

Dialog Instance (optional) scalable Dialog Instance (optional)

ABAP Java ABAP Java

failover
Central Instance (optional for HA)
ABAP Java

failover
Central File Share
/sapmnt

failover
SCS Instance Replication Server
Message Server Enqueue Server (Java)
(Java) (Java) (optional, recommended)
failover
ASCS Instance Replication Server
Message Server Enqueue Server (ABAP)
(ABAP) (ABAP)
(optional, recommended)

Database
failover
ABAP Schema

Java Schema

Figure 6. Highly available SAP ABAP and Java system

 Sun Microsystems, Inc.

9 Solaris™ Cluster for SAP Configuration Guide

Ordering a Solaris Cluster License

The part numbers for the Solaris Cluster agents discussed in this paper are included in
Table 1.

Table 1. Solaris Cluster agent part numbers

Part Number Description

Business Logic Tier
SunPlex agent license for Scalable SAP.
CLAIS-XXG-9999 One license required per cluster.

CLAIS-XAI-9999 SunPlex agent license for HA SAP Enqueue Server.

One license required per cluster.

CLAIS-XXL-9999 SunPlex agent license for HA SAP liveCache.

One license required per cluster.
Database Tier

CLAIS-XAA-9999 SunPlex agent license HA SAPDB/MaxDB.

One license required per cluster.

CLAIS-XXR-9999 SunPlex agent license HA Oracle.

One license required per cluster.
Solaris Cluster Advanced Edition for Oracle RAC, License Fee,
Tier X. Includes RTUs for Solaris Cluster RAC agent, Shared QFS
Metadata server and client, Solaris Cluster agent for QFS
CLAI9-LCA- X999 Metadata server, Solaris Cluster Oban, Solaris Cluster-QFS-Oban.
Solaris SPARC® and x64.
Pricing is per node.
Central File Share
CLAIS-XXF-9999 Solaris Cluster agent license for HA NFS.

The part numbers for the additional agents are for Solaris Cluster 3.1 and 3.2 the same.
With the exception of the Oracle RAC agent only one licence is required for each agent
installed in the cluster. The Oracle RAC agent needs one licence per node/server.
 Sun Microsystems, Inc.

10 Solaris™ Cluster for SAP Configuration Guide

Failover and Scalable Services for Solaris Cluster 3.1 (SPARC only)
Table provides the part numbers and support information for SPARC only Solaris Cluster
3.1 agents.

Table 2. Solaris Cluster agents for Solaris and SAP releases

Application Solaris Comments

Solaris Cluster Agent
Version Version
All intermediate releases of SAP
4.60 10 applications are supported (for
example 4.6C, 4.6D).
Only for ABAP and the upgrade to
6.40 from older versions such as
Scalable SAP 6.20. It is not possible to separate
CLAIS-XXG-9999 6.40 9, 10 the enqueue and the message server
from the central instance. For a few
installations Sun strongly
recommends the HA SAP Enqueue
Server agent.

7.00 10 ABAP-only system, central instance

installation.
6.40 9, 10 Solaris Cluster 3.1 9/04 or above.
HA SAP Enqueue Server
CLAIS-XAI-9999 7.00 9, 10 Solaris Cluster 3.1 9/04 or above.

SAP liveCache 7.4 64 bit 9

CLAIS-XXL-9999 7.5 9, 10
HA Agent for MaxDB 7.4 64 bit 9, 10 SAP DB has been renamed to MaxDB.
Database
CLAIS-XAA-9999 7.5 9, 10
HA NFS V3 9, 10
CLAIS-XXF-9999
HA Oracle
CLAIS-XXR-9999 9i, 10g 9, 10

Oracle RAC
CLAI9-LCA- X999 9i, 10g 10

Failover and Scalable Services for Solaris Cluster 3.2 (SPARC and x64)
All of the above agents are supported on Solaris Cluster 3.2 SPARC and x64 global zones
and non-global zones.

New features in Solaris Cluster 3.2 include:

• Improved Java application instance support: HA SAP Enqueue Server support all three
type of application instances (ABAP only, Java only, ABAP and Java combined).
Application Server Instances can be configured as failover and/or scalable.
• Support for global and non-global zones on SPARC and x64.
 Sun Microsystems, Inc.

11 Solaris™ Cluster for SAP Configuration Guide

Table 3 provides support information for Solaris Cluster 3.2.

Table 3. Sun Cluster 3.2 agents for Solaris and SAP releases

Solaris Cluster Application Solaris

Comments
Agent Version Version

• All intermediate releases of SAP

applications are supported (for
example 4.6C, 4.6D).
4.6D 64bit 10 (SPARC)
• SPARC only.
• Global and non-global zones
supported.
• Only supports ABAP-only system,
Central Instance installation. For a
new installation use the HA SAP
Enqueue Server agent with ASCS
6.40 ABAP-only 10 (SPARC)
Scalable SAP installation.
CLAIS-XXG-9999 • SPARC only.
• Global and non-global zones
supported.
• Only supports ABAP-only system,
central instance installation. For a
new installation, use the HA SAP
Enqueue Server agent with ASCS
7.00 ABAP-only 10 (SPARC &
x64) installation.
• Supported on SPARC and x64.
• Global and non-global zones
supported.
• Supports all three types of SAP
systems (ABAP, Java, ABAP and Java)
in SCS/ASCS installation.
6.40 10 (SPARC)
• SPARC only.
• Supported both on global and non-
HA SAP Enqueue global zones on SPARC.
Server
CLAIS-XAI-9999 • Supports all three types of SAP
systems (ABAP, Java, ABAP and Java)
10 (SPARC & in SCS/ASCS installation.
7.00
x64) • Supported on SPARC and x64.
• Global and on non-global zones
supported.
• SPARC only.
7.5 10 (SPARC) • Supported both on global and non-
SAP liveCache global zones on SPARC.
CLAIS-XXL-9999 • SPARC and x64.
10 (SPARC &
7.6 x64) • Global and non-global zones
supported.
 Sun Microsystems, Inc.

12 Solaris™ Cluster for SAP Configuration Guide

Solaris Cluster Application Solaris

Comments
Agent Version Version

• SAP DB has been renamed to MaxDB.

• SPARC only.
7.5 10 (SPARC)
• Supported both on global and non-
HA Agent for MaxDB
Database global zones on SPARC.
CLAIS-XAA-9999
• SPARC and x64.
7.6 10 (SPARC & • Global and non-global zones
x64)
supported.
10 (SPARC & • Global zone only.
V3 x64)
HA NFS
V4 10 (SPARC & • Global zone only.
x64)
• Agent supported on global and non-
9i 10 (SPARC)
global zones on SPARC.
HA Oracle
10 (SPARC & • Agent supported on global and non-
10g x64) global zones on SPARC and x64.

Oracle RAC •
CLAI9-LCA- X999 •

For More Information

Sun Microsystems posts product information in the form of data sheets, specifications,
and white papers on its Web site page at: http://www.sun.com/.

For more information on Sun and SAP see: http://www.sun.com/sap/.

For more information on SAP see: http://www.sap.com/.

For more information on Solaris Cluster software see: http://www.sun.com/cluster.

For more information on Sun Cluster support for SAP systems, see SAP note 961762.
Solaris Cluster for SAP Configuration Guide On the Web sun.com

Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 USA Phone 1-650-960-1300 or 1-800-555-9SUN (9786) Web sun.com
© 2007 Sun Microsystems, Inc. All rights reserved. Sun, Sun Microsystems, the Sun logo,Java, J2EE, and Solaris, are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other
countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the US and other countries. Products bearing SPARC trademarks are based upon
an architecture developed by Sun Microsystems, Inc. Information subject to change without notice. Printed in USA 09/07