IMS Store Transactions Test

This test monitors the transactions to the message store database.

Target of the test : An Oracle Communications Messaging Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every Oracle Communications messaging server.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.


The host for which the test is to be configured.


The SMTP port of the Oracle Communications messaging server.


Specify the path to the directory into which all servers of a given server group (i.e., all servers managed by a given Administration Server) are installed. For example, in Windows environments, the path can be expressed as: C:\iOracom\server5. In Unix platforms, the path can be specified in the following format: /usr/iOracom/server5. A server group may include other Oracle Communications messaging servers in addition to the messaging server.


Enter the full path to the counter registry to use. By default, the path to the counter registry will be: <IPLANET_MESSAGING_SERVER_ROOT_DIR>/<SERVER_INSTANCE>/counter/counter. Here, SERVER_ROOT_DIR will be the value of the ServerRoot parameter above, and the SERVER_INSTANCE is the name of the instance of the messaging server specified during installation. For example, in Windows environments, the path specification can be: C:\iPlanet\Server5\msg-egtes\counter\counter, and in Unix environments, it can be: usr/iplanet/server5/msg-sun08/counter/counter.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Active transactions

Indicates the number of transactions that are currently active.


A high value for this measure may indicate a large number of active transactions.

Transaction begins

Indicates the rate at which transactions have begun.



Transaction commits

Indicates the rate at which transactions have been committed



Transaction aborts

Indicates the rate at which transactions have been aborted/rolled back


Rollbacks are expensive operations on a database, and hence, will have to be kept at a minimum.