VERITAS Cluster Server Agent 3.0 for SAP R/3

Transcription

1 VERITAS Cluster Server Agent 3.0 for SAP R/3 Installation and Configuration Guide Solaris September 2002

2 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 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 USA Phone (650) Fax (650) VCS Agent for SAP R/3: Installation and Configuration Guide 2

3 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... 6 About the SAP R/3 Agent... 6 Central Instance and Database Server in One VCS Service Group... 7 Central Instance and Database Server in Two Different VCS Service Groups... 7 File Sharing Between the Database Server and Central Instance... 7 File Sharing Between the Central Instance and the Application Servers... 7 Installing the Agent Software... 8 Adding the Agent With Clus ter Manager... 8 Configuring a SAP R/3 Resource... 8 VProSAP Resource Type... 8 Type Definition... 9 Sample Configuration Sample Service Group Configuration...10 Configuring SAP R/3 Central Instance to Support Clustering...11 Configuring SAP R/3 Dialog Instance to Support Clustering...11 Removing the Agent Software VCS Agent for SAP R/3: Installation and Configuration Guide 3

4 Preface This document provides instructions for installing and configuring the VERITAS Cluster Server (VCS) Agent for SAP R/3. For information about VERITAS Cluster Server, refer to the VERITAS Cluster Server User s Guide. Technical Support For assistance with this VERITAS product, or for information regarding VERITAS service packages, contact Technical Support at (800) (U.S. and Canada). You may also contact Technical Support via 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 for a list of each country s contact information. Conventions Typeface Courier courier (bold) italic Usage Computer output, files, attribute names, device names, and directories User input and commands, keywords in grammar syntax New terms, titles, emphasis Italic Variables Symbol Usage % C shell prompt $ Bourne/Korn shell prompt # Super user prompt (for all shells) VCS Agent for SAP R/3: Installation and Configuration Guide 4

5 Introduction Welcome to the VERITAS Cluster Server (VCS) 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 VCS. It also assumes a basic understanding of SAP R/3 application architecture and configuration. Version Numbers and Operating Systems VCS Agent 3.0 for SAP R/3 has been tested with VCS 2.0 and VCS 3.5 on Solaris 8. The agent supports SAP R/3 versions 4.5x and 4.6x. 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 VCS 3.5; thus, the agent can be used immediately after it is installed. The VPro Agent Framework is not included with VCS 2.0. To use this agent with VCS 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 Operations 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 using the following steps: 1. Set the user name and environment under which the instance will run. 2. Execute startsap_hostname_instid Offline: Stops a SAP R/3 instance by executing stopsap_hostname_instid 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 are dw,se,co, and ms. The default dialog instance processes monitored are dw and se. The list of processes to monitor is defined by the agent attribute ProcMon. 2. If an external mo nitor program is defined by the attribute MonitorProgram, it is executed, and the results are reported to VCS. 3. If attribute SecondLevelMonitor is set to 1 (true), then sapinfo is run to interrogate the health of the SAP R/3 instance. 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. Clean first attempts to run the kill.sap script if it exists. If processes still exist after the script is executed they will be terminated. Finally, any IPC resources owned by user SAPAdmin are removed by using the supplied cleanipc script. VCS Agent for SAP R/3: Installation and Configuration Guide 5

6 Detecting Application Failure The SAP R/3 resource is faulted if any of the configured processes are not found in the process table. Additionally, the resource is faulted if the MonitorProgram or the SecondLevelMonitor indicates that the resource is unavailable. If this happens, the entire SAP service group will switch to the next available system listed in the service group s SystemList attribute. Prerequisites Install and configure VCS. 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 services. About the SAP R/3 Agent 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 VCS 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 SAP R/3 in Switchover Environments (SAP documentation). The SAP R/3 agent supports the most common switchover scenarios. For a more specific, customized configuration, contact VERITAS Enterprise Consulting Services. The supported switchover scenarios are: Switchover Scenario-1 and Switchover Scenario-2: The database and central instance run on two different cluster nodes and use each other s 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 VCS cluster. The standby node means that a VCS service group switches over to the node if the primary node fails. The following sections describe how to use the agents 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 (SAP documentation). VCS Agent for SAP R/3: Installation and Configuration Guide 6

