SAP WebAS agent attributes


SAP WebAS agent attributes
Prev	Configuring the agent for SAP WebAS	Next

Table: Required attributes shows the required attributes for configuring a SAP WebAS instance.

Note:

In a virtual environment, all the required attributes are discovered by the Symantec High Availability Configuration wizard.

Table: Required attributes

Required attributes

Description

EnqSrvResName

The name of the VCS resource for SAP Central Services (A)SCS Instance. This attribute is used by Enqueue and Enqueue Replication Server. Using this attribute the Enqueue server queries the Enqueue Replication Server resource state while determining the fail over target and vice a versa.

Type and dimension: string-scalar

Default: ""

Example: SAP71-PI1SCS_sap

EnvFile

The absolute path to the file that must be sourced with the UNIX shell. You must source this file to set the environment before executing SAP scripts for online, offline, monitor, and clean operations.

Supported shell environments are ksh, sh, and csh.

Note:

Ensure that the syntax of this file is in accordance with the user shell that the SAPAdmin attribute specifies. Review the information on how to generate environments file for SAP.

Symantec recommends that you store this file on shared disk so that the file is always available to an online system.

Type and dimension: string-scalar

Default: ""

Example: /usr/sap/PI1/DVEBMGS00/sappi1.env

InstType

An identifier that classifies and describes the SAP server instance type. Valid values are:

APPSERV: SAP Application Server
ENQUEUE: SAP Central Services
EBQREP: Enqueue Replication Server
SMDAGENT: Solution Manager Diagnostics Agent

Note:

The value of this attribute is not case-sensitive.

Type and dimension: string-scalar

Default: APPSERV

Example: ENQUEUE

ProcMon

The list of SAP processes to monitor. The entries in this list are separated using space and can be specified in any order. Review the information about how the monitor operation uses this attribute:

Type and dimension: string-scalar

Default: ""

Example: dw se jstart

ResLogLevel

The logging detail performed by the agent for the resource. Valid values are:

ERROR: Only logs error messages.

WARN: Logs above plus warning messages.

INFO: Logs above plus informational messages.

TRACE: Logs above plus trace messages. TRACE is very verbose and should only be used during initial configuration or for troubleshooting and diagnostic operations.

Type and dimension: string-scalar

Default: INFO

Example: TRACE

SAPAdmin

SAP System administrator for SAPSID. This user name is usually a concatenation of the SAPSID attribute and the adm string 'sidadm'.

Storing SAPAdmin in system naming services is not supported, for example: NIS, NIS+ and LDAP servers. The agent functions use this user name to execute their respective core subroutines.

Type and dimension: string-scalar

Default: ""

Example: pi1adm

InstProfile

The full path to the SAP Instance profile.

The SAPSID is found in /usr/sap/SAPSID/SYS/profile directory. The value of the instance is SAPSID_InstName_hostname. The hostname must resolve into a valid IP address that is used to cluster the SAP instance.

Type and dimension: string-scalar

Default: ""

Example: /usr/sap/PI1/SYS/profile/PI1_DVEBMGS00_sappi1pas

Table: Optional attributes lists the optional attributes.

Table: Optional attributes

Optional attribute

Description

MonitorProgram

Absolute path name of an external, user-supplied monitor executable. Review the information about setting this attribute:

Type and dimension: string-scalar

Default: ""

Example 1: /usr/sap/PI1/DVEBMGS00/work/myMonitor.sh

Example 2: /usr/sap/PI1/DVEBMGS00/work/myMonitor.sh arg1 arg2

SecondLevelMonitor

Used to enable second-level monitoring. Second-level monitoring is a deeper, more thorough state check of the SAP instance. The numeric value specifies how often the monitoring routines must run. 0 means never run the second-level monitoring routines, 1 means run routines every monitor interval, 2 means run routines every second monitor interval, and so on.

Note:

Exercise caution while setting SecondLevelMonitor to large numbers. For example, if the MonitorInterval is set to 60 seconds and the SecondLevelMonitor is set to 100, then sapinfo is executed every 100 minutes, which may not be as often as intended. For maximum flexibility, no upper limit is defined for SecondLevelMonitor.

Type and dimension: integer-scalar

Example: 1

Default: 0

ContainerName

Non-global zone support for Solaris. Defines the name of the non-global zone.

For more details refer to Veritas Cluster Server User's Guide

Type and dimension: string-scalar

Default: " "

Example: sap710scs-zone

ContainerInfo

Non-global zone support for VCS 5.1 on Solaris. Determines if you can use the service group with the container.

Assign the following values to the ContainerInfo attribute:

Name: The name of the container. For example, sap710scs-zone
Type: The type of container. Set this to Zone.
Enabled: If you want to enable the container, specify the value as 1, else specify it as 0.

For more details refer to Veritas Cluster Server Administrator's Guide

Type and dimension: string-association

Default: " "

Example: {Name = sap710scs-zone, Type = Zone, Enabled = 1}

Prev	Up	Next
Importing the agent types files in a VCS environment	Home	Setting the SecondLevelMonitor attribute