Cluster Server 7.4.2 Configuration Guide for SAP Web Application Server - Windows
- Section I. Getting Started
- Introducing the Veritas High Availability Agent for SAP Web Application Server
- About the Veritas High Availability agent for SAP Web Application Server
- How does the Veritas High Availability solution work
- Agent functions
- Installing and configuring the SAP Web Application Server for high availability
- Setting up SAP systems for clustering
- Configuring the Enqueue Replication Server
- Clustering an SAP instance
- Introducing the Veritas High Availability Agent for SAP Web Application Server
- Section II. Configuring the application for high availability
- Section III. Troubleshooting the Agent
- Troubleshooting the agent for SAP Web Application Server
- Troubleshooting common problems
- Reviewing SAP Web Application Server agent log files
- Reviewing error log files
- Troubleshooting the agent for SAP Web Application Server
- Appendix A. Sample Configurations
Configuring all other nodes in the cluster
Perform the following tasks on the other remaining cluster nodes:
Create the required SAP users and groups.
Set the system and user environment for the SAP system.
Enter the required port numbers in the Windows services files.
Install Host Agent using sapinst.exe.
Create the Windows service for the SAP instance.
To configure all other nodes in the cluster
- Log in as a domain administrator.
- Create the following local groups.
SAP_SAPSID_LocalAdmin
SAP_SAP_LocalAdmin
SAP_LocalAdmin
- Add the SAP_SAPSID_GlobalAdmin domain group to the SAP_SAPSID_LocalAdmin and SAP_LocalAdmin group.
- Add the SAP_SAP_GlobalAdmin domain group to the SAP_SAP_LocalAdmin and SAP_LocalAdmin
- Add the SAP_SAPSID_GlobalAdmin and SAP_SAP_GlobalAdmin domain group to the local Administrators group.
For details on creating and adding a new local group and users:
- Click Start > Programs > Administrative Tools > Local Security Policy > Local Policies > User Right Assignment.
- Add the following privileges for the sapsidadm user.
Act as a part of the Operating System (SeTcbPrivilege)
Replace a process-level token (SeAssignPrimaryTokenPrivilege)
Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)
- Add the following privileges for the SAPServiceSAPSID user.
Log on as a Service (SeServiceLogonRight).
Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)
Access this computer from the network (SeNetworkLogonRight)
Deny Log on Locally and Deny Log on through Terminal Services (SeDenyInteractiveLogOnRight)
- Change the sapsidadm user environment as follows:
At the command prompt enter,
runas /profile /user:domain\sapsidadm regedit
On the Registry Editor panel, click HKEY_CURRENT_USER > Environment.
Modify the user environment based on your Database, SAP Usage Type and SAPSID.
For example, the following table depicts the registry environment with Oracle database (PI1) and Add-In installation with SAPSID PI1.
Name
Type
Data
Default
REG_SZ
value not set
DBMS_TYPE
REG_SZ
ora
dbs_ora_schema
REG_SZ
SAPSR3
dbs_ora_tnsname
REG_SZ
PI1
JAVA_HOME
REG_SZ
C:\j2sdk1.4.2_19-x64
NLS_LANG
REG_SZ
AMERICAN_AMERICA.UTF8
ORACLE_HOME
REG_EXPAND_SZ
E:\oracle\PI1\102
ORACLE_SID
REG_EXPAND_SZ
PI1
PATH
REG_EXPAND_SZ
E:\usr\sap\PI1\SYS\exe\uc\NTAMD64;\
\sappi1scs\sapmnt\PI1\SYS\exe\uc\NTAMD64;
E:\oracle\PI1\102\BIN
SAPDATA_HOME
REG_EXPAND_SZ
E:\oracle\PI1
SAPEXE
REG_SZ
\\sapi1scs\sapmnt\PI1\SYS\exe\uc\NTAMD64
SAPLOCALHOST
REG_SZ
sappi1aas
SAPSYSTEMNAME
REG_SZ
PI1
TEMP
REG_EXPAND_SZ
E:\usr\sap\PI1\tmp
TMP
REG_EXPAND_SZ
E:\usr\sap\PI1\tmp
TNS_ADMIN
REG_EXPAND_SZ
\\sappi1scs\sapmnt\PI1\SYS\profile\oracle
- From the first node in the cluster, copy the following service entries for the SAP instance, from the services file in the %windir%\system32\drivers\etc directory to the corresponding services file on all other nodes in the cluster.
sapdp<No.> 32<No.>/tcp # SAP System Dispatcher Port sapdp<No.>s 47<No.>/tcp # SAP System Dispatcher Security Port sapgw<No.> 33<No.>/tcp # SAP System Gateway Port sapgw<No.>s 48<No.>/tcp # SAP System Gateway Security Port sapms<SAPSID> 36<No.>/tcp # SAP System Message Port Number
where,
The value for <No.> is the value of an Instance ID.
- Move the Service Group from the first node to the node that you are currently configuring and ensure that the drive:\usr\sap directory is shared with the names, sapmnt and saploc.
- Install SAP Host Agent with SAPInst. Follow the steps below to install the SAP Host agent.
In the Master DVD, navigate to the directory containing the sapinst.exe tool.
Double-click the sapinst.exe file to launch the SAP installation GUI.
Select High Availability System > Based on [AS ABAP/AS Java/AS ABAP and AS Java] > Host Agent based on the usage type of system you installed.
Follow the instructions to complete the installation.
- Create the SAPSAPSID_No service as follows:
At the command prompt, navigate to the drive:\usr\sap\SAPSID\InstName\exe directory.
Run the sapstartsrv.exe command.
In the SAP Service Install/Uninstall dialog box, enter the following values:
SID
SAPSID
NR
InstanceNumber
Profile
If, SAPLOCALHOST=SAPGLOBALHOST, then enter the value as:
drive:\usr\sap\SAPSID \SYS\profile\SAPSID_InstName _VirtualHostName
If, SAPLOCALHOST is not equal to SAPGLOBALHOST, then enter the value as:
\\SAPGLOBALHOST\sapmnt\SAPSID \SYS\profile\SAPSID_InstName _VirtualHostName
User
domain\SAPServiceSAPSID
Password
SAPServiceSAPSID password
Startup type
manual
Use Environment of User
domain\sapsidadm
- Click OK.
- Re-register the type library as follows:
At the command prompt, navigate to the Drive:\Path\SAP\hostctrl\exe directory.
Run the sapstartsrv.exe command.
In the SAP Service Install/Uninstall dialog box, select Register COM Typelibrary Only in the Operation field
Click OK.
- Create registry entries for the SAPSAPSID_No service.
For example,
Name
Type
Data
Default
REG_SZ
value not set
EventMessageFile
REG_SZ
\\sappi1scs\sapmnt\PI1\SYS\exe\
uc\NTAMD64\sapevents.dll
TypesSupported
REG_DWORD
0x00000007(7)
- If an SAP Microsoft Management Console (MMC) is not configured on the node, register the SAP MMC using the following steps:
Access the file sapmmcX64u.msi or sapmmcIA64u.msi from Kernel Install DVD depending on the OS architecture.
Install SAP MMC by executing the msi package.
Note:
Veritas recommends that you cluster the SAP Central Services instances for both ABAP and Java in an Add-In Usage Type in the same service group.
Also, cluster the Enqueue Replication servers for both ABAP and Java in an Add-In Usage Type in a single Service Group.