7 Central Instance and Database Server in One VCS 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 put in a single VCS service group and have a standby node to switch the service group over in case of an unrecoverable error on the currently running host. The standby may have an application server running, which corresponds to Switchover Scenario-3, as defined in SAP R/3 in Switchover Environments (SAP documentation). When starting the SAP central instance, the start script startsap_virtualhostname_instid 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 VCS agent for Oracle and the VCS agent for SQL*Net, allowing a more flexible startup of the underlying disk, disk group, volume, and mount 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 VCS 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 the database host or central instance host are 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 Environments (SAP documentation). 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 /sapmnt/sapsid/exe within the central instance. Therefore, both /oracle/sapsid and /sapmnt/sapsid/bin should be mounted on both nodes at the same time. It is recommended that users of the VCS Agent for SAP R/3 maintain a local copy of /oracle/sapsid and /sapmnt/sapsid/exe for both the central instance and database hosts instead of sharing them through NFS. It is also recommended that /oracle/sapsid and /sapmnt/sapsid/exe be put outside of the service groups (DBGRP and CIGRP) and automatically mounted when the systems reboot. 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 7

8 Installing the Agent Software Perform the following steps on each system in the cluster. 1. Log in as root. 2. Copy the agent installation file, VRTSsap.3.0.sol.tar.Z to a temporary directory. 3. Change to the temporary directory created in the previous step and then extract the contents of the installation file. # cd /[temp directory] # uncompress VRTSsap.3.0.sol.tar.Z # tar xvf VRTSsap.3.0.sol.tar 4. Remain in the same temporary directory and initiate adding the package. Follow the package-add prompts and select the VProSAP agent package. # pkgadd d. Adding the Agent With Cluster Manager To use the SAP R/3 agent without stopping and restarting VCS, import the VProSAPTypes.cf file into the VCS engine by performing the following steps in Cluster Manager (the VCS graphical user interface). 1. Start Cluster Manager. 2. Click on the File menu and select Import Types. 3. In the Import Types dialog box, select the following file: /etc/vrtsvcs/conf/sample_vprosap/vprosaptypes.cf 4. Click the Import button. 5. Save the VCS configuration. At this point, the VProSAP types have been imported to the VCS engine. VProSAP resources may now be created. For detailed information about using the VCS Cluster Manager, refer to the VERITAS Cluster Server User s 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 VCS 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 Type and Dimension Definition SAPSID string-scalar SAP R/3 System name defined during installation (three characters). InstName string-scalar SAP R/3 Instance Name defines the resource as a central instance or a dialog Server. Central instance = DVEBMGS Application (dialog) instance = D (dialog processes only) InstID string-scalar Instance ID defined during SAP R/3 system installation. The VCS Agent for SAP R/3: Installation and Configuration Guide 8

9 Attribute Type and Dimension Definition instance ID must be a two digit number between and must be unique on a single server. SAPAdmin string-scalar UNIX account name used to start and stop SAP services. The default name used by SAP is SAPSIDadm. MonitorProgram string-scalar Full path and filename to the secondary monitor script. Defining a MonitorProgram triggers the execution of the script if the filename exists and is executable by root. Setting the attribute is optional. ProcMon string-scalar SAP processes to monitor. The default for the central instance, set in SAPTypes.cf, is dw, ms, co, and se. The default values for a dialog instance are dw and se. SecondLevelMonitor integer Enables second-level monitoring for the resource. Valid values are 0 and 1. Default value is 0. The second-level monitor checks the state of the SAP R/3 instance using sapinfo. EnvFile string-scalar Full path and file name of the script or program that sets the environment prior to executing SAP programs. If the environment is set by the profile of the user specified in attribute SAPAdmin, a dummy file name must be specified that has no impact on the system (e.g./bin/true). Version string-scalar The default is version 4, which indicates that the system is running version 4.x of SAP R/3. ActivationKey string-scalar 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. LogLevel string-scalar Controls the logging detail performed by the agent for this specific instance of a resource. Valid values are as follows: ERROR WARN INFO TRACE 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. Type Definition type VProSAP ( static int OnlineWaitLimit = 1 static str ArgList[] = { VProLogLevel, ActivationKey, SAPSID, InstName, InstID, SAPAdmin, MonProgram, ProcMon, SecondLevelMonitor, EnvFile, Version } NameRule = group.name + "_" + resource.sapsid + "_" + VCS Agent for SAP R/3: Installation and Configuration Guide 9

10 Sample Configuration resource.instname + resource.instid str VProLogLevel = INFO str ActivationKey str SAPSID str InstName str InstID str SAPAdmin str MonitorProgram str ProcMon = "dw ms co se" int SecondLevelMonitor str EnvFile int Version ) 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 sapci_sapci ( VProLogLevel = INFO SAPSID = PRD InstName = DVEBMGS InstID = 05 SAPAdmin = prdadm MonitorProgram = "/path/to/monitorprog" ProcMon = "dw ms co se" SecondLevelMonitor = 1 EnvFile = "/bin/true" Version = 4 ActivationKey = A ) Sample Service Group Configuration Figure 1 is an example service group that would support a SAP R/3 Central Instance. SAP CI Share(s) IP Mount(s) NFS NIC Disk Group VCS Agent for SAP R/3: Installation and Configuration Guide 10

