1.1.1 Managing Performance Information in a Java EE Environment

Execution environment

Linking is available by installing Agent of this product into the environment in which the application server function of the Interstage Application Server V10.0 and after is installed.

Refer to "Installation types corresponding to management types" in the Technical Guide for information about the relationship with supported installation types.

Note

If the multi-server operation of Interstage Application Server is performed, only the management server will be a monitoring target.

Tasks to perform on the Interstage Application Server side

Before creating and applying collection policies, the following preparations and checks are required on the Interstage Application Server side.

Each Interstage service/daemon must be running.
The JMX services or daemons must be running.
Monitoring level must be set for each IJServer cluster of the monitoring target
Set monitoring level to monitoring target performance information by using set sub-command of asadmin command.
Setting method of monitoring level when IJServer cluster name is [IJServer001] is shown below.
1. Collecting default performance information (Refer to "Definition procedure".)
```
asadmin set IJServer001.monitoring-service.module-monitoring-levels.jvm=LOW
asadmin set IJServer001.monitoring-service.module-monitoring-levels.jdbc-connection-pool=HIGH
asadmin set IJServer001.monitoring-service.module-monitoring-levels.thread-pool=LOW
asadmin set IJServer001.monitoring-service.module-monitoring-levels.transaction-service=LOW
```
2. Collecting performance information other than default. (Refer to "Procedure for extending monitoring items".)
  Adding to step 1, set following information.
```
asadmin set IJServer001.monitoring-service.module-monitoring-levels.ejb-container=LOW
asadmin set IJServer001.monitoring-service.module-monitoring-levels.orb=LOW
asadmin set IJServer001.monitoring-service.module-monitoring-levels.http-service=LOW
asadmin set IJServer001.monitoring-service.module-monitoring-levels.connector-connection-pool=HIGH
```
Above-mentioned setting is set in each observed IJServer cluster.
Refer to Reference Manual (Command) of the Interstage Application Server for detailed information about asadmin command.
To perform "Transaction Breakdown Analysis" of the IJServer cluster, make sure the setup described in "1.1.3 Transaction breakdown analysis" has been done.

Note

The only connection protocol to JMX services is the RMI protocol (JNDI format).

1.1.1.2 Definition method

Definition procedure

By implementing the following definition procedure, the records that can be collected for each Server Instance under an IJServer cluster are as follows:

IS_JMX_JAVAEE_JVM
IS_JMX_JAVAEE_JDBC_POOL
IS_JMX_JAVAEE_THREAD_POOL
IS_JMX_JAVAEE_TRANSACTION

Each item is collected per Server Instance under IJServer cluster.

Modify the collection template (template.dat).

Definition location

[Windows]

<Variable file storage directory>\control\template.dat

[UNIX]

/etc/opt/FJSVssqc/template.dat

Modify the [ISJMXSNSR] section.

Content to be modified

Modify the lines indicated by a star (*) as required.

#########################################

# Interstage Application Server JMX Sensor Information

[ISJMXSNSR]

DCAID="ISJMXSNSR"

PORT="8686" *Set the port number of the JMX service to be connected.

USER="" *Set the user name to be connected to the JMX service.

PASSWORD="" *Set the password of the user to be connected to the JMX service.

JAVA_HOME="" *Set Java bin directory used for connecting to JMX service

#########################################

Setting values

Key	Mandatory/optional	Format	Description	Default value
DCAID	Mandatory	ISJMXSNSR	Fixed as "ISJMXSNSR"	ISJMXSNSR
PORT	Mandatory	Port number (1 to 65535)	Specify a port number for connecting to JMX services using the RMI protocol (only supports JNDI format).	8686 (Default port number of Interstage DAS service)
USER	Mandatory	(*1)	Specify a user name for connecting to JMX services.	None
PASSWORD	Mandatory	String created using genpwd (1) (2)	Encrypt and specify a password for connecting to JMX services.	None
JAVA_HOME	[Windows] Optional (3) [UNIX] Mandatory (4)	Full path of JAVA bin directory	Specify a java path to be used for connecting to JMX services. This is not required if the operating system has a path for java.	None

*1: Refer to an Interstage Application Server manual for details on the user names and passwords used in a Java EE operating environment.

*2: Refer to "A.6 genpwd (Password Encryption Command)" for information on how to use genpwd (password encryption command).

*3: This is unnecessary when either of the following path is set to the head of environment variable PATH of the system. If both of them not specified, set either one of them.

- <Interstage Application Server installation directory>\JDK6\bin

- <Interstage Application Server installation directory>\JDK5\bin

*4: Specify one of the following

- /opt/FJSVawjbk/jdk6/bin

