LabF06 Pulse12 SAP High Availability[1]

8/11/2019 LabF06 Pulse12 SAP High Availability[1]

http://slidepdf.com/reader/full/labf06-pulse12-sap-high-availability1 1/40

Lab F06

IBM Tivoli System Automation forMultiplatforms 3.2.2

SAP High Availability

March 2012



Copyright Notice

Copyright © 2012 IBM Corporation, including this documentation and all software. All rights

reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Soft-

ware License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system,

or translated into any computer language, in any form or by any means, electronic, mechanical,

magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corpora-

tion. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any

machine-readable documentation for your own use, provided that each such reproduction shall carry

the IBM Corporation copyright notice. No other rights under copyright are granted without prior writ-

ten permission of IBM Corporation. The document is not intended for production and is furnished “as

is” without warranty of any kind. All warranties on this document are hereby disclaimed, including the

warranties of merchantability and fitness for a particular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or

disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

Trademarks

The following are trademarks of IBM Corporation or Tivoli Systems Inc.: IBM, Tivoli, AIX, Cross-Site,

NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, TME. In Den-

mark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in

the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States,

other countries, or both.

Lotus is a registered trademark of Lotus Development Corporation.

PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or

both and is used by IBM Corporation under license.

ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the

United States, other countries, or both.

SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. For fur-

ther information, see http://www.setco.org/aboutmark.html.

Other company, product, and service names may be trademarks or service marks of others.

Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply

that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to

these products, programs, or services is not intended to imply that only Tivoli Systems or IBM prod-

ucts, programs, or services can be used. Subject to valid intellectual property or other legally pro-

tectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can

be used instead of the referenced product, program, or service. The evaluation and verification ofoperation in conjunction with other products, except those expressly designated by Tivoli Systems or

IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent

applications covering subject matter in this document. The furnishing of this document does not give

you any license to these patents. You can send license inquiries, in writing, to the IBM Director of

Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

Printed in Ireland.



•

•

•

•

•

II

Table of contents

Introduction . . . . . . . . . . . . . . 1

New SAP high availability solution feature . . . . . . . . . 1Lab setup and contents . . . . . . . . . . . 1

Motivation . . . . . . . . . . . . . . 2

Solution . . . . . . . . . . . . . . 2

High availability and automation objectives for SAP . . . . . . . 4

Overview of the high availability solution for SAP . . . . . . . 4

High availability of a SAP system . . . . . . . . . . 4

Automation of a SAP system . . . . . . . . . . 4

SAP high availability setup options . . . . . . . . . 5

Benefits of Tivoli System Automation . . . . . . . . . 5

Introduction . . . . . . . . . . . . . 5

Environment . . . . . . . . . . . . . 6

Overview of user IDs and passwords . . . . . . . . . 6

Overview of systems and IP addresses . . . . . . . . . 6

Exercise 1: Preparation . . . . . . . . . . . . 8Starting the Tivoli System Automation for Multiplatforms VMware images . . . . 8

Verifying configuration . . . . . . . . . . . . 9

Operations console . . . . . . . . . . . 10

Verifying that the operations console is running . . . . . . 10

Logging in to the Integrated Solutions Console . . . . . . . 11

Exercise 2: Defining automation policy for SAP . . . . . . . 11

Exercise 3: SAP Operations - Introduction . . . . . . . . 16

Objectives . . . . . . . . . . . . . 16

Introduction . . . . . . . . . . . . 16

Operations console layout . . . . . . . . . . 17

Topology tree . . . . . . . . . . . . 17

Resources section . . . . . . . . . . . 18

Information area . . . . . . . . . . . 18

Help . . . . . . . . . . . . . 18Exercise 4: Displaying defined resources and relationships . . . . . 19

Exercise 5: Starting SAP . . . . . . . . . . . 23

Exercise 6: Excluding a node from automation . . . . . . . 25

Exercise 7: Suspending automation for a resource . . . . . . . 28

Exercise 8: Testing application failover . . . . . . . . 30

Exercise 9: Moving requests . . . . . . . . . . 32

Exercise 10: Stopping SAP . . . . . . . . . . 35

Summary . . . . . . . . . . . . . 36

http://instructornotesig.pdf/









IV ©Copyright IBM Corp. 201

•

•

•

•

•

Table of contents

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.










•

•

•

•

•

1

Introduction

In this lab exercise, you learn how to make SAP available. You use the new SAP wizard of Tivoli

System Automation for Multiplatforms V3.2.2 (SA MP) to define automation in your own cluster.

You also learn to start and stop an entire SAP cluster with a single command. You perform a critical

outage scenario of the SAP central instance and watch Tivoli System Automation for

Multiplatforms recovering your SAP application.

New SAP high availability solution feature

With System Automation for Multiplatforms V3.2.1, a new feature became available that provides

product-level support for the SAP high availability policy. This feature replaces the unsupported

policy that was available on an as-is basis. The feature was extended with V3.2.2 and includes:

• High availability policy templates for four different SAP configuration options.

• Start, stop, and monitor scripts for all involved resources.

• Ease of use wizard with automatic cluster and SAP discovery (new in V3.2.2) to configure

