SAP Java Cluster Messages Test

AS Java cluster elements communicate via cluster messages. The system is able to send messages to one cluster element, to a group of elements, or to all elements in the cluster. Cluster elements use messages to broadcast notification events. The Cluster Manager is responsible for managing this communication. There are several types of cluster communication depending on the abilities they provide for transferring messages. The type of cluster communication that is used when processing one message is determined by the Cluster Manager and is transparent for the cluster elements. The successful message delivery is guaranteed, except in cases when the corresponding element stops or is timed out. In this case, the corresponding exception occurs and can be handled by the sending party. To figure out which cluster element had sent the maximum number of cluster messages and transferred the maximum amount of data, administrators can use the SAP Java Cluster Messages test.

For each Cluster element of the SAP Java System, this test reports the total messages and broadcast messages sent. The P2P messages and requests sent from each cluster element is also monitored and the cluster element that is sending the maximum number of such messages and requests are identified. The data transferred from each cluster element is monitored periodically and the cluster element that is transferring the maximum amount of data is identified.

Target of the test : A SAP JAVA System

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for each cluster element of the SAP JAVA System being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed

Host

Host name of the server for which the test is to be configured.

PortNo

Enter the port to which the specified host listens.

Central WSDL Port

In this text box, specify the port number of the SAPControl web service. To determine the exact port number of the SAPControl web service, you can look up the etc/services file on the SAP ABAP system 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 collect the required metrics, 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.

SSL

By default, this test uses the SAPControl web service for collecting measures. 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.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Total messages

Indicates the total messages sent by this cluster element during the last measurement period.

Number

Comparing the value of this measure across the cluster elements will reveal the cluster element that was sending the maximum amount of total messages.

Data transferred

Indicates the rate at which data was transferred from this cluster element during the last measurement period.

KB/min

Compare the value of this measure across the cluster elements to figure out the cluster element that had transferred the maximum amount of data.

Average message length

Indicates the average length of messages sent by this cluster element during the last measurement period.

KB

Use the detailed diagnosis of this measure to identify services performing large data transfers and downloads.

Messages

Indicates the rate at which messages were sent by this cluster element during the last measurement period.

Messages/min

 

P2P messages

Indicates the rate at which messages were sent from this cluster element to another during the last measurement period.

Messages/min

 

P2P requests

Indicates the rate at which message requests were sent from this cluster element to another during the last measurement period.

Messages/min

 

P2P replies

Indicates the rate of responses received by this cluster element from another cluster element during the last measurement period.

Messages/min

 

Broadcast messages

Indicates the rate at which messages were broadcasted from this cluster element to another cluster element during the last measurement period.

Messages/min

Broadcast messages and requests should be used appropriately as they have significant impact on overall cluster communication including critical P2P cluster communication traffic.

Broadcast requests

Indicates the rate at which requests were broadcasted from this cluster element to another cluster element during the last measurement period.

Messages/min