VERITAS Cluster Server Agent 3.

2 for SAP R/3

Installation and Configuration Guide
Solaris

May 2003

Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual. Copyright Copyright 1998-2003 VERITAS Software Corporation. All Rights Reserved. VERITAS is a registered trademark of VERITAS Software Corporation in the U.S. and other countries. The VERITAS logo and VERITAS Cluster Server are trademarks of VERITAS Software Corporation. All other trademarks or registered trademarks are the property of their respective owners. VERITAS Software Corporation 350 Ellis Street Mountain View, CA 94043 USA Phone (650) 527-8000 Fax (650) 527-2908 www.veritas.com

VCS Agent for SAP R/3: Installation and Configuration Guide

Table of Contents
Table of Contents ...................................................................................................................................... 3 Preface........................................................................................................................................................ 4 Technical Support ................................................................................................................................... 4 Conventions............................................................................................................................................. 4 Introduction............................................................................................................................................... 5 Version Numbers and Operating Systems.............................................................................................. 5 About the Agent ........................................................................................................................................ 5 Prerequisites .............................................................................................................................................. 7 Installing the Agent Software................................................................................................................... 7 Adding the Agent With Cluster Manager............................................................................................... 7 Configuring a SAP R/3 Resource ............................................................................................................ 9 VProSAP Resource Type ........................................................................................................................ 9 Type Definition .................................................................................................................................. 13 Sample Configuration........................................................................................................................ 14 Clustering SAP R/3 ................................................................................................................................. 14 Central Instance and Database Server in One Cluster Server Service Group ....................................... 15 Central Instance and Database Server in Two Different Cluster Server Service Groups...................... 15 File Sharing Between the Database Server and Central Instance.......................................................... 15 File Sharing Between the Central Instance and the Application Servers .............................................. 15 Sample Service Group Configuration ................................................................................................... 16 Configuring SAP R/3 Central Instance to Support Clustering.............................................................. 16 Configuring SAP R/3 Dialog (Application) Instance to Support Clustering ........................................ 18 Removing the Agent Software ............................................................................................................... 19 Release Notes ........................................................................................................................................... 20

VCS Agent for SAP R/3: Installation and Configuration Guide

Preface
This document provides instructions for installing and configuring the VERITAS Cluster Server Agent for SAP R/3. For information about VERITAS Cluster Server, refer to the VERITAS Cluster Server Users Guide. Technical Support For assistance with this VERITAS product, or for information regarding VERITAS service packages, contact Technical Support at (800) 342-0652 (U.S. and Canada). You may also contact Technical Support via e-mail at support@veritas.com. For Customers Outside U.S. and Canada From Europe, the Middle East, or Asia, visit the Technical Support Web site at http://support.veritas.com for a list of each countrys contact information. Conventions Typeface Courier courier (bold) italic Italic Symbol % $ # Usage Computer output, files, attribute names, device names, and directories User input and commands, keywords in grammar syntax New terms, titles, emphasis Variables Usage C shell prompt Bourne/Korn shell prompt Super user prompt (for all shells)

VCS Agent for SAP R/3: Installation and Configuration Guide

Introduction
Welcome to the VERITAS Cluster Server Agent for SAP R/3. This guide describes the agent, its modes of operation, and its attributes. It also describes how to install and configure the agent. The guide assumes the reader understands the primary components and basic functionality of VERITAS Cluster Server. It also assumes a basic understanding of SAP R/3 and SAP R/3-based application architecture and configuration.

Version Numbers and Operating Systems