the actual policy from the policy template.

• Support of different SAP releases.

• Comprehensive documentation for the installation and setup of SAP high availability

systems.

• NFS server and Oracle database high availability solution feature (new in V3.2.2) that can be added to SAP policy. DB2 and SAP policy can be combined as well.

Lab setup and contents

Tivoli System Automation for Multiplatforms is already running on Linux in a cluster, also called

automation domain. This domain has two systems, node01 and node02, plus a dedicated system

node03 for the Integrated Solutions Console based operations console. In these exercises, you have

the following goals:

• To define the automation policy to make SAP highly available

• Operate an entire SAP cluster

SAP resources are simulated, but have similar start and stop times. The enqueue replication server

(ERS) also terminates itself after an enqueue server (ES) has been started on the same system.










2 IBM Tivoli System Automation for Multiplatforms 3.2.2 ©Copyright IBM Corp. 20

•

•

•

•

•

Introduction


Motivation

The availability of a SAP production system is a critical business factor. SAP availability is

threatened by the following items:

• Single points of failure with the enqueue server being the most prominent one

• Complexity resulting from many different components and relationships for start, stop and

recovery

• Operator errors due to complexity

Solution

The Tivoli System Automation family provides a high availability solution for SAP that can fully

automate the management of all SAP components and related products running on z/OS, AIX,

Windows, Solaris or Linux. The automation software monitors all resources and controls the restart

or takeover of failing components, thereby ensuring near continuous availability of the SAP system.

In a distributed or standard SAP installation, the SAP Central Services (SAP Central Instance), the

database server, and the NFS server are single points of failures (SPOFs). To minimize the impact

of SPOF services outages, it is necessary to set up redundancy. You must run one or more standby

servers to which each of the SPOF services can be failed over and restarted independently. Each

SPOF service must be associated with its own virtual host name, which is started where the service










©Copyright IBM Corp. 2012 SAP High Availability 3

•

•

•

•

•

Introduction


runs. This allows the clients to reconnect to the same host name independently where the SPOF

service runs.

Figure 1: Components of a distributed SAP system in an ASCS high availability setup

The availability of the enqueue server is critical for a SAP system. If it fails, most SAP transactions

also fail. To address this single point of failure, SAP changed the architecture of the enqueue server.

It is no longer part of the so-called central instance. That is, it no longer runs inside a work process,

but is now a standalone process called the standalone enqueue server (which operates under the

designation SAP Central Services, or SCS). The enqueue server transmits its lock data to an

enqueue replication server, which normally resides on a different system. The enqueue replication

server stores the replication data in a shadow enqueue table that is in shared memory.

If the enqueue server fails, it is quickly restarted by Tivoli System Automation and uses thereplicated data in the shadow enqueue table to rebuild the tables and data structures. This means that

a failure of the enqueue server is transparent to the end user and the SAP application.













•

•

•

•

•

Introduction


SAP high availability setup options

System Automation for Multiplatforms supports four different SAP high availability installation

setups:

• ABAP SCS (ASCS) high availability installation

• Java SCS high availability installation

• Double-Stack (ASCS and SCS) high availability installation

• ABAP Central Instance high availability installation

In this lab, you use an ASCS high availability installation.

The ASCS high availability setup consists of at least two SCS nodes that run the ASCS and ERS

instances. The ERS always is started on the node where the ASCS is not running. This failover setup

has no downtime due to fast failure detection and data exchange between ES and ERS on the

failover node in your main memory. During the failover, the virtual IP address for the ASCS ismoved to the failover node.

Benefits of Tivoli System Automation

A SAP system has many components, and operation of these components is complex. Simplifying

the operation of the SAP system can help you meet your service level agreements. It can also help

you contain costs while more efficiently using your operations staff by removing repetitive tasks

that are error-prone.

Tivoli System Automation offers system-wide benefits by simplifying the operation of the entire

SAP system. This simplification is particularly important when there are multiple SAP systems to

manage. It is necessary for the various components of the SAP system to be started and stopped in

the proper order. Failure to do this delays the system’s availability.

The SAP system is generally critical to the operation of the business, and human errors can occur.

The use of an automation tool that responds in a consistent way to a particular event can help deliver

continuous operation.

Introduction

As the automation administrator, you implement the IBM Tivoli System Automation for

Multiplatforms product to automate your applications in a UNIX system environment, making the

applications highly available. First, you install the product on all nodes (in your automation domain)

and define the nodes to your automation domain.











•

•

•

•

•

Introduction


Environment

Three Linux systems are available for the exercise. All systems are running in a VMware

environment.

Overview of user IDs and passwords

In the following table is a list of User IDs and passwords to use in class.

Overview of systems and IP addresses

In the following table is a list of systems and IP addresses to use in class.

Purpose User ID Password

System administrator root ibm4es

WebSphere administrator

(Operations Console)

wasadmin wasadmin

SAMP administrator

(Operations Console)eezadmin eezadmin

Node Cluster Application IP-address Purpose

node01 mydom

SAMP

SAP Enqueue srvr

SAMP adapter

192.168.40.101

192.168.40.111

192.168.40.121

192.168.40.103

System base address

