204 End-to-End e-business Transaction Management Made Easy
10.Remove the file <WL7_HOME>\server\bin\jitipi.dll or
<WL7_HOME>\server\bin\ijitipi.dll file, if it exists. Some OS platforms use
jitipi.dll and some OS platforms use ijitipi.dll.
6.6 TMTP Version 5.2 best practices
This section describes our recommendations on how to implement and configure
TMTP Version 5.2 to maximize effectiveness and performance in your production
environment. Please note that although the following recommendations are
general and suitable to most typical production environments, you may need to
customize configurations for your environment and particular requirements.
Overview of recommendations
Use the following default J2EE Monitoring settings for long term monitoring
during normal operation in the production environment.
– Only record aggregate records.
– Discovery Policies for J2EE and QoS transactions should be run and then
disabled once listening policies have been created off the discovered
– Use a 20% sampling rate.
– Set low tracing detail.
Define the URI filters as narrow as possible to match the transaction patterns
you are interested in monitoring. This will optimize monitoring overhead
during normal operation in the production environment. The narrow URI filters
also help the effectiveness of analysis of TMTP reports, as you can
selectively investigate transaction data of interest.
It is suggested to avoid using regular expressions that contain wildcard (.*) in
the middle of URI filter, if possible.
Only turn up the tracing details when a performance or availability violation is
detected for the J2EE application server to allow for quick debugging of the
Note: The [i]jitipi.dll file may not exist in <WL7_HOME>\server\bin,
depending on the version of J2EE Instrumentation. If it does not exist in
this directory, it is in the Management Agent's directory, and can be left in
the Management Agent's directory without any harm.
Note: The Discovery Policies may be re-enabled at a future date if
further transaction discovery is required.
Chapter 6. Keeping the transaction monitoring environment fit 205
situation. It is recommended for high traffic Web sites to set the Sample Rate
lower than 20% when a tracing detail higher than the “Low” level is used.
Setting the maximum number of sample per minute instead of the sample rate
is also recommended to better regulate monitoring overhead during a high
In a production environment, we recommend collecting Aggregate Data Only.
TMTP will automatically collect a certain number of Instance records when a
failure is detected. It is not recommended to collect Aggregate and Instance
records during normal operation in a production environment, as it may
generate overwhelming data.
In a large-scale environment with more than 100 Management Agents
uploading ARM data to the Management Server database, the scheduled
data persistence may take more than a few minutes. As disk access may be a
bottleneck for persisting or retrieving data to/from the DB, make sure the hard
drive and the disk interface have good read/write performance. Consider
keeping the database on a dedicated physical disk if possible and using
In a large-scale environment, we suggest increasing the Maximum Heap size
for the WebSphere Application Server 5.0 JVM where the Management
From the WebSphere Application Server admin console, select Servers
→ server1 → Process Definition → Java Virtual
Machine, and set the Max heap Size to 256 > Larger Value.
Consider changing the WebSphere Application Server JVM Maximum Heap
size to half the physical memory on the system if there are no competing
products that require the unallocated memory.
Run db2 reorgchk daily on the database to prevent the UI/Reports
performance from degrading as the database grows. This command will
reorganize the indexes.
Best practice for J2EE application monitoring and debugging
Out of the box, the TMTP J2EE Monitoring Component records a summary of the
transactions in the J2EE application server. This default summary level is optimal
Note: Having a higher setting for the WebSphere Application Server JVM
Maximum Heap size means that WebSphere Application Server can use
up to this maximum value if required.
Note: The db2 reorgchk command might take some time to complete and
may need to be scheduled at off peak times.