VERITAS Cluster Server Agent 3.2 for SAP R/3 has been tested with VERITAS Cluster Server 3.5 on Solaris 8. The agent supports SAP R/3 and R/3-based application versions 4.5x, 4.6x, and 6.20 as well as SAP R/3 Enterprise 4.7. In this guide all references to SAP R/3 will refer to all versions unless otherwise noted. The SAP R/3 agent was developed using the VPro Agent Framework. The VPro Agent Framework, developed by VERITAS, is a set of libraries that contain common, reusable functions such as process identification, logging, system calls, and many others. The VPro Agent Framework is included and installed with VERITAS Cluster Server 3.5; thus, the agent can be used immediately after it is installed in a VERITAS Cluster Server 3.5 environment. The VPro Agent Framework is not included with VERITAS Cluster Server 2.0. Although not formally tested, version 3.2 of the SAP R/3 agent should also work with VERITAS Cluster Server 2.0 using the VPro Agent Framework add-on package. To use this agent with VERITAS Cluster Server 2.0, contact VERITAS Enterprise Consulting Services to obtain a copy of the VPro Agent Framework.

About the Agent

The SAP R/3 agent consists of resource type declarations and agent executables. They are described below. SAP R/3 Agent: VProSAP Description Brings a SAP R/3 instance online, monitors the R/3 related processes, and brings the SAP R/3 instance offline. Online: Starts a SAP R/3 instance by performing the following steps: 1. 2. 3. Set the user name (SAPAdmin) and source the environment (EnvFile) under which the instance will run. Remove IPC resources remaining from unclean shutdowns of this instance using the SAP supplied cleanipc program. If the Version attribute is set to 4, execute startsap_hostname_InstID r3. If the Version attribute is set to 47 or 6 execute startsap r3

Operations

Offline: Stops a SAP R/3 instance by performing the following steps: 1. 2. Set the user name (SAPAdmin) and source the environment (EnvFile) under which the instance will run. If the Version attribute is set to 4, execute stopsap_hostname_InstID r3. If the Version attribute is set to 47 or 6 execute stopsap r3. Verify that all processes associated with this SAP instance are stopped. Terminate saposcol if this is the last SAP instance running on this node.

3. 4.

VCS Agent for SAP R/3: Installation and Configuration Guide

Monitor: Monitors the state of a SAP R/3 instance by performing the following steps: 1. Scan the process table to verify that SAP processes are running. The default central instance processes monitored are dw,se,co, and ms. The default dialog (application server) instance processes monitored are dw and se. The list of processes monitored by the agent is defined by the agent attribute ProcMon. If the dw process is to be monitored, the parent dw process is the only dw process that is monitored by VERITAS Cluster Server. This parent process restarts any failed child dw processes; therefore, Cluster Server does not need to monitor those child processes. If attribute SecondLevelMonitor is set to 1 (true), then sapinfo is run to interrogate the health of the SAP R/3 instance. If an external monitor program is defined by the attribute MonitorProgram, it is executed, and the results are reported to VERITAS Cluster Server.

2. 3.

Clean: Removes SAP R/3 system resources that may remain after an unsuccessful attempt to online or offline a SAP R/3 resource or a failure in monitoring. If the clean entry point is called due to an unexpected offline, the entry point first attempts to gracefully shutdown the application using the stopsap script. Clean then attempts to run the kill.sap script if it exists. If any processes that are associated with the SAP instance still exist ten seconds after the kill.sap script is executed they are terminated. Finally, any IPC resources owned by user SAPAdmin are removed by using the SAP supplied cleanipc program. Detecting Application Failure The agent monitor follows a three-step process to detect failure. The monitor entry point will always execute the process check but will only execute the second-level state check if the SecondLevelMonitor attribute value is set to 1 (true) and the first-level process check indicates that the instance is online. The monitor entry point will only execute the third-level state check if the MonitorProgram attribute value is set, the first-level process check indicates that the instance is online and second-level check indicates that the instance is online or second-level monitoring is disabled. The three monitor algorithms are further detailed as follows: 1. 2. Process Check. Check for the existence of SAP application processes specified by the attribute ProcMon. Second-Level Check. The second-level check runs the SAP supplied program sapinfo to determine the health of the instance. This check ensures that the processes are truly available for user processing. Third-Level Check. The third-level check runs the user defined program MonitorProgram. The return code of this program must be 0 or 110 (online), 1 or 100 (offline), or 99 (Unknown). This check allows the administrator to run a user supplied script.

