SAP WAS Component Status Test

To quickly identify applications and critical SAP services that stopped suddenly or are in a Critical state, administrators need to closely track the health and operational state of every application and service on SAP WAS. For this purpose, administrators can use the SAP WAS Component Status test. This test automatically discovers the applications and services on a target SAP WAS, and reports the current health and operational state of each application and service. This way, the test promptly alerts administrators if any application/service is not running or switches to a Critical state suddenly, and thus enables administrators to swiftly initiate corrective measures.

Target of the test : A SAP Netweaver Application Server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the ICM and each of the server processes in a target Java instance.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed

Host

Specify the server for which the test is to be configured.

Port

The port number at which the specified server listens.

WSDL Port

This test uses the SAPControl web service to pull metrics on application and service status. To enable the test to communicate with the web service, you need to configure the test with the port number of the web service. Therefore, specify the port number of the SAPControl web service against WSDL Port. To determine the exact port number of the SAPControl web service, you can look up the etc/services file on the SAP WAS being monitored. If the port number is not declared in the etc/services file, you can specify the default port number of the web service against WSDL Port. If the web service is not SSL-enabled, then the default port number of the web service will be: 5<NR>13. Similarly, if the web service is SSL-enabled, then the default port number of the web service will be: 5<NR>14. <NR> in the port number refers to the system number of the SAP server being monitored. The system number is an indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the system number will be ‘00’. Similarly, if the SAP server port is 3201, the system number will have to be specified as ‘01’. Accordingly, the default port number of an SSL-enabled SAPControl web service will be 50014 , if the system number is 00, or 50114, if the system number is 01.

OS Username and OS Password

To enable the test to access the SAPControl web service and determine component state, you need to configure the OS Username and OS Password parameters of the test with the credentials (i.e., name and password) of an OS user, who fulfills one of the following conditions:

  • The name of the OS user should be declared using the service\admin_users profile parameter; (OR)
  • The name of the user group to which the OS user belongs should be declared using the service\admin_groups profile parameter; (OR)
  • The OS user should have the permission to execute the sapstartsrv executable

Confirm Password

Confirm the OS Password by retyping it here.

Startup Mode

Startup modes determine how your application is started on the J2EE Engine. By default, this test monitors only those applications that automatically start whenever the J2EE engine is restarted – i.e., those applications for which the Startup mode is set to Always. This is why, this flag is set to Always by default. Alternatively, you can set this flag to Manual. In this case, the test will monitor only those applications for which the Startup Mode is set to Manual – i.e., all applications that will require a manual start whenever the J2EE engine is restarted. You can also set this flag to Lazy, so that the test monitors only those applications for which the Startup Mode is set to Lazy. These are applications that will be stopped upon restart of the J2EE engine, and which will start only when another application requests a resource from it. 

Include Apps/Services

Provide a comma-separated list of applications and/or services that you want the test to monitor. Note that you can provide the whole/part of an application/service name here. When providing the complete application/service name, make sure that the exact application/service name is provided here. If a part of an application/service name is provided, then all applications and services that embed that string will be monitored.

Exclude Apps/Services

Provide a comma-separated list of applications and/or services that you want the test to exclude from monitoring. Note that you can provide the whole/part of an application/service name here. When providing the complete application/service name, make sure that the exact application/service name is provided here. If a part of an application/service name is provided, then all applications and services that embed that string will be excluded from monitoring.

SSL

Set this flag to Yes, if the SAPControl web service is SSL-enabled. Set this flag to No, if the SAPControl web service is not SSL-enabled.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Health

Indicates the current health of this application/service.

 

The values that this measure can report and their corresponding numeric values are discussed in the table below:

Measure Value Numeric Value
Normal 1
Critical 2
Error 3
Offline 4

Note:

By default, the test reports the Measure Values in the table above to indicate application/service state. In the graph of this measure however, the same is represented using the numeric equivalents only.

You can use the detailed diagnosis of the measure to determine the startup mode of each application/service.

Status

Indicates the current operational status of this application/service.

 

The values that this measure can report and their corresponding numeric values are discussed in the table below:

Measure Value Numeric Value
Running 1
Stopped 2

Note:

By default, the test reports the Measure Values in the table above to indicate operational status. In the graph of this measure however, the same is represented using the numeric equivalents only.

Expected status

Indicates the expected status of this application/service.

 

The values that this measure can report and their corresponding numeric values are discussed in the table below:

Measure Value Numeric Value
Running 1
Stopped 2

Note:

By default, the test reports the Measure Values in the table above to indicate expected status. In the graph of this measure however, the same is represented using the numeric equivalents only.