floating address

floating address

network tie breaker

node02 mydom

SAMP

SAP ERS

SAMP adapter

192.168.40.102

192.168.40.121

192.168.40.103

System base address

floating address

network tie breaker node03 Not part

of a cluster SAMP

Operations Console

192.168.40.103 System base

address. Network tie

breaker and

reference address for

the RSCT topology

services











•

•

•

•

•

Introduction


Figure 2: SAP configuration

The ABAP SAP Central Services group SAP_ABAP_AX0_ASCS00(ASCS): The ABAP SCSgroup contains six floating resources.:

Figure 3: ABAP SAP Central Services group

Five of those resources are SAP resources with a DependsOn relationship to the Service IP

resource. If you start the ASCS group, the IP resource is started first. When the IP resource is online,

the SAP resources are started in parallel. In addition, the DependsOn relationship has two additional

effects:

• All resources are started on the same node not only because of the DependsOn

relationship, but also due to the collocated member location of the group.

• On failure of the IP resource, all other resources in this group are restarted.

Three resources are mandatory group members as they are the most critical resources: IP address,

Enqueue Server (ES), and Message Server. The other SAP resources SAP Gateway, SAP System

Resource name Description

SAP_ABAP_AX0_ASCS00_ES Enqueue Server

SAP_ABAP_AX0_ASCS00_GW SAP-Gateway

SAP_ABAP_AX0_ASCS00_IP ASCS Service IP address

SAP_ABAP_AX0_ASCS00_MS Message Server

SAP_ABAP_AX0_ASCS00_CO Collector

SAP_ABAP_AX0_ASCS00_SE SAP Log Send Daemon











•

•

•

•

•

Exercise 1: Preparation


Log Collector, SAP System Log Sender, and FileSystem Mount are optional. In case the FileSystem

Mount resource is configured, the IP resource has a DependsOn relationship defined.

If the Enqueue Server or IP resource fails, no restart is attempted. A failover of the whole group is

triggered instead. If the Message Server fails, a restart is first attempted. If this restart fails, System

Automation for Multiplatforms initiates a failover of the whole group. Only the Message Server,

Enqueue Server and IP resource can trigger a failover. If any of the optional three resources failsand cannot be restarted, no failover is initiated.

The ABAP Enqueue Replication Server group SAP_ABAP_AX0_es01_ERS: The Enqueue

Replication Server group contains one mandatory floating resource, the ABAP Enqueue

Replication Server (ERS) itself. The optional FileSystem Mount resource is a non-mandatory

member.

Interaction between Enqueue Server and Enqueue Replication Server: A failover of the ES causes

all resources in the ES group to be moved to the replication server. This applies to ASCS and Java

SCS instances with Enqueue Server replication enabled.


In this exercise, you prepare the workshop if not already done by your proctor.

• Start your Tivoli System Automation for Multiplatforms VMware images

• Verify the cluster configuration

• Login to the Tivoli System Automation for Multiplatforms operations console

Starting the Tivoli System Automation for Multiplatforms

VMware images

If your Tivoli System Automation for Multiplatforms VMware images are not started, ask your

proctor for help. Alternatively, find the node01.vmx, node02.vmx, and node03.vmx files and start

the VMware images by double-clicking each file. No devices need to be connected to the VMware

image. Ignore error messages about no sound. If a question comes up about whether you have











•

•

•

•

•



copied or moved the image, respond moved or keep to avoid problems because of new

MACADDRs and IP addresses.

Figure 4: Start Tivoli System Automation for Multiplatforms VMware image

Log on as User ID root with Password ibm4es.

Verifying configuration

___ 1. Log on as root to both systems node01 and node02.

___ 2. Click the terminal icon to open a terminal session.

___ 3. Query the automation domain status using the following command:

lsrpdomain

It should list automation domain mydom as online.

___ 4. If the automation domain is offline, start it using the following command:

startrpdomain <domain name>

___ 5. Query the status of the individual nodes in your automation domain and start them if

necessary. Use the following commands to query, stop, and start nodes.











•

•

•

•

•



If you have any problems, ask your proctor for help.

Operations console

The operations console was installed to node03 and is used in this exercise. The automation domain

mydom is connected to the operations console. Resources defined in the automation domain can be

monitored, started, and stopped with the connected operations console.

Verifying that the operations console is running

___ 1. Log on as root to system node03 and open a terminal session.

___ 2. Verify that the WebSphere application server server1 is running:

cd /opt/IBM/tsamp/eez/ewas/AppServer/bin/

./serverStatus.sh server1 -user wasadmin -password wasadmin

___ 3. If the operations console is running, you see the following message:

ADMU0508I: The Application Server "server1" is STARTED

If the operations console is not running, you see the following message:

ADMU0509I: The Application Server "server1" cannot be reached. It

appears to be stopped

___ 4. If the server is running, go to step 5. Otherwise, start the server:

./startServer.sh server1

Wait for the completion message:

ADMU3000I: Server server1 open for e-business; process id is …

Action Command

Query nodes of automation domain lsrpnode

Start a node in the automation domain startrpnode

Stop a node in the automation domain stoprpnode











•

•

•

•

•