- /opt/FJSVawjbk/jdk5/bin

Definition example

#########################################

# Interstage Application Server JMX Sensor Information

[ISJMXSNSR]

DCAID="ISJMXSNSR"

PORT="8686"

USER="isadmin"

PASSWORD="xPtrcsgttd1325523sf"

JAVA_HOME="/opt/FJSVawjbk/jdk6/bin"

#########################################

Modify the [ATTR::AP] section.
Content to be modified
Add "ISJMXSNSR" to the GROUP key.
[Before modification]
[ATTR::AP]
GROUP="XXXX,YYYY"
[After modification]
[ATTR::AP]
GROUP="XXXX,YYYY,ISJMXSNSR"

Procedure for extending monitoring items

By implementing the following procedure for extending monitoring items, the following records will be able to be collected:.

IS_JMX_JAVAEE_MSGDRIVEN_BEAN
IS_JMX_JAVAEE_ORB_CONNECTION
IS_JMX_JAVAEE_CONNECTION_QUEUE
IS_JMX_JAVAEE_CONNECTOR_POOL
IS_JMX_JAVAEE_HTTP_LISTENER
IS_JMX_JAVAEE_ENTITY_BEAN
IS_JMX_JAVAEE_STATEFUL_SESSION
IS_JMX_JAVAEE_STATELESS_SESSION

Note

There is records cannot be collected depends on the application that operates under the IJServer Cluster.

Point

When it meets the requirement with items collected by default, the following procedures need not be executed.

Modify "template.dat" explained in "Definition procedure" given above.

Content to be modified

Add the line indicated by the star (*).

#########################################

# Interstage Application Server JMX Sensor Information

[ISJMXSNSR]

DCAID="ISJMXSNSR"

PORT="8686"

USER=""

PASSWORD=""

JAVA_HOME=""

LEVEL=2 *

#########################################

Setting values

Key	Mandatory/optional	Format	Explanation	Default value
LEVEL	Optional	2	Specify if performance information other than the default is to be collected.	None

Definition example

#########################################

# Interstage Application Server JMX Sensor Information

[ISJMXSNSR]

DCAID="ISJMXSNSR"

PORT="8686"

USER="isadmin"

PASSWORD="xPtrcsgttd1325523sf"

JAVA_HOME="/opt/FJSVawjbk/jdk6/bin"

LEVEL=2

#########################################

1.1.1.3 Setup

Execute the sqcRPolicy and the sqcSetPolicy commands by referring to "A.1 Server Resource Information Collection Policy Creation Command" for details.

If the configuration is subsequently changed by adding or deleting IJServer cluster, the collection policy must be created and applied again.

Any collection policies that have been set up must be reflected to the Console. Use the Agent Setup window to get configuration information by referring to "Agents" in the User's Guide (Console Edition).

1.1.1.4 Display

Performance information in a Java EE environment with Interstage Application Server can be displayed by following methods.

Summary: This can be displayed by selecting "Interstage(IJServer Cluster)" node (Interstage(IJServerCluster)Monitor) of the Summary Tree.

Details

This can be displayed by selecting each detailed display item under "<Server Instance Name>" node of the "IJServer (Cluster)" node of the Detailed Tree.

The detailed display items are as shown in the table below. Each detailed display item can display information by filtering it by resource.

Detailed display items	Expansion	Resource ID
JVM		Instance name
JDBCResource		Instance name : JDBC connection pool name
ThreadPool		Instance name : thread pool name
Transaction		Instance name
MsgDrivenBean	Yes	Instance name : EJB module name : MessageDrivenBean name : Application name Instance name : MessageDrivenBean name : Application name
ORBConnection	Yes	Instance name : Connection manager name
ConnectionQueue	Yes	Instance name
ConnectorPool	Yes	Instance name : Connector connection pool name
HttpListener	Yes	Instance name : Virtual server name : HTTP listener name
EntityBean	Yes	Instance name : EJB module name : EntityBean name : Application name Instance name : EntityBean name : Application name
StflSessionBeans	Yes	Instance name : EJB module name : StatefulSessionBean name : Application name Instance name : StatefulSessionBean name : Application name
StlsSessionBeans	Yes	Instance name : EJB module name : StatelessSessionBean name : Application name Instance name : StatelessSessionBean name : Application name

Note1: Instance name is displayed in "IJServer Cluster Name : Server Instance Name" format.

Note2: Items with "Yes" in the Expansion column will be displayed if "Procedure for extending monitoring items" has been implemented.

Refer to "Resources" in the User's Guide (Console edition) for method of specifying resource.

Report

Interstage Application Server (IJServer Cluster)
Generic report