278 End-to-End e-business Transaction Management Made Easy
8.6 The J2EE component
The Java 2 Platform Enterprise Edition (J2EE) component of TMTP Version 5.2
is a component in IBM Tivoli Monitoring for Transaction Performance Version 5.2
that provides transaction decomposition capabilities for Java-based e-business
Performance and availability information will be captured from methods of J2EE
Enterprise Java Beans (Entity EJBs and Session EJBs)
JMS JDBC methods
The TMTP J2EE component supports WebSphere Application Server Enterprise
Edition Versions 4.0.3 and later, which are valid for the J2EE monitoring
component. Version 7.0.1 is the only supported version of BEA WebLogic.
More details about J2EE are available in 3.3.2, “J2EE instrumentation” on
8.6.1 J2EE component deployment
From a customization and deployment point of view the J2EE component is
treated just like STI and QoS. A Management Agent can be instrumented to
perform transaction performance measurements of this specific type of
transactions, and it will report the findings back to the TMTP Management Server
for further analysis and processing.
Use the following steps to deploy the J2EE component to an existing
1. Select System Administration
→ Work with Agents from the navigation
pane on the TMTP console.
2. Select the Management Agent to which the component is going to be
deployed, and choose Deploy J2EE Monitoring Component from the
drop-down menu above the list of endpoints, as shown in Figure 8-33 on
page 279. When ready, click Go to move on to configuring the specific
properties for the deployment through the Deploy Components and/or
Monitoring Component dialog, shown in Figure 8-34 on page 280.
Chapter 8. Measuring e-business transaction response times 279
Figure 8-33 Deploy J2EE and Work of agents
280 End-to-End e-business Transaction Management Made Easy
Figure 8-34 J2EE deployment and configuration for WAS 5.0.1
3. Select a specific make and model of application server that applies to your
environment. The Deploy Components and/or Monitoring Component is built
dynamically based upon the type of application server you select.
The values you are requested to supply are summarized in Table 8-2 on
page 281. Please consult the manual IBM Tivoli Monitoring for Transaction
Performance User’s Guide Version 5.2.0, SC32-1386 for more details on each
of the properties.
Chapter 8. Measuring e-business transaction response times 281
Table 8-2 J2EE components configuration properties
To define the properties for the deployment of the J2EE component to a
Management Agent installed on a WebSphere Application Server 5.01
system, specify properties like the ones shown in Figure 8-34 on page 280
and click OK to start the deployment. After a couple of minutes, the
Management Agent will be rebooted, and the J2EE component has been
Property Example value
Application Server Name Default Server
Application Server Home C:\WebSphere\AppServe
Java Home C:\WebSphere\AppServer\java
Node Name <YOUR MAs HOSTNAME>
Automatically Restart the
Application Server Name server1
Application Server Home C:\Progra~1\WebSphere\AppServer
Cell Name ibmtiv9
Node Name ibmtiv9
Automatically Restart the
Weblogic Version 7.0
Application Server Name petstoreServer
Application Server Home c:\bea\weblogic700
Java Home c:\bea\jdk131_03
A script starts this server Check in applicable
Node Manager starts this
Check in applicable
282 End-to-End e-business Transaction Management Made Easy
4. To verify the success of the deployment, refresh the Work with Agents dialog,
and verify that the status for the J2EE Component on the Management Agent
in question shows Running, as shown in Figure 8-35.
Figure 8-35 J2EE deployment and work with agents
8.6.2 J2EE component configuration
Once the J2EE component has been deployed, discovery and listening policies
must be created and activated, as is the case for the other monitoring
components: STI and QoS.
Creating discovery policies for J2EE
The J2EE discovery policies return URIs from Management Agents on which a
J2EE listener is deployed. You might need to create more than one discovery
policy to get a complete picture of an environment that includes both Quality of
Service and J2EE listeners.
Please consult the manual IBM Tivoli Monitoring for Transaction Performance
User’s Guide Version 5.2.0, SC32-1386 for more details
The following outlines the procedure to create new discovery policies for a J2EE
1. Start by navigating to the Work with Discovery Policies dialog from the home
page of the TMTP console. From the navigation pane on the left, select
→ Work with Discovery Policies.
2. In the Work with Discovery Policies dialog shown in Figure 8-36 on page 283,
select a policy type of J2EE and press Create New.