Exercise 2: Defining automation policy for SAP


Logging in to the Integrated Solutions Console

___ 1. Open a web browser window in one of your nodes or the host and connect to the

Integrated Solutions Console:

http://node03:9060/admin

or

https://node03:9043/ibm/console

___ 2. On the WebSphere Application Server administrative console login panel, log in as user

eezadmin.

___ 3. Expand the administrative tasks for Tivoli System Automation for Multiplatforms and

click SA MP operations console. The empty main panel is displayed, showing that

currently no automation domains are connected to the operations console.

Exercise 2: Defining automation policy for

SAP

The SAP high availability policy defines all SAP components as resources and starts, stops, and

recovers them in a well-defined sequence to provide high availability for your SAP system.

Starting with Tivoli System Automation for Multiplatforms V3.2.1, automation of SAP can be

defined with a wizard which greatly simplifies setup. The wizard has been further improved, for

example, with auto discovery of SAP configuration in Tivoli System Automation forMultiplatforms V3.2.2. If you start the Policy Setup wizard, an XML template is used as the input

file. You must define values for the variables contained in the XML template before you can

activate the corresponding policy. The Policy Setup wizard fills in all values based on your input.

In this exercise, you create a new SAP automation but not activate it.

Each SAP high availability policy consists of a policy template /usr/sbin/rsct/sapolicies/sap/

samsap_templateABAP.tmpl.xml that is tailored by using the same policy wizard. The wizard

stores the results in the policy pool: /usr/sbin/rsct/sapolicies/.

___ 1. To configure the template, run the following command:

sampolicy -w /usr/sbin/rsct/sapolicies/sap/samsap_templateABAP.tmpl.xml

The template file is used to store your SAP automation policy. It asks you the following questions.

If you have time, you can answer all of them or just quickly review them and proceed to the next











•

•

•

•

•



exercise. Depending on your chosen configuration and answers to specific questions, additional

questions are asked.

----------------------------------------------------------------------

System Automation for Multiplatforms Policy Setup Wizard

Policy: SAP ABAP Central Services (ASCS) - Enqueue Replication Server(ERS) HA policy

Overall parameter status: Incorrect

-----------------------------------------------------------------------

Parameter overview

# Parameter Value

-----------------------------------------------------------------------

1 Enter the name of your SA MP domain. Missing

2 Specify the installation directory of your SAP policy script OK

files.

3 Select the IP version used in your cluster. OK

4 Specify the existing SAP system ID (SID) Missing 5 Specify your SAP admin user name. Missing

6 Select your SAP kernel version. Missing

7 Enter your desired prefix for all ABAP resources. OK

8 Enter the nodes where you want to automate your SAP Central Missing

Services Instance for ABAP (ASCS).

9 Specify the instance ID of the SAP Central Services Instance Missing

ABAP (ASCS).

10 Specify the virtual hostname for the Central Services Instanc Missing

for ABAP (ASCS).

11 Specify the virtual IPv4 address for the SAP Central Services Missing

Instance for ABAP (ASCS).

13 Specify the netmask for the virtual ASCS instance IP address. OK

15 Specify the network interface name where your ASCS instance Missing

virtual IP address is activated on each node as alias. The

following network interfaces are available on your local system:

16 Did you configure the additional services gateway, syslog Missing

sender and the syslog collector to be part of the SAP Central Services

Instance for ABAP (ASCS)?

17 Is your ABAP enqueue replication server (ERS) running under Missing

its own instance ID?

19 Do you want to automate the ABAP application servers? OK

1 Enter the nodes where you want to automate the applicatio Missing

servers.

2 Specify all instance names of your application srvrs.Use Missing

the same order as for the nodes in one of the previous questions.

3 Enter all instance IDs of the application servers. Use Missing

same order as for the nodes in the previous question.

4 Enter the start timeout value for your ABAP application OK

servers.

5 Enter the stop timeout value for your ABAP application OK

servers.

20 Did you configure a virtual hostname during installation for at











•

•

•

•

•



Missing

least one of the application servers specified in the previous

question?

21 Do you want SA MP to automate your SAP router? OK

22 Do you want SA MP to automate the SAP Web dispatcher? OK

23 If your database is automated with SA MP in the same cluster, do OK

you want to create startAfter relationships for your application servers?

Select the number of the parameter to start with or one of the following

options:

? Enable help for all parameters

H Disable automatic value harvesting for all applicable parameters

0 Finish

X Cancel

Now you define all parameters. Below all questions and their discovered values are written in italic.

___ 2. Enter 1 to start with the 1st parameter.

___ 3. Enter the name of your SA MP domain. For this exercise it is mydom, which should be

already discovered. For each parameter you can choose

– 1 to edit the current value that has been harvested, if possible

– 3 to proceed to the next parameter

– 4 to harvest again

Select an option:

1 Edit the current value

3 Next 4 Harvest

? Help for this parameter

+ Parameter overview

0 Finish

X Cancel

Enter 3 to proceed to next parameter.

___ 4. Specify the installation directory of your SAP policy script files. /usr/sbin/rsct/sapolicies/

sap

This parameter should already be discovered. Enter 3 to proceed to next parameter.

