SAp on Solaris

7/29/2019 SAp on Solaris

http://slidepdf.com/reader/full/sap-on-solaris 1/17

An Oracle White Paper

March 2012

Oracle Solaris Cluster for SAPConfiguration Guide



Oracle Solaris Cluster for SAP Configuration Guide

Introduction ....................................................................................... 1 Oracle Solaris Cluster Software and Agents ...................................... 2

Oracle Solaris Cluster Data Service for Scalable SAP ................... 2 Oracle Solaris Cluster Data Service for SAP Enqueue Server ....... 3 High Availability SAP liveCache Data Service ............................... 3 High Availability Database Agent ................................................... 3

SAP Scenarios .................................................................................. 3 Central Instance Scenario ............................................................. 4 Central Instance / Java Central Services Scenario ........................ 5

ABAP Central Services Instance /Java Central Services Instance Scenario ...................................... 7

Ordering an Oracle Solaris Cluster License ..................................... 10 Failover and Scalable Services for Oracle Solaris Cluster 3.1(SPARC Only) ............................................................................. 10 Failover and Scalable Services for Oracle Solaris Cluster 3.2(SPARC and x86) ........................................................................ 11

High Available Services for SAP on Oracle Solaris Cluster 3.3…..13(SPARC and x86)

Status Update for Oracle Solaris Cluster 4.0…………………………..14

Conclusion………………………………………………….………….…..14




1

Introduction

The global economy offers unprecedented opportunities for companies to increase customers

and revenue, but there is a downside from an IT point of view. Systems must be continuously

available. The Oracle Solaris 10 operating system includes features such as predictive self

healing and fault manager that are designed to keep systems and applications up and running,

even if there is a hardware failure. Oracle Solaris Cluster software protects against systemfailure for even higher availability. This configuration guide is intended to help identify the

Oracle Solaris Cluster agents that provide high availability (HA) for some common SAP

implementation scenarios.




2

Oracle Solaris Cluster Software and Agents

Oracle Solaris Cluster software can be used to improve the availability of SAP components running on

Oracle Solaris. Oracle 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 an Oracle Solaris Cluster environment, enabling a single point of management with

agents for the SAP central instance; SAP enqueue (including enqueue and replication servers, central

services, and Web application server); SAP Java 2 Platform, Enterprise Edition (J2EE) engine; SAP

MaxDB (formerly SAP DB); and SAP liveCache technology.

Oracle Solaris Cluster software provides extended support for Oracle Solaris Containers, enabling

server consolidation even in HA environments. These virtualization capabilities allow scalable or

failover applications and associated Oracle Solaris Cluster agents to run unmodified within 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 Oracle Solaris Cluster failover. If this fails, it can attempt to restart on adifferent server using Oracle Solaris Cluster failover. Oracle 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 SAP DB/MaxDB database HA Oracle 9i and Oracle 9i Real Application Clusters (RAC)

HA Oracle 10 g and Oracle 10 g RAC

HA Oracle 11g R2 and Oracle 11g R2 RAC

IBM DB2+

Oracle Solaris Cluster Data Service for Scalable SAP

The Oracle Solaris Cluster data service for Scalable SAP agent provides scalable and HA (restart and

failover) capability for the SAP central instance. The agent enables 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 of SAP scripts to start, stop, and monitor multiple SAP dialog

instances




3

Oracle Solaris Cluster Data Service for SAP Enqueue Server

For SAP NetWeaver ‘04 (SAP kernel version 6.40) or later, 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 the standalone enqueue server must be performed manually after

the initial installation. With SAP NetWeaver 04, the enqueue server and the message server are

automatically installed to the ABAP central services (ASCS) instance.

The Oracle Solaris Cluster data service for SAP enqueue server supports three different installation

scenarios:

ABAP (Advanced Business Application Programming ) only

J2EE only

ABAP and Java combined

High Availability SAP liveCache Data Service

The HA SAP liveCache data service consists of two agents: liveCache and xserver. The first agent is

responsible for making the SAP liveCache database highly available. The second agent monitors the

health of the SAP xserver, which establishes all connections to the SAP liveCache database. If there is

a 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, enabling the xserver to bedistributed across nodes for load balancing and better performance. Coexistence between the HA SAP

liveCache data service and the HA SAP DB/MaxDB database data service is supported.

High Availability Database Agent

Oracle Solaris Cluster provides various database agents, for example, for Oracle, Oracle RAC and SAP

DB/MaxDB. The HA agent for SAP DB is designed to provide HA 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 SAP Max

DB and helps to improve service levels. (SAP DB has been renamed to MaxDB ab version 7.5).

SAP Scenarios

There are three installation scenarios for SAP. Each scenario is highlighted in this white paper to

