Professional Documents
Culture Documents
Implementing High Availability For Sap Netweaver 7.1 Technology On System Z
Implementing High Availability For Sap Netweaver 7.1 Technology On System Z
Applies to:
SAP NetWeaver 7.1, IBM Tivoli System Automation for z/OS 3.2, IBM Tivoli System Automation for
Multiplatforms 3.1, System Automation „best practice policy‟ for SAP
For more information, visit the Landscape Design and Architecture homepage.
Summary
The IBM System Automation family of products delivers ‘best practice policies’ for SAP that implements a
high availability solution for SAP NetWeaver 7.0. This paper describes enhancements and adaptations to
these policies to cover SAP NetWeaver 7.1.
Author Bio
Harald Duvenbeck
Harald Duvenbeck is a software developer at IBM Deutschland Research & Development
GmbH, Boeblingen. He holds a master‟s degree in mathematics from the University of
Bonn, Germany, and has worked for IBM since 1990. In 1994 he joined the IBM/SAP
platform team that developed the SAP on System z solution. Since 2008 he has been
working in the IBM Team in the Boeblingen lab that focuses on High Availability for SAP on
IBM server platforms. He can be reached at duven@de.ibm.com .
Rainer Himmelsbach
Rainer Himmelsbach graduated with a degree in “IT & Electronics Engineering” in
Berlin in 1988. He started his career at Endress+Hausser as a software developer.
Rainer joined IBM in 1991 and worked as team lead of the CVT/SVT test team for
RMF, the MVS Resource Measurement Facility. In this role he worked closely together
with other IBM teams in Boeblingen, Poughkeepsie, Tucson and Endicott.
In 2007 he took the team lead position of the IBM COV-Team (Customer Oriented
Validation) for SAP on IBM System z. He is responsible for the certification of new z/OS and Linux for IBM
System z releases and for the validation of Business Continuity for SAP on IBM System z. He can be
reached at himmi@de.ibm.com .
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 1
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Heike Schmidt
Heike Schmidt joined IBM in 1986, starting as an application programmer for IBM. Since
1998 she has been working as an SAP Basis Specialist with IBM, running functional
tests on IBM platforms and providing first level support for SAP Basis issues within IBM
(SAP Customer Competence Center). She has been involved in several SAP projects
and benchmarks for customers. Since 2007 she belongs to the IBM System z
Technology Center for SAP applications in the Boeblingen Lab and is focused on z/OS
and Linux on System z certification for SAP applications. She can be reached at
heike_schmidt@de.ibm.com .
Volker Schölles
Volker Schölles is a software developer at IBM Deutschland Research & Development
GmbH, Boeblingen. He holds an IT degree from the University of Kaiserslautern,
Germany, and has worked for IBM since 1985. In 1995 he joined the IBM/SAP platform
team which developed the SAP on System z solution. Since 2003 he has been
responsible for the High Availability solution for SAP on System z. In addition, he is
currently working on the extension of this solution to other IBM server platforms. He
can be reached at volker_schoelles@de.ibm.com .
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 2
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Table of Contents
Installing and Customizing SAP 7.1 for High Availability .................................................................................... 4
Software Prerequisites .................................................................................................................................... 4
IBM Tivoli System Automation for z/OS ....................................................................................................................... 4
IBM Tivoli System Automation for Multiplatforms ......................................................................................................... 4
Filesystem Setup on z/OS............................................................................................................................... 5
Considerations for the Planned or Unplanned Move of the NFS Server ...................................................................... 5
Define Own, Separate zFS filesystems for SCS and ASCS Instance Directories ........................................................ 5
Description of Test Environment ..................................................................................................................... 5
Configuration of the SAP File Systems ........................................................................................................... 7
SAP Central Services Installation on z/OS ..................................................................................................... 8
Installation of Central Services and its ERS with ZSCSinst tool................................................................................... 8
Installation of Central Services and its ERS with SAP installation tool ......................................................................... 9
Installation of a Primary and One or More Additional Application Server (AS) Instances ............................ 10
SAP Primary Application Server Instance .................................................................................................................. 11
SAP Dialog Instance .................................................................................................................................................. 12
SAP Post Installation Steps for HA ............................................................................................................... 12
Update DBSL ............................................................................................................................................................. 12
Multiple-Node Setup for a Highly Available SAP Application Server .......................................................................... 12
Adaptations in SAP Profiles ....................................................................................................................................... 12
Environment Adaptations for AIX and for Linux on System z ....................................................................... 13
Adaptations for AIX .................................................................................................................................................... 13
Adaptations for Linux on System z ............................................................................................................................. 14
Customizing Tivoli System Automation for z/OS .............................................................................................. 16
SAP JAVA Gateway ...................................................................................................................................... 16
SAP JAVA Enqueue Server .......................................................................................................................... 17
SAPOSCOL .................................................................................................................................................. 17
SAP WebDispatcher 7.1 ............................................................................................................................... 18
Installation .................................................................................................................................................................. 18
Running under Automation Control ............................................................................................................................ 21
OMPROUTE Relationship Changes ............................................................................................................. 22
NFSSERV Relationship Changes ................................................................................................................. 22
Filesystem Recommendation ........................................................................................................................ 22
Customizing Tivoli System Automation for Multiplatforms ............................................................................... 24
Related Content ................................................................................................................................................ 25
Copyright........................................................................................................................................................... 26
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 3
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
The following features of SAP NetWeaver 7.1 require changes in this procedure and they are described in
more detail in the chapters below:
1. In SAP NetWeaver 7.1 the SAP Enqueue Replication Servers (ERS) for ABAP and JAVA are
installed by the SAP installer as individual SAP instances including ERS instance profiles.
2. In SAP NetWeaver 7.1 there is only one single profile per instance that contains all the information
that was spread across 2 separate profiles - the instance profile and the instance start profile - in
previous SAP releases.
3. The JAVA Central Services are installed including a standalone SAP Gateway.
4. The default SAPOSCOL installation directories have changed.
5. If the home directory of the <sapsid>adm is -NOT-shared, we recommend that you install your SAP
application servers in your HA environment using virtual hostnames.
The high availability concepts and recommendations described in this paper have been implemented and
tested in our SAP NetWeaver 7.1 High Availability test environment.
Software Prerequisites
Before you start with your SAP NetWeaver 7.1 high availability installation you should ensure that you have
installed the following required software levels:
http://www.ibm.com/servers/eserver/zseries/software/sap/downloads/
This zip file also contains an updated version of Chapter 11 of the book “Business Continuity for SAP
on IBM System z (SC33-8206-02”). Use the updated version.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 4
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
To accomplish this you configure a POSTSTART command for each file system in the SA z/OS policy for
NFS Server resource, as shown in the following example:
Define Own, Separate zFS filesystems for SCS and ASCS Instance Directories
In the case of a SAP double stack installation you must define System Automation resources for both the
JAVA central services (SCS) and the ABAP central services (ASCS) in your System Automation policy.
There is no technical reason why the SCS and the ASCS must run on the same z/OS LPAR. The SAP best
policy reflects this in the sense that there is no dependency between the resources of both central services
instances.
The enqueue server of each central services instance needs access to its instance directory which should –
for performance reasons – be owned by the LPAR on which the enqueue server is running (see: Filesystem
Recommendation).
If you define only one filesystem for both the SCS and the ASCS instance directories you might encounter a
situation where System Automation places the SCS and ASCS on different z/OS LPARs. Since only one
LPAR can have the ownership of the filesystem the other (A)SCS will encounter a performance penalty
especially during startup and shutdown, for example in a maintenance scenario with planned failover.
In order to avoid this penalty and potential restarts of application servers because of timeouts, we highly
recommend that you define separate filesystems for each SCS and ASCS instance directory. This allows for
movement of the filesystem ownership together with the (A)SCS that is using it, thus avoiding any
performance impact on one of the enqueue servers.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 5
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
The three SAP application servers – one primary and two additional application servers - were installed on
IBM System p LPARs running AIX 6.1, also distributed on two physical machines.
SAP supports the application server installation with virtual hostnames. We used p570coh1v, p570coh2v,
p570coh3v for the three AIX application servers. This was possible, because on each machine the home
directory of the ha2adm is local.
ABAP SCS dynamic VIPA ha2ascsv ABAP SCS dynamic VIPA ha2ascsv ABAP SCS dynamic VIPA ha2ascsv
Java SCS dynamic VIPA ha2scsv Java SCS dynamic VIPA ha2scsv Java SCS dynamic VIPA ha2scsv
NFS dynamic VIPA sapnfsv NFS dynamic VIPA sapnfsv NFS dynamic VIPA sapnfsv
ABAP SCS Instance HA2_ASCS20_ha2ascsv ABAP SCS Instance HA2_ASCS20_ha2ascsv ABAP SCS Instance HA2_ASCS20_ha2ascsv
Java SCS instance HA2_SCS21_ha2scsv Java SCS instance HA2_SCS21_ha2scsv Java SCS instance HA2_SCS21_ha2scsv
ERS for ASCS HA2_ERS22_ha2ascsv ERS for ASCS HA2_ERS22_ha2ascsv ERS for ASCS HA2_ERS22_ha2ascsv
ERS for SCS HA2_ERS23_ha2scsv ERS for SCS HA2_ERS23_ha2scsv ERS for SCS HA2_ERS23_ha2scsv
According to the instructions in the SAP NetWeaver 7.1 installation guide, the SAP instances for a high
availability system should be installed in the following sequence:
1. SAP Central Service instances (ASCS and/or SCS)
2. Enqueue Replication Server instances for ABAP and/or JAVA (ERS)
3. Database instance
4. Primary Application Server instance (PAS)
5. Additional Application Server instance (AAS)
The installation procedure in SAP 7.0 did not install the Enqueue Replication Server (ERS) as a separate
instance. This has changed with SAP 7.1.
The Installation guide “SAP NetWeaver 7.1 PI ABAP and Java on AIX: IBM DB2 for z/OS” recommends the
installation of a separate ERS instance on each eligible application server. In a High Availability setup under
USS with a shared filesystem this is not appropriate. It is required that you install only one ERS instance for
ABAP and one for ERS instance for JAVA under USS.
The SAP NetWeaver 7.1 installation will automatically add a JAVA Gateway when installing the JAVA SCS.
A change in the System Automation policy (see SAP JAVA Gateway) is required to make this component
highly available as well.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 6
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
SYS
* the Central Services instance directories are configured as zFS filesystems, see: Define Own, Separate
zFS filesystems for SCS and ASCS Instance Directories
The SAP global directories which are exported by the NFS server on z/OS are mounted on AIX in our
environment. We highly recommend using the automounter. See the following sample automounter
definitions:
p570coh1:/etc # cat auto_master
/sapmnt/HA2 auto.ha2.sapmnt
p570coh1:/etc # cat auto.ha2.sapmnt
global -rw,hard,intr,sec=sys sapnfsv:/HFS/sapmnt/HA2/global,text,cln_ccsid(819),srv_ccsid(1047)
profile -rw,hard,intr,sec=sys sapnfsv:/HFS/sapmnt/HA2/profile,text,cln_ccsid(819),srv_ccsid(1047)
trans -rw,hard,intr,sec=sys sapnfsv:/HFS/usr/sap/trans,text,cln_ccsid(819),srv_ccsid(1047)
exe -rw,hard,intr,sec=sys sapnfsv:/HFS/sapmnt/HA2/AIX/exe
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 7
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
In our environment the SAP Central Services have been installed with the ZSCSinst tool. We recommend
using ZSCSinst, because it is easier to handle and the installation is much faster.
In the examples for our sample SAPSID HA2 we use the following dynamic VIPA names as VIRTUALHOST:
ha2ascsv VIPA for the ABAP Central Services (ASCS) and its ERS
ha2scsv VIPA for the JAVA Central Services (SCS) and its ERS
Please note, that those dynamic VIPAs must be activated manually on the LPAR on which you plan to do the
installation, for example by using the moddvipa USS command as described in the “Business Continuity for
SAP on IBM System z” .
Example invocation of ZSCSinst for ABAP Central Services Installation (ASCS) using a parameter file:
./zscsinst ASCS /u/admin/REXX/ASCS.HA2
SYSTYPE=ASCS
VIRTUALHOST=ha2ascsv
SAPSID=HA2
MOUNTDIR=/sapmnt
KERNELCD=/common/sapdvds/SAP_Netweaver_PI_710/sapcd1/DATA_UNITS/K_710_UI_OS390_64
INSTANCENUMBER=20
MSPORT=3620
IMSPORT=3920
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 8
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Example invocation of ZSCSinst for Enqueue Replication Server for ABAP (ERS)
./zscsinst ERS /u/admin/REXX/ERSA.HA2
SYSTYPE=SCS
VIRTUALHOST=ha2scsv
SAPSID=HA2
MOUNTDIR=/sapmnt
KERNELCD=/common/sapdvds/SAP_Netweaver_PI_710/sapcd1/DATA_UNITS/K_710_UI_OS390_64
INSTANCENUMBER=21
IMSPORT=3921
Example invocation of ZSCSinst for Enqueue Replication Server for Java (ERS)
./zscsinst ERS /u/admin/REXX/ERSJ.HA2
The INSTFILE parameter contains the filename of the ASCS – or SCS instance profile for which the ERS
must be installed.
Note: To ensure proper functionality of SAP utilities like ensmon or enqt in a double-stack installation (ABAP and Java
stack) check the Java SCS profile. It must contain the parameter „enque/serverhost‟ set to the Java virtual
hostname. If the parameter is missing in the SCS Profile and you are using these utilities, they will fail because
they will use enque/serverhost from the default parameter file that is set to ABAP virtual hostname.
Installation of Central Services and its ERS with SAP installation tool
Parallel to using the ZSCSinst tool there is still the option of installing the high availability components on
z/OS Unix System Services using the SAPinst installation tool.
When calling SAPinst from the Unix System Services command line you need to specify the virtual hostname
using the option SAPINST_USE_HOSTNAME.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 9
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
In the SAPinst GUI select the menu item “High-Availability System” and choose the ABAP (ASCS) or JAVA
Central Service (SCS) of your choice.
The same command lines should be used for installing the corresponding enqueue replication server
instances.
Caution: When you use SAPinst to install the ERS it will install both ERS instances (for ABAP and JAVA) in one step. In
our case this would have the negative side-effect, that both ERS instances (for JAVA and ABAP SCS) would be
installed with the same virtual hostname – namely the virtual hostname which was specified in the SAPinst
command line. This would prevent the two ERS instances from running independently of each other. Therefore
you need to call SAPinst twice, to install each ERS Instance with its own virtual hostname.
In order to prevent SAPinst from installing the two ERS instances at once, you need to explicitly prevent the
installation of the „wrong‟ ERS as depicted in the following example screenshot.
In this example we want to install the ERS for the ABAP SCS using the SAPinst command line:
and therefore uncheck the checkbox in front of the Java SCS (SCS21):
If you install the ERS with SAPinst, you must follow the instruction of SAP Note 1045531, to make the ERS
instances startable:
https://service.sap.com/sap/support/notes/1045531
Installation of a Primary and One or More Additional Application Server (AS) Instances
Redundancy for SAP application servers is usually achieved by installing more than one application server
instance which is supported by the NetWeaver architecture. If a specific application server is not available, a
SAP user can connect to another one that is still active. Therefore, the „best practice policy‟ for SAP of
System Automation for Multiplatforms (SA MP) defines SAP application server resources as fixed resources
that are not moved to another node. From a high availability point of view, installing an application server
using the physical hostname is sufficient.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 10
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
On the other hand, the SAP installer supports installation of an application server instance with its own virtual
hostname. Exploiting this feature makes it easier to move an instance from one physical machine to another
in case this should be necessary, for example when moving to a newer and faster hardware.
In order to exploit the SA MP „best practice policy‟ for SAP and to get the flexibility provided by SAP‟s
virtualization option, we recommend installing every application server with its own virtual hostname,
provided the home directory of the <sapsid>adm is local on each machine. SA MP will define and manage
the application server as a fixed resource regardless of its hostname being a virtual or a physical one. The
rare case of moving such an AS from one physical host to a different one is NOT done using SA MP. It is
done as a manual task outside of automation after the cluster has been changed to include the new host.
Note: Make sure that System Automation under z/OS is not controlling the Java SCS during the Primary Application
Server installation because SAPinst will try to start and stop the Java SCS during the installation procedure. This
will create a conflict if the JAVA SCS is already managed – and kept highly available - by System Automation at
that time and will cause the Primary Application Server installation to fail.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 11
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Update DBSL
When you run your SAP application servers with virtual hostnames, you need a minimum DBSL level as
documented in SAP Note 1339004, “DB2-z/OS: Support of Logical Hostname in connect.ini”. Download the
required DBSL patch from SAP Services Marketplace and install it in your application servers.
The current DBSL level of your SAP kernel is reported when you run the following command as
<sapsid>adm:
disp+work –v
After you have installed the DBSL, follow the instructions in SAP Note 1339004 describing the modification in
the connection profile „connect.ini‟. The profile can be modified directly using an editor or through the SAP
transaction DBACOCKPIT from SAPGUI. Check the SAP note for the Support Package that needs to be
installed.
Note: It is essential that you have added the SAPLOCALHOST variable to the environment of your <sapsid>adm and
that its value is the name of the virtual/logical hostname. System Automation for Multiplatforms depends on it when
it runs the R3trans utility to test the application server connectivity to the z/OS database.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 12
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Use this parameter only if the replication port of the enqueue server cannot be set to the default port 5XX16
(where XX is the instance number).
a) Put
enque/con_retries = 120
enque/deque_wait_answer = TRUE
into DEFAULT.PFL (or into each AS instance profile, if you think this is more appropriate)
b) In the instance profiles for the Enqueue Replication Servers <SAPSID>_ERSxx_<virtual hostname>
comment out the line:
Autostart = 1
to
Start_Program_<xx>
Adaptations b) and c) make sure that SAP (via hostctrl or startsapsrv) is NOT trying to restart instances. We
want System Automation to control this (and having 2 'automation managers' controlling the same resources
will cause problems).
Caution: If you change any script that is delivered with the OS (like /etc/rc.nfs) or System Automation (like sapctrl_em),
the changes may and most likely will be over-written during a service update. So it is highly recommended that you
check the adapted scripts after such activities.
## if [ -s /etc/auto_master ]; then
## /usr/sbin/automount
## fi
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 13
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
2. Add a new rc.local script in the /etc directory. Adapt the virtual NFS server hostname to your
environment (our virt. NFS server hostname is sapnfsv):
$ cat rc.local
#!/bin/ksh
# this is to start autofs group after gated had time to consolidate it's routing table
VirtNFSHOST="sapnfsv"
TIMEVAR=0
MAXRETRY=20 # this lets this script try for 20 minutes
RETRY=0
SLEEPSEC=5 # this lets this script sleep for 5 seconds
RC=1
3. Add starting of rc.local to /etc/inittab. Insert the rc.local call before the rc_2 call and the following
rc_x:
Note: Starting the sapstartsrv processes in /usr/sap/sapservices will produce some NFS mount failure messages in the
/tmp/syslog.out file at system start. This is normal since, even if the z/OS NFS server host is listed in the routing
table, it may not be able to reply directly because the z/OS routing daemon also needs to update its routing table
after the AIX (gated) has started.
The init scripts for sapinit and autofs need to have dependencies set, so that they are started and stopped in
the correct order.
sapinit needs a start dependency to autofs and autofs needs a start dependency to ospfd/zebra. Therefore,
in the sapinit script under /etc/init.d at the end of the “# Required-Start” line, add the autofs:
ihlscoh1:/etc/init.d # head -n 20 sapinit
#!/bin/sh
# Copyright (c) 1995-2005 SAP AG Walldorf, Germany.
#
# /etc/init.d/sapinit
#
# chkconfig: 345 90 10
# description: Start sapstartsrv
#
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 14
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Also add in the autofs script under /etc/init.d at the end of the “# Required-Start” line the ospfd and zebra
processes:
ihlscoh1:/etc/init.d # head -n 20 autofs
#!/bin/bash
#
# rc file for automount using a Sun-style "master map".
# We first look for a local /etc/auto.master, then a YP
# map with that name
#
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 15
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
The following paragraphs focus on the changes that were introduced in the SAP configuration from SAP
NetWeaver 7.0 to 7.1 that require an adaptation of the System Automation policy for SAP:
- SAP JAVA gateway
- saposcol configuration
Further changes apply to SAP NetWeaver 7.1 but may also be used for 7.0:
- additional relationship from OMPROUTE to TCPIP
- additional NFSSERV relationships
- enhancements for the JAVA enqueue server
- movement of file system ownership with the ENQ server
- definition of separate filesystems for ABAP and JAVA SCS
Note: All automation names and sample command lines that are mentioned below contain the sample SAPSID HA1 that
is used in the “best practice policy” for SAP delivered with System Automation. You need to replace references to
this sample SAPSID with your specific SAPSID for which you are creating the System Automation policy.
There is no need to create SAPHA1GW from scratch, instead you can use the SAPHA1GW resource which is an
optional part of the ABAP central services in the “best practice policy” for SAP and copy its content into
SAPHA1JGW.
In case of a JAVA-only or an ABAP+JAVA double-stack installation we recommend that you define and use
SAPHA1JGW in your policy. There is no need for a second highly available gateway resource (SAPHA1GW) in
your policy.
In the case of an ABAP-only installation, you may still want to include SAPHA1GW in your policy.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 16
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
This means that in all shutdown phases the first pass will cause the JAVA enqueue server to stop normally.
All SAP JAVA application servers notice the stop. As a consequence, all JAVA application servers will
restart. As stopping and restarting of a JAVA application server can take quite some time, SAP JAVA
applications are not accessible to the SAP user during that time.
If the shutdown of the JAVA ES was intended to move the ES to another system (for example for planned
maintenance of the LPAR where it currently runs), that move is not transparent to the application server. To
actively trigger a failover of the JAVA enqueue server to another LPAR –AND-- to avoid the restart of Java
application servers, that means to make the failover seamless and transparent for the SAP users, you must
simulate an „unplanned‟ outage of the JAVA enqueue server. That can be easily done by killing the Java
enqueue server process with „kill -9‟.
Therefore we recommend changing the first pass of the STOP IMMED and STOP FORCE phases for the
SAPHA1JEN resource to:
1 INGUSS /bin/kill -9 &SUBSPID
rd nd
and to delete the second pass and rename the 3 to the 2 :
2 MVS C &SUBSUSSJOB,A=&SUBSASID
A STOP IMMED/ STOP FORCE will then initiate the following sequence:
- „kill -9‟ will stop the JAVA enqueue server immediately without the JAVA application servers being
notified.
- System Automation restarts the JAVA enqueue server on another LPAR
- the enqueue table is rebuilt from the information that the Enqueue Replication Server provides
- the JAVA application servers (re)connect to the enqueue server without restart
- SAP users can continue to work with the SAP JAVA applications and might only encounter a slight
delay during the rebuilt of the enqueue table
We highly recommend initiating such a failover by using STOP IMMEDiate or STOP FORCE.
SAPOSCOL
With the standard SAP 7.1 installation the SAP operating system collector saposcol is installed into the SAP
system independent path /usr/sap/hostctrl/exe.
If you intend to use the 7.1 SAPOSCOL you need to update the STARTUP entry in the “best practice policy”
for SAP of the System Automation APL SAPSYSOS as follows:
Replace the STARTUP command:
INGUSS JOBNAME=&SUBSJOB,/bin/tcsh -c '/usr/sap/HA1/SYS/exe/run/saposcol -l >&
/u/ha1adm/saposcol.&SYSNAME..log'
with:
INGUSS JOBNAME=&SUBSJOB,/bin/tcsh -c '/usr/sap/hostctrl/exe/saposcol -l >& /u/h
a1adm/saposcol.&SYSNAME..log'
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 17
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Installation
General Information
The SAP Web Dispatcher connects the Internet and the SAP System. The Web Dispatcher receives
requests from the internet (http/https) and forwards the request to an ABAP- or Java-Server. The incoming
requests are distributed among the application servers regarding their capacity weighting (the amount of
dialog-work-processes for AS ABAP and the amount of server processes for AS Java).
The Web Dispatcher has to be installed with its own SAP System Identifier (SID). This because it is planed
that up from SAP Netweaver 7.20 one SAP Web Dispatcher can handle several SAP Systems, SAP
Systems with different kernel versions.
There are two ways to install the SAP Web Dispatcher in z/OS Unix System Services (USS):
1. with SAP installation tool – you have to run it as a remote installation, because the GUI of sapinst
can not be started in USS.
2. with ZSCSinst for SAP Central Services on z/OS – a REXX script which is called from z/OS USS
command line. It simplifies the installation of SAP Central Services and of SAP Web Dispatcher.
The installation with ZSCSinst tool is similar to the installation of the SAP Central Services. As described in
chapter “SAP Central Services Installation on z/OS” the ZSCSinst tool can be downloaded from SAP Note
1322991 and follow the instructions from the SAP note and the the unpacked ZSCSInst_Instguide.doc
Make sure you use ZSCSinst version 710.7 or later. The version is displayed when running the command
without parameters from the z/OS Unix System Services shell:
./zscsinst
zscsinst version 710.7
Note: We recommend using ZSCSinst , because it is easier to handle and the installation is much faster.
In our environment the SAP Web Dispatcher has been installed with the ZSCSinst tool.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 18
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
After succesfull installation it is mandatory to follow the post installation steps like described in the ZSCSinst
Installation Guide.
With SAP NetWeaver Kernel 7.20 there is the possibility to manage with one SAP Web Dispatcher several
SAP Systems. This can be archieved by modifying the SAP Web Dispatcher instance profile. For each
wdisp_system enter the corresponding icm/server_port<x>, for example:
wdisp/system_0 = SID=BCO, MSHOST=bcomain, MSPORT=8127, SRCSRV=*:53548
wdisp/system_1 = SID=BIN, MSHOST=binmain, MSPORT=8082, SRCSRV=*:53547
icm/server_port_0 = PROT=HTTP,PORT=53548,
icm/server_port_1 = PROT=HTTP,PORT=53547,
For detailed information about SAP Web Dispatcher and its availablity please see the SAP Web Dispatcher
documentation in the SAP Library http://help.sap.com/ → SAP NetWeaver. Select the SAP NetWeaver
release and search for „SAP Web Dispatcher‟.
From sapinst main menu select the Standalone Engine –> Web Dispatcher
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 19
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
During the sapinst dialog you will be ask for the SAP System Identifier and the parameters to connect to the
message server.
The parameters for the connection to the target SAP System are message server host and message server
HTTP port:
Entered the instance number for Web Dispatcher and the HTTP port number.
The HTTP port number is used for the logon via web-browser:
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 20
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
User ID WD2ADM
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 21
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Condition WhenObservedAssumedDownOrStopping
This conditions results in a force down (hard down) of OMPRoute as soon as System Automation detects a
problem with TCPIP. A hard down OMPRoute in turn forces the SAP Central Services group(s) into a hard
down state and then SA moves them to another system. The groups are SAPHA1ASCS and/or
SAPHA1JSCS in our HA1 environment.
Note: you must remove OMPROUTE and PORTMAP from the AUTOLOG statement in the TCPIP profile, if both services
are managed as SA z/OS resources. Otherwise SA automation and TCPIP based restart can conflict.
The NFS server needs the PORTMAP and OMPROUTE resources to be available for proper operation so
you should introduce an additional HASPARENT relationship between System Automation APL NFSSERV
and PORTMAP and another HASPARENT between NFSSERV and OMPROUTE.
In order to trigger a failover of the NFS server in the case of an outage of PORTMAP or OMPROUTE, you
should add the following relationships System Automation APL NFSSERV on the one hand and PORTMAP
and OMPROUTE on the other hand as follows:
Condition WhenObservedAssumedDownOrStopping
and
Relationship Type FORCEDOWN
Condition WhenObservedAssumedDownOrStopping
These conditions results in a force down (hard down) of NFSSERV as soon as System Automation detects a
problem with either PORTMAP or OMPROUTE. It will cause the NFSSERV to move to another system.
Filesystem Recommendation
As already stated above, we recommend defining separate zFS filesystems for SCS and ASCS instance
directories in case of an ABAP and JAVA double stack installation. With a double stack installation there is
no technical reason why the SCS and the ASCS resources must run on the same z/OS LPAR. The SAP best
policy reflects this in the sense that there is no dependency between the resources.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 22
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Also the enqueue server of each central services instance needs access to its own instance directory which
should – for performance reasons – be owned by the LPAR on which the enqueue server is running.
Having separate filesystems for the ASCS and SCS instance directories allows System Automation
independent placement of JAVA central services (SCS) from ABAP central services (ASCS) in your Sysplex.
If you define only one filesystem for both the SCS and the ASCS instance, you might encounter a situation
where System Automation places the SCS on a different z/OS LPAR than the ASCS. Since only one LPAR
can have the ownership of the filesystem the other (A)SCS will encounter a performance penalty.
To actually move filesystem ownership for example for /usr/sap/<SAPSID>/ASCS<xx> to which the ABAP ENQ
server need access, you must adapt the Prestart automation policy item accordingly. For an ASCS00 directory and
the associated Enqueue Server resource SAPHA2AEN change the prestart automation item as in the following
example:
PRESTART
MVS SETOMVS FILESYS,FILESYSTEM='OMVS.ZFS.&SYSPLEX..USRSAP.HA2.ASCS00',SYSNAME=&SYSNAME.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 23
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 24
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Related Content
SAP Note 81737 ”DB2-z/OS: APAR List”
SAP Note 1326921 ”Updates are lost when restarting the ASCS instance”
SAP Note 1322991 ”ZSCSinst Installation tool for SAP Central services on z/OS”
SAP Note 1339004 “DB2-z/OS: Support of Logical Hostname in connect.ini”
SAP Note 1085521 “DB2-z/OS: Seamless JDBC Database Failover for SAP Java stack”
IBM documentation “Business Continuity for SAP on IBM System z (SC33-8206-02)” available from: IBM for
SAP High Availability Documentation
IBM product documentation: IBM Tivoli System Automation for z/OS
IBM product documentation: IBM Tivoli System Automation for Multiplatforms
SAP SDN: SAP for Banking on System z Reference Architecture
SAP SDN: SAP for Insurance on IBM System z Reference Architecture
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 25
Implementing High Availability for SAP NetWeaver 7.1 Technology on System z
Copyright
© Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 26