___ 5. Select the IP version used in your cluster: IPV4.


___ 6. Specify the existing SAP system ID (SID): AX6. The SAP system ID consists of three

characters and is configured during the SAP installation. This parameter should already be

discovered. Enter 3 to proceed to next parameter.











•

•

•

•

•



___ 7. Specify your SAP admin user name: ax6adm. The default SAP admin user name is

composed of the SAP SID (in lower case) and the suffix adm. This parameter should

already be discovered. Enter 3 to proceed to next parameter.

___ 8. Select your SAP kernel version: 7.0. The SAP kernel versions 6.4, 7.0, and 7.1 are

supported for this policy. This parameter should already be discovered. Enter 3 to proceed

to next parameter.

___ 9. Enter your desired prefix for all ABAP resources: SAP_ABAP . This prefix is used as a

prefix for all Tivoli System Automation for Multiplatforms resources that cover ABAP,

for example SAP_ABAP. For later operational tasks, the prefix can be used to start and

stop resources with the same prefix with one single command. You can encode the SAP

solution name, such as PI, ECC, or SCM, which results in a prefix like PI_ABAP.


___ 10. Enter the nodes where you want to automate your SAP Central Services Instance for

ABAP (ASCS). These nodes must be listed by the Tivoli System Automation for

Multiplatforms command lsrpnode for the specified domain. You can use either the longor the short name for a node. An ASCS resource is created for each of the specified nodes.

For this exercise enter node01 and node02.

Tip: Enter 1 to enter a value. Specify the values node01 and node02 for this parameter

separately. Press ENTER to complete your input and return to the window dialog for this

parameter.

___ 11. Specify the instance ID of the SAP Central Services Instance for ABAP (ASCS): 00. In this

policy, this instance ID is used to identify the instance directory that contains all necessary

files for the ASCS instance.

This parameter should be already discovered. Enter 3 to proceed to next parameter.

___ 12. Specify the virtual host name for the Central Services Instance for ABAP (ASCS):

vhASCS00. This host name is used as a virtual host name for the Central Services Instance

for ABAP (ASCS). Enter the same virtual host name that was used for sapinst

SAPINST_USE_HOSTNAME=-virt_hostname- during the ASCS installation. This

parameter should already be discovered. Enter 3 to proceed to next parameter.

___ 13. Specify the virtual IP V4 address for the SAP Central Services Instance for ABAP (ASCS).

This IP address is used as a virtual IP address for the floating ASCS instance. Enter

192.168.40.111.

___ 14. Specify the netmask for the virtual ASCS instance IP address. Enter the netmask for thesubnet of the virtual ASCS instance IP address. For this exercise enter a netmask of

255.255.255.0.

___ 15. Specify the network interface name where your ASCS instance virtual IP address is

activated on each node as alias. The following network interfaces are available on your

local system: eth0. The network interface specifies to which network interface on each

node the virtual ASCS instance IP address can be bound, for AIX an example is en0, for

Linux, an example is eth0. This network interface needs to be available on all nodes where











•

•

•

•

•



the ASCS instance is automated. This parameter should already be discovered, however

you have to enter eth0. Enter 3 to proceed to next parameter.

___ 16. Did you configure the additional services gateway, syslog sender and the syslog collector

to be part of the SAP Central Services Instance for ABAP (ASCS)? The configuration of

theses additional services helps in keeping the whole ASCS stack highly available. If you

answer this question with yes, the gateway, syslog sender, and the syslog collector is kepthighly available using Tivoli System Automation for Multiplatforms. You can only

automate all three services together or not automate them at all. Answer yes.

___ 17. Is your ABAP enqueue replication server (ERS) running under its own instance ID? Yes.

The ABAP Enqueue Replication Server can run under its own instance ID, or it can run

under the instance ID of the Enqueue Server (ES). The setup depends on the way SAP has

been installed and configured. If you answer this question with no, the policy assumes that

the ERS is running under the same instance ID as the ES. Answer yes.

___ 18. Specify the instance name of the ERS instance: ERS10. This parameter should already be

discovered. Enter 3 to proceed to next parameter.

___ 19. Do you want to configure a virtual host name for your ABAP enqueue replication server

(ERS)? The definition of a virtual host name for a ABAP SAP Enqueue Replication Server

is optional. If you answer with yes, you must specify this virtual host name in the next

question. Answer yes.

___ 20. Specify the virtual hostname of the ERS instance. node02. This parameter should already

be discovered. Enter 3 to proceed to next parameter.

___ 21. Do you want to automate the ABAP application servers? Yes. The ABAP application

servers host the applications and serve the user requests. Automation of the ABAP

application servers is recommended, but optional. Choose yes if you want to automate theABAP application servers. Answer no.

___ 22. Do you want SA MP to automate your SAP router? Answer no.

___ 23. Do you want SA MP to automate the SAP Web dispatcher? Answer no.

___ 24. If your database is automated with SA MP in the same cluster, do you want to create

startAfter relationships for your application servers? A startAfter relationship is created

for each Application Server. If you want to create startAfter relationships to a database, the

database must be automated in the same cluster as SAP. Answer no.