11 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. Insure that usernames and groups exist on all nodes of the cluster. 2. Insure that /etc/services entries are duplicated on all nodes in the cluster. 3. Insure that UIDs and GUIs are synchronized on all nodes in the cluster. 4. 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. Insure that the home directory of the SAPAdmin user is on shared storage or is copied to all servers. 6. In the following files, change all hostname dependencies to the virtual hostname of the database server. (This location may change if you are running a newer version of Oracle.) /oracle/sapsid/817_64/network/admin/listener.ora /oracle/sapid/817_64/network/admin/tnsnames.ora 7. Edit /sapmnt/sapsid/profile/default.pfl and change the following items: Set SAPDBHOST to the virtual hostname of the database server Replace all instances of the physical CI hostname with the virtual name 8. Rename /sapmnt/sapsid/profile/sapsid_dvebmgsinstid_installedhostname to /sapmnt/sapsid/profile/sapsid_dvebmgsinstid_virtualhostname and edit the file to change the following items: Add SAPGLOBALHOST = virtualhostname Add SAPLOCALHOST = virtualhostname Add SAPLOCALHOSTFULL = virtualhostname 9. Rename /sapmnt/sapsid/profile/start_dvebmgsinstid_installedhostname to /sapmnt/sapsid/profile/start_dvebmgsinstid_virtualhostname and edit the file to change any physical hostnames to virtual hostnames. Configuring SAP R/3 Dialog Instance to Support Clustering The following configurations are required for a dialog instance to run properly within the cluster: 1. Insure that /etc/services entries are duplicated on all nodes in the cluster. VCS Agent for SAP R/3: Installation and Configuration Guide 11

12 2. 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. Insure that the home directory of the SAPAdmin user is on shared storage or is copied to all servers 4. In the following file, change all hostname dependencies to the virtual hostname of the database server (This location may change if you are running a newer version of Oracle). /oracle/sapid/817_64/network/admin/tnsnames.ora 5. Rename /sapmnt/sapsid/profile/sapsid_dinstid_installedhostname to /sapmnt/sapsid/profile/sapsid_dinstid_virtualhostname and edit the file to change the following items: Add SAPGLOBALHOST = virtualhostname of central instance Add SAPLOCALHOST = virtualhostname Add SAPLOCALHOSTFULL = virtualhostname 6. Rename /sapmnt/sapsid/profile/start_dinstid_installedhostname to /sapmnt/sapsid/profile/start_dinstid_virtualhostname and edit the file to change any physical hostnames to virtual hostnames. Removing the Agent Software Follow the steps below to remove the SAP R/3 agent from VCS. These steps must be performed while the cluster is started. 1. Remove all resources from the cluster that use the SAP R/3 agent. 2. Set the VCS 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 VCS 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 agent s type file will not be removed. # hatype -delete VProSAP 4. Set the VCS 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 VCS agent. # pkgrm VRTSsap VCS Agent for SAP R/3: Installation and Configuration Guide 12