Please enter search query.
Search <book_title>...
Cluster Server 7.3.1 Configuration Guide for SAP Web Application Server - Windows
Last Published:
2017-11-05
Product(s):
InfoScale & Storage Foundation (7.3.1)
- 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 application availability is achieved in a physical environment
- How does the Veritas High Availability solution work
- Agent functions
- Agent attributes for SAP Web Application Server
- Installing the agent for SAP Web Application Server
- Installing and configuring the SAP Web Application Server for high availability
- Monitoring an SAP instance
- About installing SAP Web Application Server for high availability
- About configuring SAP Web Application Server for high availability
- Setting up SAP systems for clustering
- Installing SAP system using Virtual Hostname
- Configuring the agent for message server restart
- Configuring the Enqueue Replication Server
- Clustering an SAP instance
- Configuring the first node in the cluster
- Configuring all other nodes in the cluster
- Creating and adding domain groups and users
- Creating and adding local groups and users
- Creating and adding local groups and users
- Creating sapmnt and saploc share directories
- Configuring the first node in the cluster
- Configuring all other nodes in the cluster
- Creating and adding domain groups and users
- User accounts
- Groups
- Adding new domain groups and users
- Creating SAP system users, sapsidadm and SAPServiceSAPSID
- Adding the sapsidadm user to the SAP_SAPSID_GlobalAdmin Group
- To add the SAPServiceSAPSID user to the SAP_SAPSID_GlobalAdmin Group
- User accounts
- Groups
- Adding new domain groups and users
- Creating SAP system users, sapsidadm and SAPServiceSAPSID
- Adding the sapsidadm user to the SAP_SAPSID_GlobalAdmin Group
- To add the SAPServiceSAPSID user to the SAP_SAPSID_GlobalAdmin Group
- Creating and adding local groups and users
- Creating and adding local groups and users
- Creating sapmnt and saploc share directories
- Configuring the SAP systems on Windows Server 2008/2012
- 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
- Starting the SAP Web Application Server outside a cluster
- Troubleshooting common problems
- Unable to install the Veritas High Availability agent for SAP Web Application Server
- Unable to see an entry in the SAP MMC for an SAP instance
- The agent for SAP Web Application Server fails to bring online an SAP instance resource through VCS
- SAP instance does not come online, and the startsap.exe command exits with exit code -1
- In case of an Enqueue server failure, the Enqueue server instance fails to take over the lock table from the Enqueue Replication server instance
- The ensmon.exe command returns exit code 4 for a Enqueue server instance
- The return code of the ensmon.exe command is 8 for an Enqueue Replication server instance
- The Enqueue server instance does not fail over to the correct Enqueue Replication server instance
- In case of a resource fault, the Service Group does not fail over
- Unable to see an entry in the SAP MMC for an SAP instance
- The agent for SAP Web Application Server fails to bring online an SAP instance resource through VCS
- SAP instance does not come online, and the startsap.exe command exits with exit code -1
- In case of an Enqueue server failure, the Enqueue server instance fails to take over the lock table from the Enqueue Replication server instance
- The ensmon.exe command returns exit code 4 for a Enqueue server instance
- The return code of the ensmon.exe command is 8 for an Enqueue Replication server instance
- The Enqueue server instance does not fail over to the correct Enqueue Replication server instance
- In case of a resource fault, the Service Group does not fail over
- Reviewing SAP Web Application Server agent log files
- Reviewing error log files
- Checks for an SAP Add-In Usage Types
- Troubleshooting the agent for SAP Web Application Server
- Appendix A. Sample Configurations
- About the sample configuration for the agent for SAP Web Application Server
- Sample agent type definition for SAP WebAS
- Sample SAP resource configuration in a physical environment
- Sample SAP primary application server instance
- Sample SAP additional application server instance
- Sample SAP Central Services instance
- Sample SAP Enqueue Replication server instance
- Sample SAP primary application server instance
- Sample SAP additional application server instance
- Sample SAP Central Services instance
- Sample SAP Enqueue Replication server instance
- Sample service group configurations in a physical environment
- Sample service group configuration for ABAP and Java Usage types
- Sample service group configurations for SAP systems on Windows Server 2008/2012
- Sample configuration for SAP Central Services Instances service group for Add-In installation Usage Type
- Sample resource dependency for SAP Central Services Instances service group for Add-In installation usage type
- Sample configuration for SAP Enqueue Replication Server Instances service group for Add-In installation Usage Type
- Sample resource dependency for SAP Enqueue Replication Server Instances service group for Add-In installation Usage Type
- Sample configuration for SAP Central Services Instances service group for Add-In installation Usage Type
- Sample resource dependency for SAP Central Services Instances service group for Add-In installation usage type
- Sample configuration for SAP Enqueue Replication Server Instances service group for Add-In installation Usage Type
- Sample resource dependency for SAP Enqueue Replication Server Instances service group for Add-In installation Usage Type
- Sample service group dependency for SAP Web Application Server
- Sample configuration in a virtual environment
Sample configuration for SAP Central Services Instances service group for Add-In installation Usage Type
This section provides the VCS main.cf for SAP Central Services Instances service group for Add-In installation Usage Type.
group SAP-PI3SCS (
SystemList = { SysA = 0, SysB = 1 }
)
FileShare SAP-PI3SCS_sapmnt_FS (
PathName = "\\usr\\sap"
ShareName = sapmnt
LanmanResName = SAP-PI3SCS_Lanman
MountResName = SAP-PI3SCS_H_MountV
UserPermissions = { "'SAP_LocalAdmin'" = FULL_CONTROL,
"'Administrators'" = FULL_CONTROL,
"'SYMCORP\\SAP_PI3_GlobalAdmin'" = FULL_CONTROL,
"'SAP_PI3_LocalAdmin'" = FULL_CONTROL }
)
IP SAP-PI3SCS_IP (
Address = "10.xxx.xx.30"
SubNetMask = "255.255.252.0"
MACAddress = "00-15-17-63-45-92"
)
Lanman SAP-PI3SCS_Lanman (
VirtualName = sappi3scs
IPResName = SAP-PI3SCS_IP
)
MountV SAP-PI3ASCS_MountV (
MountPath = "I:\\usr\\sap\\PI3\\ASCS29"
VolumeName = PI3ASCS_vol
VMDGResName = SAP-PI3ASCS_VMDg
)
MountV SAP-PI3SCS_MountV (
MountPath = "I:\\usr\\sap\\PI3\\SCS30"
VolumeName = PI3SCS_vol
VMDGResName = SAP-PI3SCS_VMDg
)
MountV SAP-PI3SCS_I_MountV (
MountPath = "I:"
VolumeName = PI3SCS_I_vol
VMDGResName = SAP-PI3SCS_I_VMDg
)
MountV SAP-PI3SYS_MountV (
MountPath = "I:\\usr\\sap\\PI3\\SYS"
VolumeName = PI3SYS_vol
VMDGResName = SAP-PI3SYS_VMDg
)
NIC SAP-PI3SCS_NIC (
MACAddress = "00-15-17-63-45-92"
)
SAPWebAS SAP-PI3ASCS_SAPWebAS (
SAPSID = PI3
SAPHome = "I:\\usr\\sap\\PI3\\ASCS29\\exe"
SAPMonHome = "I:\\usr\\sap\\PI3\\ASCS29\\exe"
SAPHost = sappi3scs
ProcMon = { "msg_server.exe", "enserver.exe" }
SAPServiceUser = SAPServicePI3
SAPAdminDomain = SYMCORP
SAPAdmin = pi3adm
SAPAdminPassword = AFkl41nmqdaou
InstType = ENQUEUE
InstName = ASCS29
InstProfile = "I:\\usr\\sap\\PI3\\SYS\\profile\\PI3_ASCS29_sappi3scs"
)
SAPWebAS SAP-PI3SCS_SAPWebAS (
SAPSID = PI3
SAPHome = "I:\\usr\\sap\\PI3\\SCS30\\exe"
SAPMonHome = "I:\\usr\\sap\\PI3\\SCS30\\exe"
SAPHost = sappi3scs
ProcMon = { "msg_server.exe", "enserver.exe" }
SAPServiceUser = SAPServicePI3
SAPAdminDomain = SYMCORP
SAPAdmin = pi3adm
SAPAdminPassword = AFkl41nmqdaou
InstType = ENQUEUE
InstName = SCS30
InstProfile = "I:\\usr\\sap\\PI3\\SYS\\profile\\PI3_SCS30_sappi3scs"
)
VMDg SAP-PI3SCS_I_VMDg (
DiskGroupName = PI3SCS_I_dg
)
VMDg SAP-PI3ASCS_VMDg (
DiskGroupName = PI3ASCS_dg
)
VMDg SAP-PI3SCS_VMDg (
DiskGroupName = PI3SCS_dg
)
VMDg SAP-PI3SYS_VMDg (
DiskGroupName = PI3SYS_dg
)
SAP-PI3SCS_sapmnt_FS requires SAP-PI3SCS_Lanman
SAP-PI3SCS_sapmnt_FS requires SAP-PI3SCS_I_MountV
SAP-PI3SCS_IP requires SAP-PI3SCS_NIC
SAP-PI3SCS_Lanman requires SAP-PI3SCS_IP
SAP-PI3ASCS_MountV requires SAP-PI3SCS_I_MountV
SAP-PI3ASCS_MountV requires SAP-PI3ASCS_VMDg
SAP-PI3SCS_MountV requires SAP-PI3SCS_I_MountV
SAP-PI3SCS_MountV requires SAP-PI3SCS_VMDg
SAP-PI3SCS_I_MountV requires SAP-PI3SCS_I_VMDg
SAP-PI3SYS_MountV requires SAP-PI3SCS_I_MountV
SAP-PI3SYS_MountV requires SAP-PI3SYS_VMDg
SAP-PI3ASCS_SAPWebAS requires SAP-PI3SCS_sapmnt_FS
SAP-PI3ASCS_SAPWebAS requires SAP-PI3ASCS_MountV
SAP-PI3ASCS_SAPWebAS requires SAP-PI3SYS_MountV
SAP-PI3SCS_SAPWebAS requires SAP-PI3SCS_sapmnt_FS
SAP-PI3SCS_SAPWebAS requires SAP-PI3SCS_MountV
SAP-PI3SCS_SAPWebAS requires SAP-PI3SYS_MountV
// resource dependency tree
//
// group SAP-PI3SCS
// {
// SAPWebAS SAP-PI3ASCS_SAPWebAS
// {
// FileShare SAP-PI3SCS_sapmnt_FS
// {
// Lanman SAP-PI3SCS_Lanman
// {
// IP SAP-PI3SCS_IP
// {
// NIC SAP-PI3SCS_NIC
// }
// }
// MountV SAP-PI3SCS_I_MountV
// {
// VMDg SAP-PI3SCS_I_VMDg
// }
// }
// MountV SAP-PI3ASCS_MountV
// {
// MountV SAP-PI3SCS_I_MountV
// {
// VMDg SAP-PI3SCS_I_VMDg
// }
// VMDg SAP-PI3ASCS_VMDg
// }
// MountV SAP-PI3SYS_MountV
// {
// MountV SAP-PI3SCS_I_MountV
// {
// VMDg SAP-PI3SCS_I_VMDg
// }
// VMDg SAP-PI3SYS_VMDg
// }
// }
// SAPWebAS SAP-PI3SCS_SAPWebAS
// {
// FileShare SAP-PI3SCS_sapmnt_FS
// {
// Lanman SAP-PI3SCS_Lanman
// {
// IP SAP-PI3SCS_IP
// {
// NIC SAP-PI3SCS_NIC
// }
// }
// MountV SAP-PI3SCS_I_MountV
// {
// VMDg SAP-PI3SCS_I_VMDg
// }
// }
// MountV SAP-PI3SCS_MountV
// {
// MountV SAP-PI3SCS_I_MountV
// {
// VMDg SAP-PI3SCS_I_VMDg
// }
// VMDg SAP-PI3SCS_VMDg
// }
// MountV SAP-PI3SYS_MountV
// {
// MountV SAP-PI3SCS_I_MountV
// {
// VMDg SAP-PI3SCS_I_VMDg
// }
// VMDg SAP-PI3SYS_VMDg
// }
// }
// }