___ 25. At the end of the questions, enter 0 to finish. The result is like the following example:Do you want to activate the policy now?

1 Yes, activate as new policy

2 Yes, activate by updating currently active policy

3 No











•

•

•

•

•

Exercise 3: SAP Operations - Introduction


To activate the new policy requires that all resources of the current policy are offline. Do not

activate the new policy as the simulated resources would not work with your policy. If you

accidentally activated it, you can activate the saved policy with the following command:

sampolicy -a /usr/sbin/rsct/sapolicies/sap_policy3.xml

Now, you have successfully configured one SAP cluster, but there might be 10 more similarclusters. You can copy the xml file with the answers to those systems and run the wizard with the

xml file. If the SAP system is installed identically, the only things that have to be changed are the

Domain Name, NodeNames, virtual host names, the SAP SID, and IP addresses.


In this exercise, you use the browser-based Operations Console of IBM Tivoli System Automation

for Multiplatforms to operate a cluster and the web server running in it. You see how IBM TivoliSystem Automation for Multiplatforms works during system failures.

Objectives

The purpose of these exercises are to:

• Exclude a node from and include a node in automation

• Display resource status information

• Start and stop resources by using requests

• Move resources

• Test system behavior with critical resources when losing the quorum

Introduction

As the system operator, you want to use IBM Tivoli System Automation for Multiplatforms to

operate a cluster and the critical SAP resources running in it. You are required to start and stop

applications, free systems for maintenance, and test application failover with different tie breakers.

The graphical user front end of IBM Tivoli System Automation for Multiplatforms is the Tivoli

System Automation operations console. It can be used by operators to monitor and control the

availability status of all automated resources representing your business applications.

The operator can monitor all automated resources in the enterprise environment using a single

console. The Integrated Solutions Console provides a common administrative console for multiple











•

•

•

•

•



products. Tivoli System Automation for Multiplatforms is one of these products. The Tivoli System

Automation operations console, the policy editor, and additional administrative tasks that are

specific to Tivoli System Automation are accessed from the administrative console of Integrated

Solutions Console, which is displayed in a web browser window.

Operations console layout

The main panel of the System Automation operations console is divided into several areas, as

shown in the following screen capture.

Figure 5: Tivoli System Automation operations console

Topology tree

This tree shows the domain hierarchy by showing clusters and systems. It provides a view of the

physical topology. At the top is your mydom domain. The topology tree is divided into four

columns:

• The Topology column shows the automation domains and the nodes that belong to adomain in a hierarchical view.

• The Status column shows the health status of the domain.

• The Located here column is used to identify by which domain a resource is hosted and on

which node or nodes it is located.

• The OS Name column shows the operating system of the domain.











•

•

•

•

•



When a node is not online, the icon is greyed-out. To select an element in the topology tree, you

click the name of the element. You click the twistie in front of a domain icon to expand or collapse

the nodes belonging to the domain.

Resources section

This section shows the automated applications for the domain selected in the topology tree. The

resources section has the following areas:

• Section header: The section header displays the name of the domain or node that is

currently selected in the topology tree.

• View and Search: The View and Search functions allow you to limit the scope of the

resource table.

– Resource table with resource name and compound state. When a resource is not

online, the icon is greyed-out. – To select a resource in the resource table, you click the name of the resource.

Information area

This area shows the details about the current selection. On the pages in the information area,

controls are available for you to perform actions on the selected element. In the information area,

you can use tabs to switch between pages. Which pages are displayed and what they contain

depends on the type of element that is currently selected:

• For domains you see domain name, status, and log on the general page.

• Other pages show policy, history and additional information.

For resources you have a general page with information like name, class, owner, detailed status, and

action buttons to enter and cancel request against the resource. Additional tabs might show

relationships, location, history, and additional information.

Help

• Use the Help link in the top right of the Integrated Solutions Console to open the online

help system. The online help index for all Integrated Solutions Console deployed products

is opened from here.

• Use the question mark in the portlet title bar to get the online help for the panel that is

currently displayed.











•

•

•

•

•

Exercise 4: Displaying defined resources and relationships


Exercise 4: Displaying defined resources and

relationships

In this exercise, you list the defined resource groups and their members, including their

relationships.

___ 1. Explore the layout of the operations console.

___ 2. Expand mydom to show its systems. You should see two nodes, both as online.

___ 3. Click the mydom domain in the topology tree to display all defined resource groups in the

resource tree.

___ 4. Select the Resources section. It shows the automated applications for the domain selected

in the topology tree. It provides a logical view of the business applications and their

components.

___ 5. Expand the SAP_ABAP_AX0_ASCS00 resource group by clicking it to show its

members. You should see the six members listed in the following table, all offline.

Resource name Description

SAP_ABAP_AX0_ASCS00_ES Enqueue Server

SAP_ABAP_AX0_ASCS00_GW SAP-Gateway

SAP_ABAP_AX0_ASCS00_IP ASCS Service IP address

SAP_ABAP_AX0_ASCS00_MS Message Server

SAP_ABAP_AX0_ASCS00_CO Collector

SAP_ABAP_AX0_ASCS00_SE SAP Log Send Daemon











•

•