3.

VCS Agent for SAP R/3: Installation and Configuration Guide

Prerequisites
Install and configure VERITAS Cluster Server. If necessary, review the VERITAS Cluster Server Installation Guide. Remove any prior version of the SAP R/3 agent. Verify that all systems have enough resources, such as shared memory, to run the application instance.

Installing the Agent Software

Perform the following steps on each system in the cluster. 1. 2. 3. Log in as root. Copy the agent installation file to a temporary directory. Change to the temporary directory created in the previous step, extract the contents of the installation file, and then change to the pkgs directory.
# cd /temp_directory # uncompress file_name.tar.Z # tar xvf file_name.tar # cd pkgs

4.

Install the package. Follow the package-add prompts and select the VERITAS VCS SAP Agent package. Other displayed packages may be ignored.
# pkgadd d .

5.

Verify the package was installed correctly by using the Solaris pkginfo command as follows:
# pkginfo l VRTSsap PKGINST: VRTSsap NAME: VERITAS VCS SAP agent CATEGORY: application ARCH: generic VERSION: 3.2 VENDOR: VERITAS Software Corporation DESC: VERITAS VCS SAP R/3 Agent. This package requires an activation key. PSTAMP: 3.2b85 2003053011 INSTDATE: May 30 2003 14:43 EMAIL: support@veritas.com STATUS: completely installed FILES: 11 installed pathnames 2 directories 5 executables 163 blocks used (approx)

Adding the Agent With Cluster Manager

To use the SAP R/3 agent without stopping and restarting VERITAS Cluster Server, import the VProSAPTypes.cf file into the VERITAS Cluster Server engine by performing the following steps in Cluster Manager (the Cluster Server graphical user interface). 1. Start Cluster Manager. 7

VCS Agent for SAP R/3: Installation and Configuration Guide

2. 3.

Click on the File menu and select Import Types. In the Import Types dialog box, select the following file:
/etc/VRTSvcs/conf/sample_VProSAP/VProSAPTypes.cf

4. 5.

Click the Import button. Save the Cluster Server configuration.

At this point, the VProSAP types have been imported to the Cluster Server engine. VProSAP resources may now be created. For detailed information about using the Cluster Manager, refer to the VERITAS Cluster Server Users Guide.

VCS Agent for SAP R/3: Installation and Configuration Guide

Configuring a SAP R/3 Resource

After installing the agent programs and importing the configuration file, a SAP R/3 resource can be created and configured by using Cluster Manager. Before you configure a resource, review the following table that describes the SAP R/3 resource type and its attributes. The resource type definition file and a sample main.cf configuration are also shown for reference. VProSAP Resource Type Attribute ActivationKey Definition Type: String-scalar Description: License key that enables the use of the agent for each resource. Obtain the key from your VERITAS sales representative. The agent will not function properly without a valid key. This attribute is required and must have a valid value. Example: A123456789 Default Value: No default value EnvFile Type: String-scalar Description: Name of the file used to setup required environment variables. It must be a fully qualified path to the environment file. This attribute is required and is the only method by which needed environment variables are set. Example: /home/prdadm/.login Default Value: No default value InstID Type: String-scalar Description: Instance ID defined during SAP R/3 system installation. The instance ID must be a two-digit number between 00 and 96 and must be unique on a single server. If the instance ID is less than 10 then a zero (0) must be included before the instance ID. This attribute is required. Example: 00 Default Value: No default value

VCS Agent for SAP R/3: Installation and Configuration Guide

Attribute InstName

Definition Type: String-scalar Description: Defines the resource as either a central instance or a dialog (application) server. For a central instance, the InstName is set to DVEBMGS and for an application instance the InstName is set to D. This attribute is required. Example: DVEBMGS Default Value: DVEBMGS

