This section explains the procedures for managing the performance information in a J2EE environment.
Execution environment
Service Quality Coordinator can be linked to Interstage Application Server by installing this product's Agent in an environment where the application server function for Interstage Application Server has been installed.
Refer to "Installation types corresponding to management types" in the Technical Guide for information about the relationship with supported installation types.
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.
To manage the performance of EJB, TD and CORBA Work Units, a monitoring environment for performance analysis must be created (error messages must not be displayed when the ispstatus command is executed). (It is not required when managing the performance of IJServer Work Units.)
Note 1: Refer to the Interstage Application Server manuals for information about how to create a monitoring environment for performance analysis.
Note 2: Set the collection interval to 5 minutes.
Each Interstage service/daemon must be running.
If "transaction breakdown analysis" is performed for IJServer Work Units, the settings described in "1.1.3 Transaction breakdown analysis" must be made.
With the default settings, the records that can be collected for IJServer Work Units are as follows:
IS_JMX_JVM
IS_JMX_JTARESOURCE
IS_JMX_JDBCRESOURCE
By implementing the definition procedure below, the following records can also be collected:
IS_JMX_SERVLET
IS_JMX_ENTITYBEAN_METHOD
IS_JMX_ENTBEAN_POOL_AND_PASSIVATE
IS_JMX_STFBEAN_METHOD
IS_JMX_STFBEAN_INS_AND_IDLE
IS_JMX_STLSBEAN_METHOD
IS_JMX_MESSBEAN_METHOD
IS_JMX_MESSBEAN_INFO
Note
Some records cannot be collected, depending on the application running on the IJServer Work Unit.
The number of records that can be collected increases as a result of implementing this definition procedure, so collection processing may not be able to complete within the collection interval (because there are too many monitored objects, for example) and errors may occur.
Point
If the items that are collected by default meet the requirements for the operation, there is no need to implement the procedure in this section.
Procedure for extending performance information collection for IJServer
Modify the "template.dat" file.
[Windows]
<Variable file storage directory>\control\template.dat |
[UNIX]
/etc/opt/FJSVssqc/template.dat |
Content to be modified
Add the line "LEVEL=2" after the "ARMTXN=..." line in the INTSG section, as shown below.
######################################### ## Interstage ispreport DCA_CMD [INTSG] DCAID="INTSGREPO" AUTOFLAG="ON" INTERVAL=5 TDOBJ="ON" EJBAPL="ON" IMPLID="ON" IJSERVER="ON" ARMTXN="ON" LEVEL=2 *Add this line. ######################################### |
Execute the sqcRPolicy and the sqcSetPolicy commands by referring to "A.1 Server Resource Information Collection Policy Creation Command".
If the configuration is subsequently changed by adding or deleting Work Units, 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).
Performance information in a J2EE environment with Interstage Application Server can be displayed by following methods.
Performance information can be displayed by selecting "Interstage(IJServer)" node (Interstage(IJServer)Monitor) in the Summary tree.
Performance information can be displayed by selecting each detailed display item under the "Work Unit name" node of the "Interstage" node on the Detailed tree.
Interstage Application Server (Work Unit)
Generic report