•

•

•



Figure 6: SAP_ABAP_AX0_ASCS00 resource group

___ 6. Click the Additional Info tab to show the dynamic attributes, including detailed status.

Analyze the detailed status.

Figure 7: ASCS dynamic attributes

CompoundState: Overall status of the resource group including group dependencies. An

example is Satisfactory. The resource or group has reached the requested user status.













•

•

•

•

•



___ 8. Click the Relationships tab to see forward and backward relationships of the selected

resource.

Figure 9: Enqueue Server relationships

Forward relationships

Forward relationships point from the Enqueue Server to so-called supporting resources.

Forward relationships are a dependency that the Enqueue Server has.

The Collocated relationship to SAP_ABAP_AX0_es01_ERS, which is the Enqueue

Replication Server, ensures with its condition IfNotOffline that the Enqueue Server is

started where the Enqueue Replication Server is running. This is required. After an

Enqueue Server outage, the Enqueue Replication Server has a backup of all transactions,which can only be transferred to the Enqueue Server when both are in the same system.

The DependsOn relationship to SAP_ABAP_AX0_ASCS00_IP, which is the ASCS

Service IP address, ensures that the Enqueue Server is only started when the ASCS

Service IP address is online. Additionally, the DependsOn relationship includes a

collocation relationship, making sure that both are on the same system.

Backward relationships

Backward relationships point to the Enqueue Server. They are a dependency that the other

resource has to the Enqueue Server.

The most important one is the Anticollocated relationship toSAP_ABAP_AX0_es01_ERS, which is the Enqueue Replication Server. It ensures that

the Enqueue Replication Server is not started where the Enqueue Server is running. This

avoids a single point of failure. This relationship is not in conflict with the Collocated

relationship as relationships are only evaluated when required to determine whether all

dependencies for a start or stop request can be fulfilled. After the request has been

satisfied, these two relationships are no longer enforced. Also, for a start request against

the Enqueue Server, only its forward relationships are evaluated.











•

•

•

•

•

Exercise 5: Starting SAP


___ 9. Click one of the constituents. The information area now displays an IBM.Application

resource and its status.

___ 10. Click the Additional Info tab to show the persistent and dynamic attributes, including

detailed status. Analyze the policy, like start, stop and monitor commands and timeouts,

and the user ID used to execute the scripts. See the detailed status on page 2.

Figure 10: Constituents persistent and dynamic attributes


In this exercise, you start and stop resource groups. The assumption is that your resource groups are

not running. If not, you can reverse the steps for start and stop.

___ 1. As an alternative to the Integrated Solutions Console, you can use a terminal session on

node01 or node02 to start all SAP resources with a single command that changes the

nominal state:

chrg -o online -s "Name like 'SAP_ABAP%'"

You can check SAP resource status with the following command:

lssam -V -top











•

•

•

•

•



The -top option dynamically refreshes status.

The -V option displays details like IP addresses and dependencies.

All resources are displayed when you specify a selections string.

lssam -V -top -s "Name like 'SAP_ABAP%'"

Figure 11: lssam display

The following list explains the two-character shortcut for the relationship types:

• "DO" - DependsOn - Specifies a combination of source StartAfter target, target StopAfter

source, source ForcedDownBy target, source Collocated to target and target Collocated to

source.

• "SA" - StartAfter - Specifies that the source resource is to be started after the target

resource.

• "CO" - Collocated - Specifies that the source resource is always located on the same node

as the target resource.

• "AC" - AntiCollocated - Specifies that the source resource is always located on a different

node as the target resource.

• "IS" - IsStartable - Specifies that the source resource and its target resources are startable.

___ 2. When you want to use the Integrated Solutions Console, navigate to the

SAP_ABAP_AX0_ASCS00 resource group.











•

•

•

•

•

Exercise 6: Excluding a node from automation


___ 3. Start the SAP_ABAP_AX0_ASCS00 resource group by clicking Request Online in the

General tab.

___ 4. Enter a meaningful comment in the next panel.

___ 5. In the resource tree, watch the changing states of the SAP_ABAP_AX0_ASCS00

resource group. Why are there exclamation marks in front of the

SAP_ABAP_AX0_ASCS00 resource group members?

_________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ ______________________________________________________________

Note the exclamation mark at the domain level.

Note the yellow icon after the observed state. It indicates an operator request in progress.

When the operator request has been satisfied, the icon is green.

___ 6. Click View Requests. You see your request at the top as the winning request. Below it is a

vote that is generated from the Nominal State = Offline (from Policy).

___ 7. In the resource tree, start the SAP_ABAP_AX0_es01 resource group as well. After it is

online, SAP is protected against any resource or single system outage.

Exercise 6: Excluding a node from

automation

The purpose of these exercises is to exclude a node from and include a node into automation.

___ 1. Expand mydom to show its systems. You should see your two nodes, both as online.

___ 2. Click the node hosting the Enqueue Server.











•

•

•

•

•



On which system is the Enqueue Server running?________________________

Figure 12: Exclude a node from automation

___ 3. If the Enqueue Server constituent resource runs on the same system as the samadapter

resource that is required for interfacing with the Integrated Solutions Console, move the

