You will need to install Oracle SOA Suite and the Hyperic HQ server and agents for this recipe. Both Hyperic HQ and Oracle SOA Suite will need to be running. You will also need the login credentials for the Hyperic HQ console.

Follow these steps to monitor the number of committed transactions:

The Hyperic HQ agent periodically connects to the WebLogic server instances that are in its inventory, and uses the JMX service to obtain metrics on a number of measurements, including the JTA transaction statistics. It reports this data back to the server, which stores it in its database. We can then view this collected data by using the Hyperic console.

The number of committed JTA transactions are a very good indicator of how busy a system is. We can therefore use it to detect when an abnormally high load affects our system, to be aware of the potential performance problems that this may cause.

WebLogic server does have a limit on the number of concurrent JTA transactions that can be going on at any one time, so this metric can be a useful indicator of whether our system is reaching that limit.