Beruflich Dokumente
Kultur Dokumente
IBMs statements regarding its plans, directions, and intent are subject to change or withdrawal
without notice at IBMs sole discretion.
Information regarding potential future products is intended to outline our general product
direction and it should not be relied on in making a purchasing decision.
The information mentioned regarding potential future products is not a commitment, promise,
or legal obligation to deliver any material, code or functionality.
Information about potential future products may not be incorporated into any contract.
The development, release, and timing of any future features or functionality described for our
products remains at our sole discretion.
Please refer to the developerWorks terms of use for more information.
-i-
Table of Contents
Chapter 19. SAP High Availability Policy................................................................5
High availability concepts for a SAP system.....................................................5
Single Point of Failure (SPOF).............................................................................6
(A)SCS node................................................................................................6
Primary AS node...........................................................................................6
Additional Application Server node..............................................................7
Web Dispatcher and SAProuter node..........................................................7
Host Agents..................................................................................................7
Database node.............................................................................................7
NFS node.....................................................................................................7
SAP clients...................................................................................................7
Example of a two-node setup...............................................................................7
SAP HA setup options...........................................................................................8
ASCS HA setup..............................................................................................10
ASCS HA setup..........................................................................................10
Primary and Additional AS node.................................................................10
Web Dispatcher and SAProuter node (optional)........................................11
Database HA setup.....................................................................................11
NFS HA setup.............................................................................................11
Java SCS HA setup........................................................................................12
Java SCS HA setup....................................................................................12
Primary and Additional AS node.................................................................12
Web Dispatcher and SAProuter node (optional)........................................13
Database HA setup....................................................................................13
NFS HA setup.............................................................................................13
Location of SAP instance directories..................................................................14
Database HA installation setup...........................................................................14
SAP Central Services and database in the same HA cluster.........................14
SAP Central Services and database on different HA clusters........................14
High availability for DB2 and other databases...............................................15
DB2 HA Setup............................................................................................15
High availability with other databases........................................................15
NFS HA installation setup...................................................................................15
High availability impact.......................................................................................16
Interactions between Enqueue Server and Enqueue Replication Server......18
Database host.................................................................................................20
NFS server......................................................................................................20
SAP Host Agent..............................................................................................20
SAP Web Dispatcher......................................................................................21
SAProuter.......................................................................................................21
Planning the SAP HA solution........................................................................... 21
Installing a new high-availability SAP system............................................21
Exporting an existing non-HA SAP system................................................21
Post-installation tasks.................................................................................21
Installing a new ASCS or SCS HA SAP system.................................................21
-1-
Prerequisites...................................................................................................22
Prerequisite installation tasks.....................................................................22
Initial installation on primary node..................................................................23
Initial installation on failover node..................................................................23
Required adaptions of SAP profiles................................................................24
Verifying the initial installation.........................................................................24
Installing and setting up System Automation for Multiplatforms...................27
Prerequisites.......................................................................................................27
Installing System Automation for Multiplatforms on all cluster nodes................27
Granting System Automation for Multiplatforms access for the <sapsid>adm...28
Setting up the domain.........................................................................................28
Setting up a tie breaker.......................................................................................29
Enabling syslog daemon.....................................................................................29
Installing the SAP HA policy feature...................................................................29
Packaging.......................................................................................................29
Installing the SAP HA policy feature license...................................................30
Restrictions.....................................................................................................30
Enabling the SAP HA Connector........................................................................30
Configuring and activating the SAP HA solution.............................................31
The SAP HA policy..............................................................................................31
ASCS HA policy..............................................................................................32
The ABAP SAP Central Services group (ASCS).......................................35
The ABAP Enqueue Replication Server group..........................................35
Interactions between Enqueue Server (ES) and Enqueue Replication
Server (ERS)..............................................................................................36
Java SCS HA policy........................................................................................39
The Java SAP Central Services group.......................................................42
The Java Enqueue Replication Server group............................................43
Parts of the ABAP and Java policies with the same behavior........................43
The ABAP and Java Application Server (AS) groups.................................43
The ABAP and Java SAProuter group.......................................................43
The ABAP and Java SAP Web Dispatcher group......................................44
The Host Agent groups...............................................................................44
Policy parameters...............................................................................................44
SAP ABAP Central Services (ASCS) -Enqueue Replication Server (ERS) HA
policy (ABAP)..................................................................................................44
SAP JAVA Central Services (SCS) -Enqueue Replication Server (ERS) HA
policy (Java)....................................................................................................54
Migration steps....................................................................................................64
Overview.........................................................................................................64
Migration considerations.....................................................................................64
Migrating the SAP HA policy.............................................................................64
Upgrade your SAP cluster to System Automation for Multiplatforms 3.next..65
Granting System Automation for Multiplatforms access for the <sapsid>adm
........................................................................................................................65
Create a new SAP HA automation policy.......................................................65
-2-
-3-
Figures
Figure 1: Components of a distributed SAP system.....................................................6
Figure 2: Example of a two-node setup........................................................................8
Figure 3: ASCS HA setup............................................................................................10
Figure 4: Java SCS HA setup......................................................................................12
Figure 5: Initial startup of (A)SCS................................................................................19
Figure 6: Failure of (A)SCS and recovery of the enqueue table.................................19
Figure 7: Movement of the Enqueue Replication Server............................................20
Figure 8: ASCS HA policy............................................................................................32
Figure 9: Relationships between the Enqueue and Message Servers and the
Enqueue Replication Server........................................................................................36
Figure 10: Java SCS HA policy...................................................................................39
Index of Tables
Table 1: ABAP resources and the corresponding components...................................11
Table 2: Java resources and the corresponding components....................................13
Table 3: Fully implemented high availability solution for SAP.....................................17
Table 4: Resources and resource groups of the ASCS HA policy..............................33
Table 5: Description and examples of placeholders for ABAP resource names.........35
Table 6: Resources and resource groups of the Java SCS HA policy........................40
Table 7: Description and examples of placeholders for JAVA resource names..........42
Table 8: ABAP policy parameters................................................................................44
Table 9: Java policy parameters..................................................................................54
Table 10: Location for the SAP HA XML template files...............................................66
Table 11: Planned Outages.........................................................................................68
Table 12: Unplanned outages......................................................................................70
Table 13: SAP HA solution checklist............................................................................71
-4-
The high availability solution for SAP uses System Automation for Multiplatforms to
automate all SAP components. System Automation for Multiplatforms detects failed
components, restarts them or initiates a failover. This setup will also help to reduce
the operational complexity of an SAP environment and to avoid operator errors
resulting from this complexity.
-5-
Host
HostAgent
Agent
Host
HostAgent
Agent
Host
HostAgent
Agent
(A)SCS node
The (A)SCS node consists of the standalone components Enqueue Server
(ES) and Message Server (MS) that operate as SAP Central Services instance.
Depending on the SAP solution the SCS Node contains the ABAP or Java
components.
In addition there is an SAP Instance Agent running for each instance.
SAP uses the following terms and abbreviations:
ASCS
SCS
(A)SCS
Primary AS node
The Primary AS node consists of the Primary Application Server (PAS)
-6-
instance running the SAP Services Dialog, Update, Batch, Gateway and
Spool. An Instance Agent accompanies the Primary Application Server.
Note:
Each machine or LPAR must be capable to run all instances. These are the main SAP
instances, which must be made highly available by System Automation for
Multiplatforms. High availability for application servers is achieved by having at
least two application server instances (PAS and AAS) as fixed resources.
If the setup contains the database server, SAProuter or SAP Web Dispatcher, they
should be made highly available as well.
ASCS HA installation
-9-
ASCS HA setup
This ASCS HA setup is used for ABAP only SAP solutions.
ASCS HA setup
The ASCS HA setup consists of at least two SCS nodes which run the ASCS
and ERS instances. Under regular conditions the ERS will always be started
on the node where the ASCS is not running. This failover setup has no
downtime due to fast failure detection and in-memory data exchange between
ES and ERS in case the ASCS must be moved to the failover node. During
the failover, the virtual IP address for the ASCS is moved to the failover node
too, so its addressing remains unchanged.
Primary and Additional AS node
The Primary AS node and the Additional AS nodes consist of ABAP
Application Servers which will be restarted in place in case of software
failures. Protection against hardware outages is done by setting up multiple
Application Servers on different hardware. Therefore the System Automation
for Multiplatforms concept for SAP HA does not consider failovers of
Application Servers to other nodes because Application Server restarts take a
lot of time. Other Application Servers must be sized to take the additional
workload from failing servers.
- 10 -
ABAP Resources
ABAP resources
SAP component
ABAP SAP Central Services (ASCS) instances
using an own virtual hostname on two nodes.
Enqueue Replication Server using an own
virtual hostname on two nodes.
Database Server instances using an own virtual
hostname on two nodes.
Primary Application Server for ABAP instance
on first node.
Additional Application Server for ABAP
instances on other nodes.
Host Agent
Web Dispatcher instances using an own virtual
hostname on two nodes.
SAProuter setup on two nodes.
- 11 -
- 12 -
Java Resources
Java resources
Java independent
resources (optional)
SAP component
Java SAP Central Services (SCS) instances using an
own virtual hostname on two nodes.
Enqueue Replication Server using an own virtual
hostname on two nodes.
Database server instances using an own virtual
hostname on two nodes.
Primary Application Server for Java instance on first
node.
Additional Application Server for Java instances on
other nodes.
Host Agent
Web Dispatcher instances using an own virtual
hostname on two nodes.
SAProuter setup on two nodes.
- 13 -
- 14 -
Further links:
How to setup and run a DB2 LUW database server or client see SAP Note
No. 960843: DB6: Installation SA MP
For more information about high availability with SAP on DB2, refer to
IBM DB2 for LUW Cluster Using IBM Tivoli SA MP SAP Community
Network link: http://scn.sap.com/docs/DOC-14508.
- 16 -
Failing resource
Database
Impact
Rollback of transactions
Remote application servers
fail over automatically to
the other database node
Enqueue Server
No impact.
Enqueue
Replication
Server
Message Server
Application
Server instance
SAP-Gateway
Web Dispatcher
SAProuter
Actions
SA: Restart or Failover
Database (Optional setup in
same HA cluster)
User: Restart transactions
SA: Failover Enqueue Server
Remote application servers
automatically reconnect to
the other database node.
- 17 -
Actions
SA: Restart or Failover NFS
server
(Note: The HA setup of SAP
and NFS on the same cluster
nodes is not supported).
- 18 -
virtual
virtual
IPIP
address
address
virtual
IP
address
If system 1 fails, system 2 takes over the role of the first one as shown in Figure 6 on
page 19:
1. The virtual IP address related to the Enqueue and Message Servers is taken
over to system 2.
2. Enqueue and Message Servers are restarted on system 2.
3. The enqueue table is rebuilt from the shadow table hosted by the Enqueue
Replication Server.
4. The Enqueue Replication Server stops after the Enqueue Server has rebuild
the enqueue table.
5. The Application Servers reconnect to the Enqueue and Message Servers.
System Automation for Multiplatforms will handle this complete failover process.
The failover is fully transparent to the application. Enqueue locks are preserved and
transactions continue to run.
virtual
virtual
IPIP
address
address
virtual
IP
address
- 19 -
After a successful failover of the Enqueue Server, the Enqueue Replication Server is
no longer needed on system 2 and therefore stops itself. If another system is
available, the Enqueue Replication Server is started by System Automation for
Multiplatforms on that system and a new shadow enqueue table is established. This is
shown in Figure 7 on page 20.
virtual
virtual
IPIP
address
address
virtual
IP
address
Database host
If the database server is not available, the entire SAP system becomes unavailable.
The database host maintains the persistent storage for the entire SAP system. Once
the database is available again, all uncommitted transactions are rolled back and the
SAP system continues to run.
System Automation for Multiplatforms can be used to automate the start, stop,
monitor, restart and failover of the database server. For more information, refer to
High availability for DB2 and other databases on page 15.
NFS server
A SAP HA setup requires shared access for directories like global, profile, trans.
On UNIX and Linux systems you need NFS to share files. Thus the availability of
the file systems together with the NFS server is critical.
Note: NFS file access is not transactional. There is no commit or rollback logic. In
case of system failure or communication loss there is no guarantee that the
last written data has been stored on disk.
System Automation for Multiplatforms can be used to automate the start, stop,
monitor, restart and failover of the NFS server. For more information, refer to NFS
HA installation setup on page 15.
SAP Host Agent
The SAP Host Agent is a tool that you can use for monitoring and controlling SAP
and non-SAP instances, operating systems, and databases. It is installed
automatically during the installation of new SAP instances with SAP kernel 7.20 or
- 20 -
higher.
The SAP Host Agent provides features for SAP instance discovery and inventory,
instance control, database monitoring and management, and operating system
monitoring using saposcol. It aids in system or instance provisioning by hosting the
infrastructure of SAP NetWeaver Landscape Virtualization Management (LVM).
SAP Web Dispatcher
The Web Dispatcher is the entry point for all external HTTP requests and the
interface between all HTTP clients and the SAP system. The Web Dispatcher can
work as load balancer for incoming requests which are distributed among all
available application servers.
When the SAP Web Dispatcher fails, clients cannot connect to the SAP subsystems
using HTTP request.
SAProuter
The SAProuter controls the access between the external network and the SAP
subsystem.
In case of a failure of the SAProuter, no connections can be processed using this
proxy.
Ensure to set the correct ulimits and umask values for your environment as it
is documented in the SAP product installation guide.
Register permanent entries for the virtual hostnames in the DNS server.
Ensure that the network interfaces that you want to use have the same name
on each system. For each virtual IP address defined in the HA policy, an
equivalency of network interfaces will be created. Only network interfaces
with the same name on each node can be part of each equivalency.
4. Database instance
sapinst SAPINST_USE_HOSTNAME=<virtual DB hostname>
Database instance
sapinst SAPINST_USE_HOSTNAME=<virtual DB hostname>
3. Use the sapinst command to execute the following installation tasks using the
installation option SAP-System "High-Availability System":
- 23 -
It is required to disable the SAP restart capability for the Enqueue Server and
the Enqueue Replication Server in the appropriate profiles. Otherwise the
automatic restart of SAP (executed by startsapsrv) mismatches with
System Automation for Multiplatforms start functionality and will cause
problems with the automation. Set the SAP profile parameter for EN and ERS
to Start_Program_<NR> in the EN and ERS profiles in the
/sapmnt/<SID>/profile directory.
For all servers other than EN and ERS set the SAP profile parameters
Restart_Program_<NR>.
Disable autostart of all SAP instances in all their profiles by commenting the
line Autostart = 1.
In order to share the enqueue backup file within the Linux or AIX cluster, it
should be stored on the NFS mounted /sapmnt/<SID>/global directory.
This way it can be accessed from all nodes in the cluster where the Enqueue
Server can start.
Add the following parameter to the (A)SCS profile for sharing the enqueue
backup files between nodes:
enque/backup_file = $(DIR_GLOBAL)/ENQBCK(A)SCS
All SAP ABAP services that run on the Primary Application Server
installation must also be manually configured in the instance profiles of the
Additional Application Server. The SAP ABAP services are:
Batch service
Update/Update 2 service
Spool service
Through this setup all SAP ABAP services are running on each Application
Server and are no single points of failure (SPOF) any more.
The SAP HA connector must be enabled in the default profile. This step
requires that System Automation for Multiplatforms is already installed on
the cluster nodes, so it probably must be done at a later time. Refer to
Enabling the SAP HA Connector on page 30 on how to enable the SAP HA
connector for your platform.
The syntax of the ifconfig commands shown below applies to the AIX operating
system.
Prerequisites:
2.
Start ASCS and the Primary Application Server instance on the first node:
ifconfig <interface_name> <ASCS_IP_alias> netmask <IP_netmask> alias up
startsap r3 ASCS<ID>
startsap r3 DVEBMGS<ID>
3.
Stop ERS and the Additional Application Server instance on the second node:
stopsap r3 ERS<ID>
stopsap r3 D<ID>
ifconfig <interface_name> <ERS_IP_alias> delete
2.
Stop ASCS and the Primary Application Servers instances on the first node:
stopsap r3 DVEBMGS<ID>
stopsap r3 ASCS<ID>
ifconfig <interface_name> <ASCS_IP_alias> delete
3.
4.
5.
Check replication status for ERS instance on the first node using ensmon
utility:
ensmon pf=/usr/sap/<SID>/ERS<ID>/profile/<SID>_ERS<ID>_<node1>
Select task Get replication information. The output looks like this
...Replication is enabled in server, replication server is connected.
Replication is active...
6.
7.
8.
Logon to the Primary Application Server for ABAP using the SAP graphical
user interface (SAPGUI).
Logon to the Additional Application Server for ABAP using the SAP
graphical user interface (SAPGUI).
Logon to the Primary Application Server for Java using a Web browser. The
default is:
http://node1:5<ID>00/index.html
Logon to the Additional Application Server for Java using a Web browser.
The default is:
http://node2:5<ID>00/index.html
Stop ERS and Primary Application Server instance on the first node:
stopsap r3 DVEBMGS<ID>
stopsap r3 ERS<ID>
ifconfig <interface_name> <ERS_IP_alias> delete
2.
Stop ASCS and Additional Application Servers instances on the second node:
stopsap r3 D<ID>
stopsap r3 ASCS<ID>
ifconfig <interface_name> <ASCS_IP_alias> delete
3.
4.
5.
Check replication status for ERS instance on the second node using ensmon
utility:
ensmon pf=/usr/sap/<SID>/ERS<ID>/profile/<SID>_ERS<ID>_<node2>
Select task Get replication information. The output looks like this
...Replication is enabled in server, replication server is connected.
Replication is active...
6.
7.
8.
Logon to the Primary Application Server for ABAP using the SAP graphical
user interface (SAPGUI).
Logon to the Additional Application Server for ABAP using the SAP
graphical user interface (SAPGUI).
Logon to the Primary Application Server for Java using a Web browser. The
default is:
http://node1:5<ID>00/index.html
- 26 -
Logon to the Additional Application Server for Java using a Web browser.
The default is:
http://node2:5<ID>00/index.html
Check if you have the right prerequisites for System Automation for
Multiplatforms in a cluster environment : Prerequisites on page 27
Grant access on each node for the sap user ID: Granting System Automation
for Multiplatforms access for the <sapsid>adm on page 28
Activate the feature license: Installing the SAP HA policy feature on page
29
Prerequisites
Refer to the following chapter for UNIX and Linux: Prerequisites on page nnn
For more information about the installation refer to Installing IBM Tivoli System
Automation on UNIX and Linux on page nnn.
2. Create the SAP domain for System Automation for Multiplatforms, where
sap is the domain name (you might use another name of your choice):
mkrpdomain sap <node1> <node2>
- 28 -
OpState
Online
Online
RSCTVersion
3.1.5.3
3.1.5.3
For more information on setting up a domain, refer to IBM Tivoli System Automation
for Multiplatforms Administrator's and User's Guide.
CD: Install the SAP HA policy feature license from the CD "IBM Tivoli
System Automation for Multiplatforms 3.next High Availability for SAP".
The license file is located in the directory SAM3nextFeatSAP/license.
- 29 -
To verify that the feature license has been successfully installed, issue the following
command:
samlicm -s
The name of the SAP HA policy feature should appear as value of the Product
Annotation field in the output of the command. For example:
...
Product Annotation: SA for MP - SAP HA policy
Creation date: Fri Dec 6 00:00:01 MET 2013
Expiration date: Thu Dec 31 00:00:01 MET 2037
...
For more information on the samlicm command, refer to IBM Tivoli System
Automation for Multiplatforms Reference Guide.
Restrictions
If you edit the start, stop, and monitor scripts used in the SAP HA policy feature, no
support is provided for the modified scripts. The scripts will still be used to automate
your SAP installation, but you will find the message "Modified script not supported"
in the Syslog for each modified script.
LINUX
Replace <your platform> with the appropriate directory name
#----------------------------------------------------------------------# SAP HA connector
#-----------------------------------------------------------------------
- 30 -
Please also refer to SAP Note 1693245 - "SAP HA Script Connector Library" for
details about the latest patch level for the SAP HA Script Connector Library.
Use the wizard to provide the policy parameters: Using the wizard to
configure and activate the SAP HA solution on page 66
- 31 -
ASCS HA policy
Figure 10 on page 39 gives an overview of all resources that can be part of a ABAP
SCS HA policy.
The ASCS HA policy consists of equivalencies, resource groups, floating and fixed
resources, that are connected to each other with various relationships.
Table 4 on page 33 gives an overview of all resources.
See Table 5 on page 35 for a description of the tags used for the resource names as
well as examples.
- 32 -
Name
ABAP Network
Equivalency
Network Interface
Network Interface
ERS Network
Equivalency
Network Interface
Network Interface
SAPRouter
Network
Equivalency
Network Interface
Network Interface
Web Dispatcher
Network
Equivalency
Network Interface
Network Interface
ABAP SAP Central
Services top-level
group
ABAP SAP
Instance Agent
group
ASCS Service
IP
Instance Agent
ABAP SAP
Central Services
group
Enqueue Server
Message Server
Enqueue
Replication Server
top-level group
ERS Instance
Agent group
Enqueue
Replication
Server ServiceIP
Instance Agent
Resource
Type
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_NETIF
Equivalency
<INTERFACENAME>:<NODENAME_1>
<INTERFACENAME>:<NODENAME_2>
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_NETIF
<INTERFACENAME>:<NODENAME_1>
<INTERFACENAME>:<NODENAME_2>
<ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_NETIF
<INTERFACENAME>:<NODENAME_1>
<INTERFACENAME>:<NODENAME_2>
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_NETI
F
Fixed
Fixed
Equivalency
Fixed
Fixed
Equivalency
Fixed
Fixed
Equivalency
<INTERFACENAME>:<NODENAME_2>
Fixed
Fixed
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>
Group
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_SRV
Group
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_ip
Floating
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_sapstartsrv
Floating
<INTERFACENAME>:<NODENAME_1>
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_ASCS
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_en
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_ms
Group
Floating
Floating
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>
Group
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_SRV
Group
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_ip
Floating
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_sapstartsrv
Floating
Enqueue
Replication Server <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_ERS
group
- 33 -
Group
Name
Enqueue
Replication
Server
Primary
Application Server
top-level group
Primary
Application
Server Instance
Agent group
Instance Agent
Primary
Application
Server group
Primary
Application
Server
Additional
Application Server
top-level group
Additional
Application
Server Instance
Agent group
Instance Agent
Additional
Application
Server group
Additional
Application
Server
SAProuter group
SAProuter
SAProuter Service
IP
SAP WEB
Dispatcher toplevel group
SAP WEB
Dispatcher
Instance Agent
group
SAP Web
Dispatcher
Service IP
Instance Agent
Resource
Type
Floating
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMAR
Y>
Group
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMAR
Y>_SRV
Group
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMAR
Y>_sapstartsrv
Fixed
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMAR
Y>_AS
Group
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMAR
Y>_as
Fixed
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITI
ONAL>
Group
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITI
ONAL>_SRV
Group
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITI
ONAL>_sapstartsrv
Fixed
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITI
ONAL>_AS
Group
<A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITI
ONAL>_as
Fixed
<ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_saprouter
Group
Floating
<ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_ip
Floating
<ROUT_PREFIX>_<SAPSID>_SYS_ROUTER
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>
Group
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_SRV
Group
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_ip
Floating
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_saps
tartsrv
Floating
- 34 -
Name
SAP WEB
Dispatcher group
SAP WEB
Dispatcher
Host Agent Group
Host Agent
Resource
Type
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_WD
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_sapw
ebdisp
Group
Floating
SAP_HOST_AGENT_<NODENAME>
Group
SAP_HOST_AGENT_<NODENAME>_ha
Fixed
Tag
<A_PREFIX>
<ROUT_PREFIX>
<WD_PREFIX>
<SAPSID>
<SAPWEBDISP_SID>
<INTERFACENAME>
<NODENAME_PRIMARY>
<NODENAME_ADDITIONAL>
<NODENAME_1>
<NODENAME_2>
<INSTANCE_NAME>
<INSTANCE_NAME_ERS>
<INSTANCE_NAME_WD>
Description
Prefix for resources, has to be specified
in policy. Use a meaningful value to
easily identify resources later.
Example
LOP
eth0
ABAP,
SAPROUTER
sapnode01
sapnode01
DVEBMGS01
ERS10
WD00
ServiceIP is started first, followed by Instance Agent and the ABAP enqueue
replication server.
Interactions between Enqueue Server (ES) and Enqueue Replication Server
(ERS)
A set of six relationships between the Enqueue and Message Servers and the
Enqueue Replication Server provide the most important rules for the high availability
of the SAP Central Services. Figure 9 on page 36 shows an overview of these
relationships which will be referred by their numbers as shown in the picture.
Figure 9: Relationships between the Enqueue and Message Servers and the
Enqueue Replication Server
A set of example scenarios best explain the functions of these relationships. Please
refer to the IBM Tivoli System Automation for Multiplatforms Administrator's and
User's Guide for a detailed explanation of relationships and their properties.
Be aware that ES and MS will always start collocated on the same node because of
their common group constraint.
Initial Start (All nodes are available)
ERS will start first (because of [1] and [7]), followed by ES and MS in succession.
Since ES was not online before the initial start, ES/MS will start on another node
than ERS because of [2], relationship [3] and [5] are not applicable in this situation.
So the shadow enqueue table is maintained by ERS on another node than then the
one on which ES is running.
Initial Start (Only one node is available in a two-node cluster)
Because of [2] and [5] ES/MS and ERS cannot be started on the same node. The
competitive situation is resolved by the priorites that are assigned to the groups of
ES/MS and ERS. The group holding ES and MS has a higher priority than the ERS
group, thus it will be started on the sole node (the IfPossibe condition relaxes
relationship [1]). Thus the SAP Central Services can be made available under the
adverse conditions.
- 36 -
Failure of ES
When the Enqueue Server fails, it will bring down all members of its group too
because ES is a mandatory member of the group. System Automation for
Multiplatforms will recover ES on the node where ERS is running because of [3]. So
ES can rebuild its enqueue table from the shadow that was maintained by ERS.
Relationship [5] does not apply to this situation nor does relationship [2] since ES
was Online before. MS (and the other group members too) will follow ES to the node
where it has been restarted.
There is also an optional restart feature for the Enqueue Server in the SAP profile
which is able to recover a failed ES on the same node. This restart feature must be
disabled (as advised by Required adaptions of SAP profiles on page 24), otherwise
ES would not start on the node where ERS runs, hence the rebuild of the enqueue
table would not be possible.
Failure of MS
While in former SAP releases System Automation fro Multiplatforms could attempt a
restart in-place on the same node for a failed Message Server, this is now not
working anymore when done by System Automation. The relationship [6] forces the
restart of MS on the node where ERS runs, thereby pulling all other group members
(including ES) to move to the ERS node too.
The restart feature for the Message Server in the SAP profile should be enabled to
recover a failed MS on the same node (as advised by Required adaptions of SAP
profiles on page 24). The described recovery action by System Automation for
Multiplatforms will be executed in case the SAP restart feature was not able to restart
MS on its former node.
ERS stop/relocation after ES or MS failure recovery
As described in the previous paragraphs, a failed ES will be restarted on the node
where ERS is running. After ES has recovered its enqueue table from the shadow
table, ERS will terminate itself and be restarted by System Automation for
Multiplatforms in succession. The restart of ERS will be anticollocated on another
node because of [5], but [4] will only allow a node where the appropriate ES
constituent is not Failed Offline, so ES would be startable on that node. All other
relationships do not apply here.
There is also an optional restart feature for the Enqueue Replication Server in the
SAP profile which is able to recover a failed ERS on the same node. This restart
feature must be disabled (as advised by Required adaptions of SAP profiles on
page 24), otherwise ERS would not start another node away from EN.
ERS failure
Should ERS fail for any reason in an otherwise up and running SAP system, it will
be restarted anticollocated to the ES node because of [5], but [4] will only allow a
node where the appropriate ES constituent is not Failed Offline. All other
relationships do not apply here.
As already mentioned before there is also an optional restart feature for the Enqueue
Replication Server in the SAP profile which must be disabled (as advised by
Required adaptions of SAP profiles on page 24).
- 37 -
- 38 -
The Java SCS HA policy consists of equivalencies, resource groups, floating and
fixed resources, that are connected to each other with various relationships. Table 6
on page 40 provides an overview of all resources.
See Table 7 on page 42 for a description of the tags used for the resource names as
well as examples.
- 39 -
Name
Java Network
Equivalency
Network Interface
Network Interface
ERS Network
Equivalency
Network Interface
Network Interface
SAPRouter
Network
Equivalency
Network Interface
Network Interface
Web Dispatcher
Network
Equivalency
Network Interface
Network Interface
Java SAP Central
Services top-level
group
Java SAP Instance
Agent group
ASCS Service
IP
Instance Agent
Java SAP Central
Services group
Enqueue Server
Message Server
SAP Gateway
Enqueue
Replication Server
top-level group
ERS Instance
Agent group
Enqueue
Replication
Server ServiceIP
Instance Agent
Resource
Type
Equivalency
Fixed
Fixed
Equivalency
Fixed
Fixed
Equivalency
Fixed
Fixed
Equivalency
<INTERFACENAME>:<NODENAME_2>
Fixed
Fixed
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_SRV
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_ip
Floating
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_sapstartsrv
Floating
<INTERFACENAME>:<NODENAME_1>
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_SCS
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_en
Floating
Floating
Floating
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_ms
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_gw
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_SRV
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_ip
Floating
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_sapstartsrv
Floating
Enqueue
Replication Server <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_ERS
group
- 40 -
Group
Name
Enqueue
Replication
Server
Primary
Application Server
top-level group
Primary
Application
Server Instance
Agent group
Instance Agent
Primary
Application
Server group
Primary
Application
Server
Additional
Application Server
top-level group
Additional
Application
Server Instance
Agent group
Instance Agent
Additional
Application
Server group
Additional
Application
Server
SAProuter group
SAProuter
SAProuter Service
IP
SAP WEB
Dispatcher toplevel group
SAP WEB
Dispatcher
Instance Agent
group
SAP Web
Dispatcher
Service IP
Instance Agent
Resource
Type
Floating
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMA
RY>
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMA
RY>_SRV
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMA
RY>_sapstartsrv
Fixed
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMA
RY>_AS
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMA
RY>_as
Fixed
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDIT
IONAL>
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDIT
IONAL>_SRV
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDIT
IONAL>_sapstartsrv
Fixed
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDIT
IONAL>_AS
Group
<J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDIT
IONAL>_as
Fixed
<ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_saprouter
Group
Floating
<ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_ip
Floating
<ROUT_PREFIX>_<SAPSID>_SYS_ROUTER
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>
Group
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_SRV
Group
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_ip
Floating
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_sap
startsrv
Floating
- 41 -
Name
SAP WEB
Dispatcher group
SAP WEB
Dispatcher
Host Agent Group
Host Agent
Resource
Type
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_WD
Group
<WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_sap
webdisp
Floating
SAP_HOST_AGENT_<NODENAME>
Group
SAP_HOST_AGENT_<NODENAME>_ha
Fixed
The namings of the SAProuter and the SAP WEB dispatcher are the same for the
ABAP and the JAVA policy, refer to Table 4 on page 33.
Table 7: Description and examples of placeholders for JAVA resource names
Tag
<J_PREFIX>
<ROUT_PREFIX>
<WD_PREFIX>
<SAPSID>
<SAPWEBDISP_SID>
<INTERFACENAME>
<NODENAME_PRIMARY>
<NODENAME_ADDITIONAL>
<NODENAME_1>
<NODENAME_2>
<INSTANCE_NAME>
<INSTANCE_NAME_ERS>
<INSTANCE_NAME_WD>
Description
Prefix for resources, has to be specified
in policy. Use a meaningful value to
easily identify resources later.
SAP System SID
Example
JAVA_XI
LOP
- 42 -
SAProuter
Service IP address
Both are tied together by StartAfter and StopAfter relationships If you start the
SAProuter group, the IP resource is started first, followed by the SAProuter resource
itsself. All resoures are contained in a collocated group, so they will always be
started on the same node.
- 43 -
Service IP address
All are tied together by StartAfter and StopAfter relationships If you start the SAP
Web Dispatcher group, the IP resource is started first, followed by the Instance Agent
resource and the Web Dispatcher resource itsself. All resoures are contained in a
collocated group, so they will always be started on the same node.
The Host Agent groups
A SAP Host Agent is running on each cluster node that is able to host SAP servers
and instances. With System Automation for Multiplatforms each of these Host
Agents is modelled as a fixed resources in its own resource group. No dependencies
exist to other SAP servers and instances.
Policy parameters
The following paragraphs list all parameters that have to be specified for the different
policy options. A HTML file containing all parameter descriptions and all currently
defined values is generated each time the wizard is started and finished using the 0
selection option. For more information, refer to Terminating the wizard on page
nnn.
SAP ABAP Central Services (ASCS) -Enqueue Replication Server (ERS)
HA policy (ABAP)
Table 8: ABAP policy parameters
#
Parameter description
Value type
String
- 44 -
One of the
following values:
IPv4
IPv6
Value
Parameter description
Value type
String
Minimum number
of characters: 3,
maximum
number of
characters: 3
(plus additional
value checking)
Value
String (plus
additional value
checking)
String
Enter the nodes where you want to automate your SAP Central
Services Instance for ABAP (ASCS).
List of values,
value type for
each value:
Hostname or IP
version 4
address (plus
additional value
checking)
String
Minimum number
of characters: 6,
maximum
This instance name is used for the instance directory that contains number of
all necessary files for the ASCS instance. A sample instance name characters: 6
is 'ASCS00'.
Note: Value harvesting is provided for this parameter.
Specify the virtual hostname for the Central Services Instance for
ABAP (ASCS).
Note: Value harvesting is provided for this parameter.
This hostname will be used as a virtual hostname for the Central
Services Instance for ABAP (ASCS). Enter the same virtual
hostname that was used for 'sapinst SAPINST_USE_HOSTNAME=virt_hostname-' during the ASCS installation.
- 45 -
Hostname
SAP_ABAP
Parameter description
Value type
IP version 4
address
Value
IP version 6
address
IP version 4
address
Numeric
Minimum value:
0, maximum
value: 128
14
String
Minimum number
of characters: 5,
This instance name is used for the instance directory that contains maximum
all necessary files for the ABAP ERS instance. A sample instance number of
name is 'ERS12'.
characters: 5
(plus additional
value checking)
- 46 -
255.255.255.0
Parameter description
Value type
15
String
Value
IP version 4
address
IP version 6
address
IP version 4
address
Numeric
Minimum value:
0, maximum
value: 128
- 47 -
255.255.255.0
Parameter description
Value type
21
{yes|no}
Value
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
the ABAP application servers.
21.1 Optional; a value for this parameter is only required if parameter
#21 has the value "yes".
Enter the nodes where you want to automate the application
servers.
Note: Value harvesting is provided for this parameter.
List of values,
value type for
each value:
Hostname or IP
version 4
address
List of values,
value type for
each value:
String (plus
additional value
checking)
In this policy, the instance names are used to identify the instance
directory that contains all necessary files for the application server.
The naming syntax is DVEBMGS-InstanceID- or D-InstanceID-.
Use the same order as for the nodes in one of the previous
questions, i.e. if you specified node01 first, then you now have to
specify the instance directory for your application server on
node01 first.
This parameter must have the same number of values as the
following parameters:
- Parameter # 21, nested parameter 1
21.3 Optional; a value for this parameter is only required if parameter
#21 has the value "yes".
Enter the start timeout value for your ABAP application servers.
The start timeout attribute determines the maximum run time in
seconds of the StartCommand. If the StartCommand does not
return within the timeout period, System Automation for
Multiplatforms kills the StartCommand with the SIGKILL command
and logs a message to the system log of the node. The default
value for the ABAP application servers is 300.
- 48 -
Numeric
300
Parameter description
Value type
Value
Numeric
300
Enter the stop timeout value for your ABAP application servers.
With the stop timeout attribute you specify the amount of time in
seconds the stop command for your application servers allowed to
run before it is killed by Tivoli System Automation. The default
value for the ABAP application servers is 300 seconds.
22
{yes|no}
List of values,
value type for
each value:
Hostname
{yes|no}
SAP Host Agent can be used for monitoring and control of SAP
instances and non-SAP instances, operating systems, and
databases.
23.1
List of values,
value type for
each value:
Enter the nodes where you want to automate the SAP Host Agent.
Note: Value harvesting is provided for this parameter.
Hostname or IP
version 4
address
- 49 -
{yes|no}
#
24.1
Parameter description
Value type
Value
String
SAP_ROUTER
List of values,
value type for
each value:
Enter the nodes where you want to automate the SAP router.
Hostname or IP
version 4
address (plus
additional value
checking)
IP version 4
address
24.3
IP version 6
address
- 50 -
IP version 4
address
255.255.255.0
Parameter description
Value type
24.6 This parameter will be ignored unless all following conditions are
fulfilled:
Value
Numeric
Minimum value:
0, maximum
value: 128
String (plus
additional value
checking)
Enter the network interface for the SAP router IP address. The
following network interfaces are available on your local system:
(remaining part of description is harvested from running system)
The available network interface specifies to which network
interfaces the SAP router virtual IP address can be bound, for AIX
an example is "en0", for Linux, an example is "eth0". The same
network interface name needs to be available on all nodes where
the SAP router will be automated.
24.8
String
{yes|no}
String
Enter the desired prefix for the SAP Web Dispatcher resources.
You are allowed to use the same prefix as for other resources, like
JAVA or ABAP.
25.2
- 51 -
List of values,
value type for
each value:
Hostname or IP
version 4
address (plus
additional value
checking)
SAP_WDISP
#
25.3
Parameter description
Value type
String (plus
additional value
checking)
Specify the SAP system ID (SAPSID) for the SAP Web dispatcher.
The SAP system ID (SAPSID) for the SAP Web dispatcher is
required to identify the SAP Web dispatcher correctly.
25.4
String (plus
additional value
checking)
String
Hostname
- 52 -
IP version 4
address
Value
#
25.8
Parameter description
Value type
IP version 6
address
Value
IP version 4
address
Numeric
Minimum value:
0, maximum
value: 128
- 53 -
String (plus
additional value
checking)
255.255.255.0
Parameter description
Value type
26
{yes|no}
Value
String
Parameter description
Value type
String
IPv4
IPv6
String
Minimum number
of characters: 3,
maximum
number of
characters: 3
(plus additional
value checking)
One of the
following values:
- 54 -
String (plus
additional value
checking)
Value
Parameter description
Value type
Value
String
SAP_JAVA
Enter the nodes where you want to automate your SAP Central
Services Instance for JAVA (SCS).
List of values,
value type for
each value:
String
Minimum number
of characters: 5,
maximum
This instance name is used for the instance directory that contains number of
all necessary files for the SCS instance. A sample instance name characters: 5
is 'SCS01'.
Note: Value harvesting is provided for this parameter.
Specify the virtual hostname for the Central Services Instance for Hostname
JAVA (SCS). Enter the same virtual hostname that was used for
'sapinst SAPINST_USE_HOSTNAME=-virt_hostname-' during the
SAP installation.
Note: Value harvesting is provided for this parameter.
This hostname will be used as a virtual hostname for the Central
Services Instance for JAVA (SCS).
IP version 4
address
- 55 -
IP version 6
address
Parameter description
Value type
Value
11
IP version 4
address
255.255.255.0
Numeric
Minimum value:
0, maximum
value: 128
14
String
Minimum number
of characters: 5,
This instance name is used for the instance directory that contains maximum
all necessary files for the JAVA ERS instance. A sample instance
number of
name is 'ERS11'.
characters: 5
(plus additional
value checking)
15
String
- 56 -
IP version 4
address
Parameter description
Value type
17
IP version 6
address
Value
IP version 4
address
Numeric
Minimum value:
0, maximum
value: 128
21
- 57 -
{yes|no}
255.255.255.0
#
21.1
Parameter description
Value type
List of values,
value type for
each value:
Value
Hostname or IP
version 4 address
List of values,
value type for
each value:
String (plus
additional value
checking)
In this policy, the instance names are used to identify the instance
directory that contains all necessary files for the application server.
The naming syntax is J-InstanceID- or JC-InstanceID-. Use the
same order as for the nodes in one of the previous questions, i.e.
if you specified node01 first, then you now have to specify the
instance directory for your application server on node01 first.
This parameter must have the same number of values as the
following parameters:
- Parameter # 21, nested parameter 1
21.3
Numeric
500
Numeric
360
Enter the start timeout value for your JAVA application servers.
The start timeout attribute determines the maximum run time in
seconds of the StartCommand. If the StartCommand does not
return within the timeout period, System Automation for
Multiplatforms kills the StartCommand with the SIGKILL command
and logs a message to the system log of the node. The default
value for the JAVA application servers is 500.
21.4
- 58 -
Parameter description
Value type
22
{yes|no}
Value
List of values,
value type for
each value:
Hostname
{yes|no}
SAP Host Agent can be used for monitoring and control of SAP
instances and non-SAP instances, operating systems, and
databases.
23.1
List of values,
value type for
each value:
Enter the nodes where you want to automate the SAP Host Agent.
Note: Value harvesting is provided for this parameter.
Hostname or IP
version 4 address
{yes|no}
- 59 -
String
SAP_ROUTER
#
24.2
Parameter description
Value type
List of values,
value type for
each value:
Value
Enter the nodes where you want to automate the SAP router.
Note: Value harvesting is provided for this parameter.
For each of the nodes specified, SA MP will create SAP router
resources.
24.3
Hostname or IP
version 4 address
(plus additional
value checking)
IP version 4
address
IP version 6
address
IP version 4
address
Numeric
Minimum value:
0, maximum
value: 128
- 60 -
255.255.255.0
#
24.7
Parameter description
Value type
String (plus
additional value
checking)
Value
Enter the network interface for the SAP router IP address. The
following network interfaces are available on your local system:
(remaining part of description is harvested from running system)
The available network interface specifies to which network
interfaces the SAP router virtual IP address can be bound, for AIX
an example is "en0", for Linux, an example is "eth0". The same
network interface name needs to be available on all nodes where
the SAP router will be automated.
24.8
String
{yes|no}
String
Enter the desired prefix for the SAP Web Dispatcher resources.
You are allowed to use the same prefix as for other resources, like
JAVA or ABAP.
25.2
List of values,
value type for
each value:
Hostname or IP
version 4 address
(plus additional
value checking)
- 61 -
String (plus
additional value
checking)
SAP_WDISP
#
25.4
Parameter description
Value type
String (plus
additional value
checking)
String
Hostname
IP version 4
address
- 62 -
IP version 6
address
Value
#
25.9
Parameter description
Value type
Value
IP version 4
address
255.255.255.0
Numeric
Minimum value:
0, maximum
value: 128
String (plus
additional value
checking)
{yes|no}
- 63 -
String
With System Automation for Multiplatforms 3.next all existing SAP HA 3.2style policies can still be used and activated as long as they are in the form
of a complete XML policy file, that was created with System Automation
for Multiplatforms 3.2 from a former SAP HA policy template of the same
version. These existing SAP HA policies are usually stored in the System
Automation for Multiplatforms policy pool and are not erased or overwritten
when a new System Automation for Multiplatforms release is installed. The
Start/Stop/Monitor scripts used by those 3.2-style SAP HA policies are still
delivered with System Automation for Multiplatforms Release 3.next, so they
do not have to be saved before migrating.
Migration steps
Overview
Migration considerations
Migrating the SAP HA policy
The SAP HA automation policy shipped with System Automation for Multiplatforms
3.next incorporates major changes in the way the components of a SAP solution are
controlled and managed. The new SAP HA policy makes use of new interfaces and
conforms to advisories made by SAP.
Because of these changes, a SAP HA policy generated with System Automation for
Multiplatforms 3.next will show major differences when compared to a 3.2-style
SAP HA policy. Thus the migration process is essentially a way of a smoothly
replacing the former policy with a new policy that conforms to the changed methods
of controlling a SAP solution.
These are the special considerations that must be observed when migrating an SAP
HA cluster and policy from the previous version of System Automation for
Multiplatforms Release 3.2.
The former SAP HA policy template files and their related snippets are
replaced by new versions when System Automation for Multiplatforms
Release 3.next is installed. The new SAP HA policy wizard contained in SA
MP 3.next will not work with the former policy templates. So you cannot use
the old template files to generate or change SAP HA policies in the 3.2
style, even if you saved these template files to another location before
installing System Automation for Multiplatforms 3.next.
Only SAP NetWeaver versions 7.0 or higher with kernel versions 7.20 or
higher are supported by the SAP HA solution provided by System
Automation for Multiplattforms 3.next.
SAP solutions that are based on a SAP Central Instance (CI) implementation
are no longer supported by the SAP HA solution. You need to have a SAP
Central Services (CS) setup.
These are the steps to follow when migrating your SAP HA cluster to System
Automation for Multiplatforms 3.next:
- 64 -
Activate the new SAP HA policy as described in chapter 22 (???) Using the
wizard to configure and activate the policy
Depending on the SAP HA setup option that you choose, specify one of the
following fully qualified XML template file names:
Table 10: Location for the SAP HA XML template files
SAP HA setup
ABAP
Java
/usr/sbin/rsct/sapolicies/sap/sap_ABAP_v41.tmpl.xml
/usr/sbin/rsct/sapolicies/sap/sap_Java_v41.tmpl.xml
You must configure a policy pool before running the wizard. The wizard will then
store all modifications to the policy pool. If you set your policy pool to
/etc/myPolicyPool, a wizard run using
sampolicy -w /usr/sbin/rsct/sapolicies/sap/sap_ABAP_v41.tmpl.xml
The next time you invoke the wizard, use the file stored in the policy pool. With the
- 66 -
example above, invoking the wizard for the second time would look like this:
sampolicy -w /etc/myPolicyPool/sap_ABAP_v41.tmpl.xml
For a detailed description of the sampolicy wizard, refer to chapter 22 (???), Using
the wizard to configure and activate the policy, on page nnn.
Enter the following command to display your SAP ABAP or Java HA policy:
lssam -noequ
Output:
root@node1 ~# lssam -noequ
Offline IBM.ResourceGroup:SAP_ABAP_AX6_ASCS00 Nominal=Offline
|- Offline IBM.ResourceGroup:SAP_ABAP_AX6_ASCS00_ASCS Nominal=Offline
|- Offline IBM.Application:SAP_ABAP_AX6_ASCS00_en
|- Offline IBM.Application:SAP_ABAP_AX6_ASCS00_en:node1
'- Offline IBM.Application:SAP_ABAP_AX6_ASCS00_en:node2
'- Offline IBM.Application:SAP_ABAP_AX6_ASCS00_ms
|- Offline IBM.Application:SAP_ABAP_AX6_ASCS00_ms:node1
'- Offline IBM.Application:SAP_ABAP_AX6_ASCS00_ms:node2
'- Offline IBM.ResourceGroup:SAP_ABAP_AX6_ASCS00_SRV Nominal=Offline
|- Offline IBM.Application:SAP_ABAP_AX6_ASCS00_sapstartsrv
|- Offline IBM.Application:SAP_ABAP_AX6_ASCS00_sapstartsrv:node1
'- Offline IBM.Application:SAP_ABAP_AX6_ASCS00_sapstartsrv:node2
'- Offline IBM.ServiceIP:SAP_ABAP_AX6_ASCS00_ip IP=9.152.135.234
|- Offline IBM.ServiceIP:SAP_ABAP_AX6_ASCS00_ip:node1
'- Offline IBM.ServiceIP:SAP_ABAP_AX6_ASCS00_ip:node2
Offline IBM.ResourceGroup:SAP_ABAP_AX6_D03_node2 Nominal=Offline
|- Offline IBM.ResourceGroup:SAP_ABAP_AX6_D03_node2_AS Nominal=Offline
'- Offline IBM.Application:SAP_ABAP_AX6_D03_node2_as:node2
'- Offline IBM.ResourceGroup:SAP_ABAP_AX6_D03_node2_SRV Nominal=Offline
'- Offline IBM.Application:SAP_ABAP_AX6_D03_node2_sapstartsrv:node2
Offline IBM.ResourceGroup:SAP_ABAP_AX6_DVEBMGS02_node1 Nominal=Offline
|- Offline IBM.ResourceGroup:SAP_ABAP_AX6_DVEBMGS02_node1_AS Nominal=Offline
'- Offline IBM.Application:SAP_ABAP_AX6_DVEBMGS02_node1_as:node1
'- Offline IBM.ResourceGroup:SAP_ABAP_AX6_DVEBMGS02_node1_SRV Nominal=Offline
'- Offline IBM.Application:SAP_ABAP_AX6_DVEBMGS02_node1_sapstartsrv:node1
Offline IBM.ResourceGroup:SAP_ABAP_AX6_ERS10 Nominal=Offline
|- Offline IBM.ResourceGroup:SAP_ABAP_AX6_ERS10_AERS Nominal=Offline
'- Offline IBM.Application:SAP_ABAP_AX6_ERS10_ers
|- Offline IBM.Application:SAP_ABAP_AX6_ERS10_ers:node1
'- Offline IBM.Application:SAP_ABAP_AX6_ERS10_ers:node2
'- Offline IBM.ResourceGroup:SAP_ABAP_AX6_ERS10_SRV Nominal=Offline
|- Offline IBM.Application:SAP_ABAP_AX6_ERS10_sapstartsrv
|- Offline IBM.Application:SAP_ABAP_AX6_ERS10_sapstartsrv:node1
'- Offline IBM.Application:SAP_ABAP_AX6_ERS10_sapstartsrv:node2
'- Offline IBM.ServiceIP:SAP_ABAP_AX6_ERS10_ip IP=9.152.135.235
|- Offline IBM.ServiceIP:SAP_ABAP_AX6_ERS10_ip:node1
'- Offline IBM.ServiceIP:SAP_ABAP_AX6_ERS10_ip:node2
Offline IBM.ResourceGroup:SAP_HOST_AGENT_node1 Nominal=Offline
'- Offline IBM.Application:SAP_HOST_AGENT_node1_ha:node1
Offline IBM.ResourceGroup:SAP_HOST_AGENT_node2 Nominal=Offline
- 67 -
Failover scenarios
The scenarios cover both planned outages (normal operation, maintenance) and
unplanned outages (failures). Each scenario should be verified for proper operation.
Test setup
The following scenarios expect the topology to be a cluster with two nodes (node1,
node2). We have "floating" groups for the SAProuter, Web Dispatcher and the
Enqueue and Enqueue Replication servers, and "fixed" groups for each application
server on each node.
You can use the lssam command to monitor the reaction of the system to the actions
taken.
Scenarios
Table 11 on page 69 and Table 12 on page 70 list the important scenarios for planned
and unplanned outages. The preconditions for executing the scenarios are listed
above the "Action", "Command" and "Expected result" columns. Each scenario is
divided into steps, where each steps precondition is the successful completion of the
preceding action. The commands to be executed are listed in the "Command"
column. If you have different namings, you have to adapt the commands accordingly.
The last column of the tables lists the expected result.
See Table 4 on page 33, Table 6 on page 40, and Table 10 on page 66 for a detailed
explanation of the <placeholders> for the resource names within the command
column.
For the command examples in Table 11, replace <x_PREFIX> with the ABAP or
Java prefix depending on whether you have ABAB or Java setup. Also replace
DVEBMSG and D for ABAP application servers with J for Java application
servers.
- 68 -
Scenario
Normal
operation
Maintena
nce
Action
Command
Precondition: All groups offline
Start an SAP
system
chrg -o online -s
"Name like <x_PREFIX>_%"
(Re-)Start SAP
system AX6
Expected result
ROUTER, WEBDISP,
(A)SCS and
DVEBMGS/J groups
start on node1.
ERS and D/J groups start
on node2.
(A)SCS, ERS,
DVEBMGS/J and D/J
groups stop.
(A)SCS, and ABAP
DVEBMGS/J groups
start on node1.
ERS and D/J groups start
on node2.
All groups stop.
chrg -o offline -s
Stop an SAP
"Name like <x_PREFIX>_%"
system
Precondition:
ROUTER, WEBDISP, (A)SCS, and DVEBMGS/J groups are online on
node1
ERS and D/J groups are online on node2
ROUTER, WEBDISP,
(A)SCS, and
DVEBMGS/J groups
stop.
DVEBMGS/J groups
Move all
have status Failed
resources away
samctrl -u a node1
Offline.
from node1 in
ROUTER and WEBDISP
order to apply
group start on node2.
operating system
(A)SCS group starts on
or hardware
node2.
maintenance.
ERS terminates.
ERS groups sacrificed.
Apply maintenance, reboot, etc.
DVEBMGS/J groups and
samctrl -u d node1
ERS groups start on node1.
rgreq -o stop
Stop and restart
ERS groups stop.
<x_PREFIX>_<SAPSID>_
Enqueue
<INSTANCE_NAME_ERS>
Replication
Server in order to
- 69 -
Scenario
Action
Command
apply SAP
maintenance
(code or profile
changes).
Move Enqueue
Server in order to
apply SAP
maintenance
(code or profile
changes).
Stop and restart
Primary
Application
Server in order to
apply SAP
maintenance
(code or profile
changes).
rgreq -o cancel
<x_PREFIX>_<SAPSID>_
<INSTANCE_NAME_ERS>
rgreq -o move
<x_PREFIX>_<SAPSID>_
<INSTANCE_NAME_(A)SCS>
rgreq -o stop
<x_PREFIX>_<SAPSID>_
<INSTANCE_NAME>_
<NODENAME_PRIMARY>
rgreq -o cancel
<x_PREFIX>_<SAPSID>_
<INSTANCE_NAME>_
<NODENAME_PRIMARY>
Expected result
ERS groups start on node1.
DVEBMGS/J groups
restart on node1.
Scenario
Simulation action/command
Expected result
Precondition:
ROUTER, WEBDISP, (A)SCS and DVEBMGS/J groups online on node1
ERS and D groups online on node2
To simulate a software failure create a script using the name "killscript". Add the following
content:
kill $1 `ps -ef | grep $2 | grep -v grep | awk {print $2}`
Failure of the
(A)SCS Enqueue
Server
node1:
Failure of the
Enqueue
Replication Server
Failure of the
Message Server
node1:
killscript -9
en.sap<SAPSID>_<INSTANCE_NAME_(A)SC
S>
killscript -9
er.sap<SAPSID>_<INSTANCE_NAME_ERS>
node2:
killscript -9
ms.sap<SAPSID>_<INSTANCE_NAME_(A)SC
S>
- 70 -
Scenario
Failure of an
(A)SCS application
server
Simulation action/command
node1:
ASCS:
killscript -9
dw.sap<SAPSID>_DVEBMGS<ID>
Expected result
DVEBMGS/J application
servers restart on node1.
SCS:
killscript -2 jc.sap<SAPSID>_J<ID>
node2:
reboot
#
1.1
Tasks
Configure automounter for NFS
SAP data directory.
Reference
NFS HA installation setup on page 15
1.2
1.3
2.1
2.2
2.3
2.4
2.5
2.6
- 71 -
Done
#
2.7
Tasks
Install SAP Web Dispatcher
(optional)
2.8
2.9
2.10
2.11
3.1
3.2
3.3
3.4
3.5
3.6
3.7
4.1
4.2
Reference
Initial installation on primary node on
page 23 in Installing a new ASCS or SCS
HA SAP system on page 21
4.3
4.4
4.5
- 72 -
Done