describe single points of failure and the best Oracle Solaris Cluster agents that address these points.

Central instance scenario (for example, SAP R/3 4.6C/4.6D, SAP NetWeaver ‘04 ABAP only,

SAP NetWeaver 2004s ABAP only)




4

Central instance / Java central services (SAP Central Services [SCS]) scenario (for example, SAP

NetWeaver ‘04 based on SAP Web Application Server 6.40)

ASCS/SCS scenario (for example, SAP NetWeaver 2004s based on SAP NetWeaver Application

Server 7.00). Please note ASCS/SCS scenario is mandatory for SAP kernel 720 and 720_EXT. It isalso the default HA installation with sapinst.

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 application server ABAP usage type. The central

instance, the central file share, and the database are single points of failure (SPOF). Within the Oracle

Solaris Cluster environment, these services are monitored, and if there is a failure, the Oracle 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.

Figure 1. Single points of failure for central instance scenario

This scenario is supported with the Oracle Cluster Scalable SAP agent on Oracle Cluster 3.1 and 3.2

(both global zones and nonglobal zones) in Containers. The global zone is the master instance of the

operating system. Nonglobal zones are the virtualized, isolated environments.

Figure 2 shows an HA example of an ABAP-only system. It is supported for all ABAP-only SAP

systems with kernels 4.6D, 6.40, and 7.00. The Oracle Solaris Cluster agents required in this example

are Scalable SAP, HA NFS, and HA Oracle (or another database).




5

Figure 2. High availability ABAP-only central instance configuration

Central Instance / Java Central Services 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 add-in system,

single points of failure are the central file share, ABAP message server, ABAP enqueue server, Java

message server, Java enqueue server, and database. These single points of failure are illustrated in

Figure 3.




6

Figure 3. Central instance / SCS single points of failure

Oracle Solaris Cluster data service for the SAP enqueue server supports this scenario on Sun Cluster

3.1 update 3 or later, and also on Sun Cluster 3.2 global zones and nonglobal 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 an HA 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 kernels 6.40, 7.00, or later.

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 later can be configured for HA with

either the central instance scenario or the central instance / SCS scenario.




7

Figure 4. High availability Java-only or ABAP-only system in central instance / SCS

ABAP Central Services Instance / Java Central Services Instance Scenario

The difference between SAP NetWeaver 2004s 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.




8

Figure 5. ASCS/SCS single points of failure

The Oracle Solaris 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 an ABAP and Java system in an Oracle Solaris Cluster environment. It is supported

for all ABAP and Java systems with SAP kernels 6.40, 7.00, or later. Agents required for this

configuration are SAP Enqueue Server, HA NFS, and HA Oracle.




9

Figure 6. High availability SAP ABAP and Java




10

Ordering an Oracle Solaris Cluster License

The part numbers for the Oracle Solaris Cluster agents discussed in this white paper are included in

Table 1.

TABLE 1. ORACLE SOLARIS CLUSTER AGENT PART NUMBERS

PART NUMBER DESCRIPTION

BUSINESS LOGIC TIER

CLAIS-XXG-9999 SunPlex agent license for Scalable SAP. 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 SAP DB/MaxDB. One license required per cluster.

CLAIS-XXR-9999 SunPlex agent license HA Oracle. One license required per cluster.

CLAI9-LCA- X999 Oracle Solaris Cluster Advanced Edition for Oracle RAC, license fee, Tier X. Includes remote terminal

units for Oracle Solaris Cluster RAC agent, Shared QFS Metadata server and client, Oracle Solaris

Cluster agent for QFS Metadata server, Oracle Solaris Cluster Oban, Oracle Solaris Cluster-QFS-

Oban. Oracle Solaris SPARC and x86. Pricing is per node.

CENTRAL FILE SHARE

CLAIS-XXF-9999 Oracle Solaris Cluster agent license for HA NFS.

The part numbers for the additional agents are the same for Oracle Solaris Cluster 3.1 and 3.2. With

the exception of the Oracle RAC agent, only one license is required for each agent installed in the

cluster. The Oracle RAC agent needs one license per node/server.

Failover and Scalable Services for Oracle Solaris Cluster 3.1 (SPARC Only)

Table 2 provides the part numbers and support information for SPARC-only Oracle Solaris Cluster 3.1

agents.




11

TABLE 2. ORACLE SOLARIS CLUSTER AGENTS FOR ORACLE SOLARIS AND SAP RELEASES

ORACLE SOLARIS

CLUSTER AGENT

APPLICATION

VERSION

ORACLE SOLARIS

VERSION

COMMENTS

Scalable SAP

CLAIS-XXG-9999

