J2EE Configuration Syntax

The J2EE Configuration is used to configure monitoring of the J2EE environment.

SUBSYS J2EE

MONITOR LOCALAPPSERVER  (<port>[:<servlet-alias>][:<process_name>])
MONITOR REMOTEAPPSERVER (<monitoring-node>, <was-node-alias>, <ip>:<port>[:<servlet-alias>][:<process_name>])
MONITOR ENT-APPLICATION (<entapp-name>[, <entapp-name> ..])
EXCLUDE ENT-APPLICATION (<entapp-name>[, <entapp-name> ..])
DEFINE SERVLET-RESPONSE (<ent-app-name>, <web-app-name>, <servlet-name>, <good-response-time>, <ok-response-time>, <bad-response-time>)

Syntax Elements

MONITOR LOCALAPPSERVER

Defines which local Web Application Servers (WAS) are to be monitored.

<port>

The port that the Web Application Server is running on

<servlet-alias>

This allows you to choose a custom name for the Monitoring Servlet. This might be used to avoid a servlet name conflict with an existing servlet, or to distinguish between two concurrently running instances of the Monitoring Servlet on the same node. Note: For HPE NonStop, this name must NOT start with '$'. Default: irwasmon.

<process_name>

(HPE NonStop) The TCP/IP connections process name, starting with '$'. This field will be ignored on Windows and UNIX.

Example:

SUBSYS J2EE

MONITOR LOCALAPPSERVER (7001)
MONITOR LOCALAPPSERVER (9080:irwasmon1)

MONITOR REMOTEAPPSERVER

Defines a remote Web Application Server (WAS) to monitor.

<monitoring-node>

The node which is to do the monitoring.

<was-node-alias>

An alias name given to the remote node.

<ip>:<port>

The IP address and Port number of the remote Web Application Server.

<servlet-alias>

An alias name given to the servlet. Note that for HPE NonStop the name must NOT start with '$'. Default: irwasmon.

<process_name>

(HPE NonStop) The TCP/IP connections process name, starting with '$'. This field will be ignored on Windows and UNIX.

Example:

SUBSYS J2EE

MONITOR REMOTEAPPSERVER (\my-node, \was-node, 10.1.2.3:9000)

MONITOR ENT-APPLICATION

A 'white list' of Enterprise Applications to be monitored. If this is not defined then all Enterprise Applications, except those listed in the EXCLUDEENTAPP, will be monitored.

<entapp-name>

Name of the Enterprise Application to monitor.

Example:

SUBSYS J2EE

MONITOR ENT-APPLICATION (MyEntApp1, MyEntApp2)

EXCLUDE ENT-APPLICATION

A 'black list' of Enterprise Applications not to be monitored.

<entapp-name>

Name of the Enterprise Application to monitor.

Example:

SUBSYS J2EE

EXCLUDE ENT-APPLICATION (testapp)

DEFINE SERVLET-RESPONSE

This parameter sets the values used for classifying response time (in seconds) of servlets. If this parameter is not defined then the response of all servlets will be classified using the default settings of:

good response time        0.1 sec

ok response time            0.2 sec

bad response time          0.3 sec

<ent-app-name>

Name of the Enterprise Application. Use blank for wildcard matching.

<web-app-name>

Name of the Web Application. Use blank for wildcard matching.

<servlet-name>

Servlet Name. Use blank for wildcard matching.

<good-response-time>

If a response time is less than or equal to this value in seconds, then the transaction is counted as 'good'.

<ok-response-time>

If a response time is greater than good-response-time and less than or equal to ok-response-time then the transaction is counted as 'ok'.

<bad-response-time>

If a response time is greater than <ok-response-time> and less than or equal to <bad-response-time> then the transaction is counted as 'slow'. If a response time is greater than <bad-response-time> then the transaction is counted as 'bad'.

SERVLET-RESPONSE Wildcard Rules

1.   A lower level wildcard must be applied before it can be applied to the next level in the servlet hierarchy. For instance, the following can be configured:

DEFINE SERVLET-RESPONSE (examplesEntApp,,, 0.5, 1, 2)
DEFINE SERVLET-RESPONSE (examplesEntApp,examplesWebApp,, 0.5, 1, 2)
DEFINE SERVLET-RESPONSE (,,, 0.5, 1, 2)

But not...

DEFINE SERVLET-RESPONSE (,examplesWebApp,, 0.5, 1, 2)
DEFINE SERVLET-RESPONSE (,,SessionServlet, 0.5, 1, 2)

2.   In the case of multiple configuration lines, values for more specific ent-app/web-app and servlet names will override wildcards. For example, consider the following configuration:

DEFINE SERVLET-RESPONSE (examplesEntApp, examplesWebApp, SessionServlet, 0.5, 1, 2)
DEFINE SERVLET-RESPONSE (examplesEntApp, *, *, 1, 2, 3)

In the above configuration, response time values 1, 2 and 3 will be applicable to all servlets that belong to examplesEntApp except for SessionServlet under examplesWebApp for which response time values would be 0.5, 1 and 2.

Default SERVLET-RESPONSE Time Settings

By default, irwasmon will gather servlet response time information every two seconds, therefore it is important to verify that the response time of the irwasmon DataServlet is under two seconds.

There are several factors that affect the time it takes for the irwasmon DataServlet to execute, so it may be necessary to change the frequency at which irwasmon DataServlet is run. To change the DataServlet execution frequency, edit the 'UpdIntv' value in the 'Servlets' section of the irebcol.ini file, then change the response time values for DataServlet in this file. The Prognosis service will need to be restarted to make these changes take effect. This will need to be done on each Monitoring Server.

Examples:

DEFINE SERVLET-RESPONSE (examplesEntApp, examplesWebApp, DataServlet, 0.5, 1, 2)
DEFINE SERVLET-RESPONSE (examplesEntApp, examplesWebApp,, 1, 2, 3)
DEFINE SERVLET-RESPONSE (examplesEntApp,,, 1, 3, 5)
DEFINE SERVLET-RESPONSE (,,, 0.5, 0.75, 1)
Provide feedback on this article