ProcMon

Type: String-scalar Description: The list of SAP processes to monitor. The list of processes is space separated and can be specified in any order. The valid values for a central instance are dw, se, ms, and co. Valid values for a dialog (application) instance are dw and se. For a given instance not all of the processes need to be specified. For example, in a central instance, the ms process could be the only one monitored. This attribute is required. Example: dw se ms co Default Value: dw se ms co

MonitorProgram

Type: String-scalar Description: Full path, filename, and any needed arguments to the tertiary monitor program. Specifying a value for MonitorProgram triggers the execution of the program if the filename exists and is executable by SAPAdmin. This attribute is optional. Example: /home/prdadm/monitorprogram monitor Default Value: No default value

MonitorProgramTimeout

Type: Integer Description: Number of seconds the monitor entry point will wait on the execution of a monitor program. If the monitor program does not return to the calling monitor entry point before the MonitorProgramTimeout window expires, the monitor entry point will terminate the execution of MonitorProgram and will report that the resource is offline. Example: 15 Default Value: 30

VCS Agent for SAP R/3: Installation and Configuration Guide

10

Attribute SAPAdmin

Definition Type: String-scalar Description: UNIX user name in /etc/passwd, NIS domain or LDAP directory defined as owner of SAP R/3 directories and executables. The online, offline, monitor, and clean scripts execute SAP R/3 commands using this name. The SAP R/3 processes are owned by this username. A user name commonly used is SAPSIDadm. This value does NOT have to be unique in a cluster. The users login shell may be Bourne, C, or Korn. The .login or .profile file for this user is NOT sourced prior to performing an online, offline, or monitor. This attribute is required. Example: prdadm Default Value: No default value

SAPHost

Type: String-scalar Description: Name of the virtual hostname assigned to this SAP instance. This value is only used if the Version attribute is set to 4. If Version is set to 4, and the attribute SAPHost is defined, then the start and stop script use the SAPHost value to determine the name of the start and script scripts rather than using the local hostname. This value is optional. Example: sapci Default Value: No default value

SAPSID

Type: String-scalar Description: SAP R/3 system name defined during installation. This attribute is required and will be exactly three characters. Example: PRD Default Value: No default value

VCS Agent for SAP R/3: Installation and Configuration Guide

11

Attribute SecondLevelMonitor

Definition Type: Boolean Description: Enables second-level monitoring for the resource. Second-level monitoring is a deeper, more thorough state check of the SAP instance. The secondlevel monitor checks the state of the SAP R/3 instance using sapinfo. To use sapinfo, you must install RFC-SDK from the SAP Presentation CD. The file is named RFC.CAR and has to be extracted to the /usr/sap/<SID>/SYS/exe/run directory using the SAP utility SAPCAR. Valid attribute values are 1 (true) and 0 (false). Example: 0 Default Value: 0

SecondLevelMonitorTimeout

Type: Integer Description: Number of seconds the monitor entry point will wait on the execution of a second-level monitor program. If the second level monitor program does not return to the calling monitor entry point before the SecondLevelTimeout window expires, the monitor entry point will terminate the execution of the secondlevel monitor and will report that the resource is offline. Example: 30 Default Value: 30

Version

Type: Integer Description: Used to determine how the SAP instance is started and stopped. Set the value of the Version attribute to 4 for applications using SAP R/3 4.5X and 4.6X technology, 6 for SAP applications using SAP R/3 6.2 technology, and 47 for SAP applications using SAP R/3 Enterprise 4.7 technology. Example: 4 Default Value: No default value

VCS Agent for SAP R/3: Installation and Configuration Guide

12

Attribute VProLogLevel

Definition Type: String-scalar Description: Controls the logging detail performed by the agent for this specific instance of a resource. Valid values are listed as follows: ERROR WARN INFO Only error level messages are logged Error and warning level messages are logged Error, warning, and informational level messages are logged. This is the default value. Error, warning, informational, and trace level messages are logged. Trace logging is very verbose and should only be used during initial configuration or to facilitate troubleshooting.