4.60 10 All intermediate releases of SAP applications are supported

(for example, 4.6C, 4.6D).

6.40 9, 10 Only for ABAP and the upgrade to 6.40 from older versions

such as 6.20. It is not possible to separate the enqueue and

the message server from the central instance. For a few

installations, Oracle strongly recommends the HA SAP

Enqueue Server agent.

7.00 10 ABAP-only system, central instance installation.

HA SAP Enqueue

Server CLAIS-XAI-

9999

6.40 9, 10 Oracle Solaris Cluster 3.1 9/04 or later.

7.00 9, 10 Oracle Solaris Cluster 3.1 9/04 or later.

SAP liveCache

CLAIS-XXL-9999

7.4 64 bit 9

7.5 9, 10

HA Agent for MaxDB

Database CLAIS-

XAA-9999

7.4 64 bit 9, 10 SAP DB has been renamed to MaxDB.

7.5 9, 10

HA NFS CLAIS-

XXF-9999

V3 9, 10

HA Oracle CLAIS-

XXR-9999

9i , 10g 9, 10

Oracle RAC CLAI9-

LCA-X999

9i , 10g 10

Failover and Scalable Services for Oracle Solaris Cluster 3.2 (SPARC and x86)

All of the above agents are supported on Oracle Solaris Cluster 3.2 SPARC and x86 global zones and

nonglobal zones.

New features in Oracle Solaris Cluster 3.2 include the following:

Improved Java application instance support: HA SAP Enqueue Server supports all three types of

application instances (ABAP only, Java only, ABAP and Java combined). Application server

instances can be configured as failover and scalable.

Support for global and nonglobal zones on SPARC and x86.

Table 3 provides support information for Oracle Solaris Cluster 3.2.




12

TABLE 3. ORACLE CLUSTER 3.2 AGENTS FOR ORACLE SOLARIS AND SAP RELEASES

ORACLE SOLARIS

CLUSTER AGENT

APPLICATION

VERSION

ORACLE SOLARIS

VERSION

COMMENTS

Scalable SAP

CLAIS-XXG-9999

4.6D 64 bit 10 (SPARC) All intermediate releases of SAP applications are supported

(for example, 4.6C, 4.6D).

SPARC only.

Global and nonglobal zones supported.

6.40 ABAP only 10 (SPARC) Only supports ABAP-only system, central instance

installation. For a new installation, use the HA SAP

Enqueue Server agent with ASCS installation.

SPARC only.


7.00 ABAP only 10 (SPARC and

x86)

Only supports ABAP-only system, central instance

installation. For a new installation, use the HA SAP

Enqueue Server agent with ASCS installation.

Supported on SPARC and x86.


HA SAP Enqueue

Server

CLAIS-XAI-9999

6.40 10 (SPARC) Supports all three types of SAP systems (ABAP, Java,

ABAP and Java) in SCS/ASCS installation.

SPARC only.

Supported both on global and nonglobal zones on SPARC.

7.00

7.01

10 (SPARC and

x86)