SAP_ABAP_AX0_ASCS00 resource group away from that system using the last exercise

in this unit.

Note: In this case, the Enqueue Replication Server is moved to the other node automatically.











•

•

•

•

•



___ 4. Exclude the node hosting the Enqueue Server from system automation by clicking

Exclude Node in the General tab.

Figure 13: Excluding node02 from automation

___ 5. Verify whether the Enqueue Server is running and determine the hosting system.

Is the Enqueue Replication Server still running?________________________











•

•

•

•

•

Exercise 7: Suspending automation for a resource


Why is the Enqueue Replication Server not running?

______________________________________________________________

___ 6. Include the excluded node back to system automation by clicking Include Node in the

General tab.

Is the Enqueue Replication Server now running?________________________

Exercise 7: Suspending automation for a

resource

A lock or suspend automation request suspends a resource group and its contained resources from

automation. The ControlState changes to ResourceSuspended.

___ 1. Navigate to the SAP_ABAP_AX0_ASCS00 resource group.











•

•

•

•

•

Exercise 7: Suspending automation for a resource


___ 2. Suspend the SAP_ABAP_AX0_ASCS00 resource group by clicking Suspend

Automation in the General tab.

Figure 14: Suspend ASCS automation

___ 3. Stop the Enqueue Server on the system where it runs by using the following command:

/tmp/appcmd/appcmd setcfg ascses:Monitor 2

___ 4. Verify whether the Enqueue Server still runs. Tivoli System Automation forMultiplatforms should not have recovered it. The other SAP_ABAP_AX0_ASCS00

resource group members should still be running.

___ 5. Click the node that hosted the Enqueue Server. This action gives you a better view of the

amazing action coming up.

___ 6. Resume the SAP_ABAP_AX0_ASCS00 resource group by clicking Resume

Automation in the General tab.











•

•

•

•

•

Exercise 8: Testing application failover


___ 7. Verify whether the Enqueue Server runs again. Tivoli System Automation for

Multiplatforms should have recovered it.

On which system is the Enqueue Server running?________________________

Why has the Enqueue Server been moved?

________________________________________________________________


To induce a hard system failure, you turn off a system during this exercise. Confirm that the

VMware settings permit a hard turn off of a system. If in doubt, ask the instructor.

___ 1. Determine the system hosting the Enqueue Server.

___ 2. If the SAP_ABAP_AX0_ASCS00 resource group runs on the same system as the

samadapter, move the SAP_ABAP_AX0_ASCS00 resource group away from that system

using the last exercise in this unit.

___ 3. Turn off the system currently running the Enqueue Server using the VMware console or

by entering command:

shutdown now -h

Is the Enqueue Server running on the remaining system? ___________











•

•

•

•

•



Is the Enqueue Replication Server still running?________________________

Figure 15: node02 resources are offline

Figure 16: node02 resources have failed over to node01











•

•

•

•

•

Exercise 9: Moving requests


___ 4. Confirm that the remaining automation domain has operational quorum by clicking the

Additional Info tab of the mydom domain (Attribute sa_status_quorum). The cluster is

operable only if the majority of the nodes are online. This condition is called operational

quorum.

Figure 17: Operational quorum

___ 5. Turn on the offline system and ensure that it has joined the automation domain.


A move request shifts members of a single top-level resource group to other nodes. Excluding a

node affects all resources on a node. A move request affects the members of the moved resource

group and dependent resources. Only one move request at a time can be active.

Move requests are useful for performing software maintenance on certain nodes and re-establishing

load balancing between nodes after outages under the following conditions:

• If the resource group is collocated (move away from the current node)

• If the resource group is distributed on several nodes (move away from certain nodes)











•

•

•

•

•



Perform the following steps:

___ 1. Navigate to the Location Info tab of the SAP_ABAP_AX0_ASCS00 resource group.

___ 2. Click Move. The following panel is displayed.

Figure 18: Move request











•

•

•

•

•



___ 3. Click Move to watch the move taking place.

Figure 19: Move request being executed











•

•

•

•

•

Exercise 10: Stopping SAP


___ 4. Verify whether the Enqueue Server is running and determine the hosting system.

Figure 20: Move request done


In this exercise, you start and stop resource groups. The assumption is that your resource groups are

not running. If not, you can reverse the steps for start and stop.

___ 1. Navigate to the SAP_ABAP_AX0_ASCS00 resource group.

___ 2. Stop the SAP_ABAP_AX0_ASCS00 resource group by clicking Cancel Request in the

General tab. After cancelling the request, the nominal state = offline wins.

___ 3. In the resource tree, watch the changing states of the SAP_ABAP_AX0_ASCS00

resource group. Why are there exclamation marks in front of theSAP_ABAP_AX0_ASCS00 resource group members?











Summary

You have used the new SAP wizard of Tivoli System Automation for Multiplatforms V3.2.2 to

define automation in your own cluster. You have learned to start and stop an entire SAP cluster with

a single command. You have performed a critical outage scenario of the SAP central instance and

watched Tivoli System Automation for Multiplatforms recovering your SAP application.

Documents

LabF06 Pulse12 SAP High Availability[1]