TRACE

Example: INFO Default Value: INFO

Type Definition type VProSAP ( static str ArgList[] = { VProLogLevel, ActivationKey, State, IState, SAPSID, InstName, InstID, SAPAdmin, MonitorProgram, MonitorProgramTimeout, ProcMon, SecondLevelMonitor, SecondLevelMonitorTimeout, EnvFile, Version, SAPHost } NameRule = group.name + "_" + resource.SAPSID + "_" + resource.InstName + resource.InstID str VProLogLevel = INFO str ActivationKey str SAPSID str InstName str InstID str SAPAdmin str MonitorProgram int MonitorProgramTimeout = 30 str ProcMon = "dw ms co se" boolean SecondLevelMonitor =0 int SecondLevelMonitorTimeout = 30 str EnvFile int Version str SAPHost )

VCS Agent for SAP R/3: Installation and Configuration Guide

13

Sample Configuration The following is an excerpt from a main.cf file that included a SAP R/3 resource. The activation key is only an example. It will not enable the SAP resource. VProSAP SAP46_app ( ActivationKey SAPSID InstName InstID SAPAdmin MonitorProgramTimeout ProcMon SecondLevelMonitor SecondLevelMonitorTimeout EnvFile Version SAPHost
)

= = = = = = = = = = = =

A123456790 PRD DVEBMGS 05 prdadm 5 "dw ms se co" 1 5 "/home/prdadm/.login" 4 sapci

Clustering SAP R/3

The SAP central instance and database are single points of failure and need to be protected from hardware and system software failures. The configurations described in this section concentrate on protecting the continuous availability of the central instance. The protection of the database is covered in the VERITAS Cluster Server Agent for Oracle Install and Configuration Guide. Typically, in a production environment, SAP application servers are deployed on different systems than the database and central instance. The SAP R/3 GUI can reconnect to a different application server if the current application server fails for any reason. Therefore, protecting an application server in an R/3 system is generally not required but is supported by this agent. The configurations described here are based on the SAP-recommended switchover scenarios as described in the SAP documented titled SAP R/3 in Switchover Environments. The SAP R/3 agent supports the most common switchover scenarios. For a more specific, customized configuration, contact VERITAS Enterprise Consulting Services. This agent supports the following switchover scenarios as defined by the document SAP R/3 in Switchover Environments: Switchover Scenario-1 and Switchover Scenario-2: The database and central instance run on two different cluster nodes and use each others host as the standby node. No application server is running in either cluster node. Switchover Scenario-3: The database and central instance run on the same cluster node, and the second cluster node is used as the standby node for the database and central instance. An application server instance may run on the standby node.

A cluster node is a host machine that is part of a VERITAS Cluster Server cluster. The standby node means that a service group switches over to that node if the primary node fails. The following sections describe how to use the agent in different switchover scenarios to achieve the high availability requirement of the R/3 system. For details on configuring the SAP R/3 system for each switchover scenario, see SAP R/3 in Switchover Environments.

VCS Agent for SAP R/3: Installation and Configuration Guide

14