Supports all three types of SAP systems (ABAP, Java,



Global and on nonglobal zones supported.

7.10 10 (SPARC and

x86)

Supports all three types of SAP systems (ABAP, Java,



Global and on nonglobal zones supported.

SAP liveCache

CLAIS-XXL-9999

7.5 10 (SPARC) SPARC only.


7.6 10 (SPARC and

x86)

SPARC and x86.


7.7 10 (SPARC and

x86)

SPARC and x86

Global and nonglobal zones supported

From liveCache 7.7.04.38

Also refer to SAP note 1461628

HA Agent for SAP

MaxDB Database

CLAIS-XAA-9999

7.5 10 (SPARC) SAP DB has been renamed to SAP MaxDB.

SPARC only.


7.6 10 (SPARC and SPARC and x86.




13

x86) Global and nonglobal zones supported.

7.7 10 (SPARC and

x86)

SPARC and x86.


HA NFS V3 10 (SPARC and

x86)

Global zone only.

V4 10 (SPARC and

x86)

Global zone only.

HA Oracle 9i 10 (SPARC) Agent supported on global and nonglobal zones on SPARC.

10g 10 (SPARC and

x86)

Agent supported on global and nonglobal zones on SPARC

and x86.

Oracle RAC

CLAI9-LCA-X999

High Available Services for SAP on Oracle Solaris Cluster 3.3 (SPARC and x86)

All of the above agents are supported on Oracle Solaris Cluster 3.3 SPARC and x86 global zones andnonglobal zones. Oracle Solaris Cluster 3.3 supports SAP products based on SAP kernel 700, 701, 710,711, 720 and 720_EXT (e.g SAP EHP2 for NetWeaver 7.0, SAP Enhancement Package 5 for SAPERP 6.0.)

For SAP kernel 720 and 720_EXT, ASCS/SCS scenario is mandatory, the following is required:

- Oracle Solaris Release 10 10/09, 9/10, 8/11- Oracle Solaris Cluster 3.3 5/11- Solaris Cluster Agents SUNW.sapwebas, SUNW.sapscs, SUNW.sapenq, SUNW.saprepl.- Patch 146091-06 for SPARC and 146092-06 for x86_64

For SAP kernel 700, 701, 710 and 711, the above configuration is not mandatory but is strongly recommended, for compatibility of updating to SAP kernel 720 and 720_EXT later.

New features in Oracle Solaris Cluster 3.3 include the following:- Improved Java application instance support: HA SAP Enqueue Server supports all three types of

application instances (ABAP only, Java only, ABAP and Java combined). Application serverinstances can be configured as failover and scalable.

- Improved support for global and nonglobal zones on SPARC and x86.- Support for SAP kernel 720 and 720_EXT.

Table 4 provides support information for Oracle Solaris Cluster 3.3.




14

TABLE 4. ORACLE CLUSTER 3.3

ORACLE SOLARISCLUSTER AGENT

APPLICATIONVERSION

ORALCE SOLARISVERSION

COMMENTS

Scalable SAPCLAIS-XXG-9999

SAP kernel 640 ABAP onlySAP kernel 700 ABAP onlySAP kernel 701 ABAP only

10 (SPARC)10 (SPARC and x86)

+ Only supports ABAP-only updated system. For a newinstallation, use the HA SAP Enqueue Server agent with ASCS/SCS scenario.

+ SAP kernel 640 is supported on SPARCE only.+ SAP kernel 700 and 701 are supported on SPARC and

x86.+ Global and nonglobal zones supported.

HA SAP Enqueue Server CLAIS-XAI-9999

SAP kernel 640,SAP kernel 700,SAP kernel 701,SAP kernel 710,SAP kernel 711,SAP kernel 720,SAP kernel 720_EXT

10 (SPARC and x86) + Supports all three types of SAP systems (ABAP, Java, ABAP and Java) in SCS/ASCS installation.

+ Supported on SPARC and x86.+ Global and nonglobal zones supported.+ Requires OracleSolaris Release 10 10/09, 9/10, 8/11+ Requires Oracle Solaris Cluster 3.3 5/11+ Requires Patch 146091-06 for SPARC and 146092-06 for

x86_64

SAP liveCache

CLAIS-XXL-9999

SAP liveCache 7.6,

SAP liveCache 7.7

10 (SPARC and x86) + SPARC and x86

+ Global and nonglobal zones supported+ 7.6 requires at least 7.6.03.09+ 7.7 requires 7.7.04.38+ Also refer to SAP note 1461628

HA Agent for SAPMaxDB DatabaseCLAIS-XAA-9999

SAP MaxDB 7.6,SAP MaxDB 7.7,SAP MaxDB 7.8

10 (SPARC and x86) + SPARC and x86.+ Global and nonglobal zones supported.

HA NFS V3,V4

10 (SPARC and x86) + Global zone only.

HA Oracle Oracle 10gOracle 11g R2

10 (SPARC and x86) + Agent supported on global and nonglobal zones onSPARC and x86.

Oracle RAC Oracle 10g RACOracle 11g R2 RAC

10 (SPARC and x86)

Status Update for Oracle Solaris Cluster 4.0

Oracle Solaris Cluster 4.0 is supported with Solaris 11.Oracle Solaris Cluster 4.0 supports HA Oracle 11.2.0.3 and Oracle 11.2.0.3 RAC.HA NFS is supported on Oracle Solaris Cluster 4.0.HA SAP (central services server ASCS/SCS, enqueue replication server ERS, primary applicationserver PAS and additional application server AAS) will be supported on Oracle Solaris Cluster 4.0soon.

Conclusion

Oracle Solaris Cluster software creates high availability environments for multiple SAP

deployment scenarios. Whether using ABAP or Java or a combination of the

two organizations can make their SAP environments continuously available using Oracle Solaris

Cluster.



Oracle Solaris Cluster for SAP

Configuration Guide

October 2010

Oracle Corporation

World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065

U.S.A.

Worldwide Inquiries:

Phone: +1.650.506.7000

Fax: +1.650.506.7200

oracle.com

Copyright © 2007, 2010, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and

the contents hereof are subject to change without notice. This document is not warranted to be error -free, nor subject to any other

warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or

fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obli gations are

formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any

means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective

owners.

AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel

and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are

trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open

Company, Ltd. 0410

SAp on Solaris

Documents

Transcript of SAp on Solaris