SAP WAS Beans Test

This test measures the efficiency with which the EJB Container Service manages the enterprise bean instances deployed on the server. The EJB Container provides all the services that are required by an EJB application, such as transaction and security management, clustering, persistence, network distribution of remote clients, scalable management of resources, and so on.

If too many EJBs have been deployed on the server, then managing the individual EJBs could become a cumbersome task. In such a case, you can use the eG administrative interface to group EJBs and manage the groups, instead. To create an EJB group, you will need to click on the Click here hyperlink displayed above the parameters of the SAP WAS Beans test. By default, eG Enterprise system monitors only those beans that are part of a group.

Target of the test : A SAP Netweaver Application Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every configured EJB group.

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.

UserName

This test connects to a specific SAP web application server instance, and extracts critical metrics from it. Therefore, in the UserName text box, provide a valid j2ee admin user name which the test should use for connecting to the server instance.

Password

Provide the Password that corresponds to the specified UserName.

Confirm Password

Confirm the OS Password by retyping it here.

InstanceName

Provide the name of the application server instance to which the test should connect. For example, if you specify tpp here, then the test will use the login credentials (UserName and Password) provided here to connect to an instance named TPP. To know the available server instances, use the instructions provided in Determining the Name of the SAP Web AS Instance.

ConnectorPort

This test uses the P4 protocol for connecting to the SAP web application server. Therefore, the port at which the P4 protocol listens needs to be specified as the ConnectorPort. To know how to determine the P4 port, use the procedure detailed in Determining the P4 Port.

DispatcherID

This test reports a set of metrics for the Java dispatcher that receives client requests. By default, the cluster ID  of the dispatcher is auto-discovered by the eG Enterprise. Therefore, default option is specified against this parameter. Alternately, if you wish to monitor a specific cluster ID, then you can mention that cluster ID against this parameter. To know the cluster ID of the dispatcher, follow the steps discussed in Determining the Name of the SAP Web AS Instance and P4 Protocol Port .

ServerIDs

Typically, the Java dispatcher or the ICM distributes the client requests it receives to the server processes executing on the Java component of the SAP Web AS for processing.  By default, the ServerIDs are auto-discovered by the eG Enterprise. To monitor specific server processes, specify a comma-separated list of the cluster IDs of these server processes in the ServerIDs text box. To know the cluster IDs of the server processes, follow the procedure detailed in Determining the Name of the SAP Web AS Instance and P4 Protocol Port.

Providing a comma-separated list of server process cluster IDs will ensure that these cluster IDs alone appear as the descriptors of the test. If need be, you can have server process name-cluster ID pairs appear as the test descriptors. To achieve this, the specification in the ServerIDs text box should be of the following format: Server process name:Cluster ID of the server process. For example, if the cluster ID of a server process named Server0 is 12621850, then you can specify the ServerID in the format: Server0:12621850.

Autodiscovery

By default, the eG Enterprise allows administrators to configure bean groups using the eG administrative interface, and reports metrics pertaining to every group so created. Accordingly, by default, Autodiscovery is set to No. If you want beans to be discovered and monitored automatically, then select the Yes option against Autodiscovery. When this is done, the eG agent automatically discovers all the beans on the SAP web application server, and reports one set of measures for every bean hosted on the server.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise 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

Bean creations

Indicates the number of times a bean has been created.

Number

The detailed diagnosis of this measure, if enabled, provides an individual bean-wise breakup of the current pool size, and the number of additions and removals.

Bean removals

Indicates the number of times a bean has been removed.

Number

 

Current pool size

Indicates the number of bean instances provided by this pool, which are currently used by the application or are stored in the pool.

Number

 

Bean activations

Indicates the number of times a bean instance has been activated since the last measurement period.

Number

 

Bean passivations

Indicates the number of times a bean instance has been passivated or deactivated since the last measurement period.

Number

 

Active sessions

Indicates the number of bean sessions that are currently active.

Number

 

Passive sessions

Indicates the number of bean sessions that are currently passive.

Number

 

Completed sessions

Indicates the number of bean sessions that have been completed since the last measurement period.

Number

 

Bean stores

Indicates the number of entity bean instances that were stored in the database since the last measurement period.

Number

 

Bean loads

Indicates the number of entity bean instances that were loaded to the EJB container from the database since the last measurement period.

Number