Central Instance and Database Server in One Cluster Server Service Group In a typical SAP R/3 installation, the database and central instance are on the same host machine. All SAP R/3 related resources, such as database files, disk groups, database server, SAP server, and network, can be configured in a single service group and have a standby node to switch the service group over in case of an unrecoverable error on the active host. The standby may have an application server running, which corresponds to Switchover Scenario-3. When starting the central instance, the SAP start script checks the availability of the Oracle database by trying to connect to it using the command R3trans d w. If the connection fails, the start script tries to start the Oracle server as well. If a system has just been rebooted, this will typically fail because the SAP startup script does not start the Oracle SQL*Net listener process before it attempts to start the Oracle server. It is recommended that customers control the Oracle database by the use of the VERITAS Cluster Server agent for Oracle and the VERITAS Cluster Server agent for SQL*Net, allowing a more flexible startup of the underlying disk storage resources. The SAP central instance resource must be the parent of the Oracle server and SQL*Net resources in the SAP service group. Central Instance and Database Server in Two Different Cluster Server Service Groups In a large SAP R/3 installation, the database and central instance are commonly on two separate machines due to the resource contention. In an HA environment, each machine can be the standby node for the each other. If the host running the database fails, the database switches over to the central instance host. It is very important to reserve machine resources, such as CPU and memory, when planning the installation so either host in the cluster is capable of running both the central instance and database together. This configuration is referred to as Switchover Scenario-1 or Switchover Scenario-2 by SAP in SAP R/3 in Switchover Environment. Typically, both the database and central instance have their own service group. For example, group CIGRP is on host sysa, and group DBGRP is on host sysb. Because the database must be running before the central instance can be started, bring group DBGRP online globally before bringing CIGRP online. The following command establishes the group dependency:
# hagrp -link DBGRP CIGRP online global

DBGRP must be online in any cluster node before CIGRP can be online. The SQL*Net listener should be configured on a virtual IP address. An IP resource for the virtual address is a prerequisite to bringing the SQL*Net address online. File Sharing Between the Database Server and Central Instance The central instance runs on its own machine and requires Oracle client software, which is mounted by default on /oracle/SAPSID. The database has its own /oracle/SAPSID file system that contains the full Oracle software distribution. In addition, the database also requires SAP executables. These executables are available from /usr/sap/SAPSID/SYS/exe/run within the central instance. Therefore, both /oracle/SAPSID and /usr/sap/SAPSID/SYS/exe/run should be mounted on both nodes at the same time. It is recommended that users of the VERITAS Cluster Server Agent for SAP R/3 maintain a local copy of /oracle/SAPSID and /usr/sap/SAPSID/exe/run for both the central instance and database hosts instead of sharing them through NFS. It is also recommended that the file systems /oracle/SAPSID and /usr/sap/SAPSID/SYS/exe/run be controlled by the operating system and not VERITAS Cluster Server. File Sharing Between the Central Instance and the Application Servers The application servers typically require that /usr/sap/trans, /$sapmnt/SAPSID/global, and /$sapmnt/SAPSID/profile be NFS mounted from the Central Instance. Therefore it is necessary to share those resources using NFS. It is recommended that /$sapmnt/SAPSID/exe be maintained as a local copy rather than sharing them through NFS. This is consistent with the recommendation in the document SAP R/3 in Switchover Environments.

VCS Agent for SAP R/3: Installation and Configuration Guide

15

Sample Service Group Configuration Figure 1 is an example service group that would support a SAP R/3 Central Instance.

SAP CI

NFS Share(s)

IP

Mount(s)

NFS

NIC

Disk Group

Figure 1 - Service group for a SAP R/3 central instance

Configuring SAP R/3 Central Instance to Support Clustering The following configurations are required for a central instance to run properly within the cluster: 1. 2. 3. 4. Ensure that usernames and groups exist on all nodes of the cluster. Ensure that /etc/services entries are duplicated on all nodes in the cluster. Ensure that UIDs and GIDs are synchronized on all nodes in the cluster. If the Version attribute is set to 4 and the attribute SAPHost is NOT defined, then the following six environment files in the SAPAdmin home directory need to be copied for each host that SAP R/3 could run on: .sapenv_installedhostname.csh .sapenv_installedhostname.sh .dbenv_installedhostname.csh .dbenv_installedhostname.sh startsap_installedhostname_InstID stopsap_installedhostname_InstID Each file must be duplicated for each host that the SAP R/3 instance could run on. For example: # cp .sapenv_installedhostname.csh .sapenv_otherhostname.csh 5. If the Version attribute is set to 4 and the attribute SAPHost is defined, then the following six environment files in the SAPAdmin home directory need to be renamed to the virtual host that SAP R/3 will run on: .sapenv_installedhostname.csh VCS Agent for SAP R/3: Installation and Configuration Guide 16

.sapenv_installedhostname.sh .dbenv_installedhostname.csh .dbenv_installedhostname.sh startsap_installedhostname_InstID stopsap_installedhostname_InstID Each file must be duplicated for each host that the SAP R/3 instance could run on. For example: # cp .sapenv_installedhostname.csh .sapenv_virtualhostname.csh 6. If the Version attribute is set to 47 or 6, then the following eight environment files in the SAPAdmin home directory need to be copied for each host that SAP R/3 could run on: .sapenv_installedhostname.csh .sapenv_installedhostname.sh .dbenv_installedhostname.csh .dbenv_installedhostname.sh .sapsrc_installedhostname.csh .sapsrc_installedhostname.sh .dbsrc_installedhostname.csh .dbsrc_installedhostname.sh

Each file must be duplicated for each host that the SAP R/3 instance could run on. The files can either be copied or hard linked. For example: # ln .sapenv_installedhostname.csh .sapenv_otherhostname.csh 7. 8. Ensure that the home directory of the SAPAdmin user is on shared storage or is copied to all servers. Edit /usr/sap/SAPSID/SYS/profile/DEFAULT.PFL and change the following items: 9. Set SAPDBHOST to the virtual hostname of the database server Replace all instances of the physical CI hostname with the virtual name

Rename /usr/sap/SAPSID/SYS/profile/SAPSID_DVEBMGSInstID_installedhostname to /usr/sap/SAPSID/SYS/profile/SAPSID_DVEBMGSInstID_virtualhostname and edit the file to change the following items: Add SAPGLOBALHOST = virtualhostname Add SAPLOCALHOST = virtualhostname Add SAPLOCALHOSTFULL = virtualhostname

10. Copy or hard link /usr/sap/SAPSID/SYS/profile/SAPSID_DVEBMGSInstID_virtualhostname to /usr/sap/SAPSID/SYS/profile/SAPSID_DVEBMGSInstID_otherhostname where otherhostname is replaced by any server the resource can run on. 11. Rename /usr/sap/SAPSID/SYS/profile/START_DVEBMGSInstID_installedhostname to /usr/sap/SAPSID/SYS/profile/START_DVEBMGSInstID_virtualhostname and edit the file to change any physical hostnames to virtual hostnames.

12. Copy or hard link VCS Agent for SAP R/3: Installation and Configuration Guide 17

/usr/sap/SAPSID/SYS/profile/START_DVEBMGSInstID_virtualhostname to /usr/sap/SAPSID/SYS/profile/START_DVEBMGSInstID_otherhostname where otherhostname is replaced by any server the resource can run on.

Configuring SAP R/3 Dialog (Application) Instance to Support Clustering The following configurations are required for a dialog instance to run properly within the cluster: 1. 2. Ensure that /etc/services entries are duplicated on all nodes in the cluster. If the Version attribute is set to 4 and the attribute SAPHost is NOT defined, then the following six environment files in the SAPAdmin home directory need to be copied for each host that SAP R/3 could run on: .sapenv_installedhostname.csh .sapenv_installedhostname.sh .dbenv_installedhostname.csh .dbenv_installedhostname.sh startsap_installedhostname_InstID stopsap_installedhostname_InstID Each file must be duplicated for each host that the SAP R/3 instance could run on. For example: # cp .sapenv_installedhostname.csh .sapenv_otherhostname.csh 3. If the Version attribute is set to 4 and the attribute SAPHost is defined, then the following six environment files in the SAPAdmin home directory need to be renamed to the virtual host that SAP R/3 will run on: .sapenv_installedhostname.csh .sapenv_installedhostname.sh .dbenv_installedhostname.csh .dbenv_installedhostname.sh startsap_installedhostname_InstID stopsap_installedhostname_InstID Each file must be duplicated for each host that the SAP R/3 instance could run on. For example: # cp .sapenv_installedhostname.csh .sapenv_virtualhostname.csh 4. If the Version attribute is set to 47 or 6, then the following eight environment files in the SAPAdmin home directory need to be copied for each host that SAP R/3 could run on: .sapenv_installedhostname.csh .sapenv_installedhostname.sh .dbenv_installedhostname.csh .dbenv_installedhostname.sh .sapsrc_installedhostname.csh .sapsrc_installedhostname.sh .dbsrc_installedhostname.csh .dbsrc_installedhostname.sh Each file must be duplicated for each host that the SAP R/3 instance could run on. The files can either be copied or hard linked. For example: # ln .sapenv_installedhostname.csh .sapenv_otherhostname.csh 5. Ensure that the home directory of the SAPAdmin user is on shared storage or is copied to all servers

VCS Agent for SAP R/3: Installation and Configuration Guide

18

6.

Rename /usr/sap/SAPSID/SYS/profile/SAPSID_DVEBMGSInstID_installedhostname to /usr/sap/SAPSID/SYS/profile/SAPSID_DVEBMGSInstID_virtualhostname and edit the file to change the following items: Add SAPGLOBALHOST = virtualhostname Add SAPLOCALHOST = virtualhostname Add SAPLOCALHOSTFULL = virtualhostname

7.

Copy or hard link /usr/sap/SAPSID/SYS/profile/SAPSID_DVEBMGSInstID_virtualhostname to /usr/sap/SAPSID/SYS/profile/SAPSID_DVEBMGSInstID_otherhostname where otherhostname is replaced by any server the resource can run on. Rename /usr/SAP/SAPSID/SYS/profile/START_DVEBMGSInstID_installedhostname to /usr/sap/SAPSID/SYS/profile/START_DVEBMGSInstID_virtualhostname and edit the file to change any physical hostnames to virtual hostnames. Copy or hard link /usr/sap/SAPSID/SYS/profile/START_DVEBMGSInstID_virtualhostname to /usr/sap/SAPSID/SYS/profile/START_DVEBMGSInstID_otherhostname where otherhostname is replaced by any server the resource can run on.

8.

9.

Removing the Agent Software

Follow the steps below to remove the SAP R/3 agent from VERITAS Cluster Server. These steps must be performed while the cluster is started. 1. 2. Remove all resources from the cluster that use the SAP R/3 agent. Set the Cluster Server configuration mode to read/write by typing the following command from any system in the cluster (must be logged in as user root):
# haconf -makerw

3.

Remove the agent from the Cluster Server configuration by typing the following command from any system in the cluster. This will remove the include statement for the agent from main.cf, but the agents type file will not be removed.
# hatype -delete VProSAP

4.

Set the Cluster Server configuration mode to read-only by typing the following command from any system in the cluster:
# haconf dump -makero

5.

On each node in the cluster, use the package remove program to uninstall the VERITAS Cluster Server agent.
# pkgrm VRTSsap

VCS Agent for SAP R/3: Installation and Configuration Guide

19

Release Notes
Listed below are fixes and enhancements to the VERITAS Cluster Server Agent for SAP. Applications using SAP R/3 6.2 or SAP R/3 4.7 technology are now supported. The agent now supports using the C shell for the SAPAdmin user. The profile of the user SAPAdmin is not sourced. All environment variables must be set using the EnvFile attribute. The EnvFile attribute is now required. The parent dw process is the only dw process monitored; all child dw processes are ignored as they are restarted by the parent dw process. The output by the second-level monitor program (sapinfo) is no longer sent to the engine log. Monitor running on the offline node no longer generates messages. /sapmnt is no longer assumed to be the sapmnt directory. Three new attributes have been added: MonitorProgramTimeout SecondLevelMonitorTimeout SAPHost

VCS Agent for SAP R/3: Installation and Configuration Guide

20