Parser Statistics Test

A parser is a program that interprets the physical bit stream of an incoming message, and creates an internal logical representation of the message in a tree structure. The parser also regenerates a bit stream for an outgoing message from the internal message tree representation. A parser is called when the bit stream that represents an input message is converted to the internal form that can be handled by the broker; this invocation of the parser is known as parsing. The internal form, a logical tree structure, is described in Logical tree structure. It is described as a tree because messages are typically hierarchical in structure; a good example of this structure is XML. The way in which the parser interprets the bit stream is unique to that parser; therefore, the logical message tree that is created from the bit stream varies from parser to parser.

The parser that is called depends on the structure of a message, referred to as the message template. Message template information comprises the message domain, message set, message type, and physical format of the message. Together, these values identify the structure of the data that the message contains.

A parser is also called when a logical tree that represents an output message is converted into a bit stream; this action by the parser is known as writing. Typically, an output message is generated by an output node at the end of the message flow. However, you can connect more nodes to an output node to continue processing of the message.

The message domain identifies the parser that is used to parse and write instances of the message. The remaining parts of the message template, message set, message type, and physical format, are optional, and are used by model-driven parsers such as the MRM parser.

For each message flow parser type, this test reports the largest bit stream that is parsed/written. In addition, this test reports the processing rate of each parser type in terms of parses and writes. This way, administrators may be alerted to processing bottlenecks , if any.

Target of the test : An IBM Integration Bus

Agent deploying the test : An internal/remote agent.

Outputs of the test : One set of results for each Execution group:message flow parser of the IBM Integration Bus that is to be monitored

Configurable parameters for the test
Parameters Description

Test period

How often should the test be executed.

Host

The host for which the test is to be configured.

Port

The port on which the specified host listens.

JNDI Namespace Location

Indicate where the JNDI namespace has been created. For this, select one of the following options: File or LDAP. Select File if the JNDI namespace is created in the same location as that of the IIB server.

SSL

If you have chosen LDAP as the JNDI Namespace Location wherein the LDAP server communicating with the IIB server that is to be monitored is an SSL-enabled server, then set the SSL flag to Yes. By default, this flag is set to No.

User DN and Password

Here, provide the credentials of the Active Directory user created as explained in Creating a user in the Active Directory server, if the target IIB server is monitored in an agentless manner. If the IIB server is to be monitored in an agent based manner, specify none against these parameters.

Confirm Password

Confirm the Password by retyping it in this text box.

JNDI Provider URL

Specify the URL that was specified as the provider URL while creating the initial context. To know the Provider URL, refer to Agent based monitoring of the IIB server if you choose to monitor the target IIB server in an agent based manner and Agentless Monitoring of the IIB server if you chose to monitor the target IIB server in an agentless manner.

TopicConnectionFactory

Specify the name of the connection factory in this text box. If you have chosen to monitor the target IIB server in an agent-based manner, refer to Creating a Connection Factory and if you have chosen to monitor the target IIB server in an agentless manner, refer to Creating a Connection Factory.

JMS Resource Stats

Specify the name of the JMS destination that you have created for storing the Resource statistics. If you chose to monitor the target IIB server in an agentless manner, refer to Creating the JMS Destinations and if you choose to monitor the target IIB server in an agent based manner, refer to Agent based monitoring of the IIB server.

JMS Flow Stats

Specify the name of the JMS destination that you have created for storing the Message flow statistics. If you chose to monitor the target IIB server in an agentless manner, refer to Creating the JMS Destinations and if you choose to monitor the target IIB server in an agent based manner, refer to Agent based monitoring of the IIB server.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Threads

Indicates the number of message flow threads that contributed to the statistics of this message flow parser type accumulation during the last measurement period.

Number

 

Memory utilization

Indicates the approximate amount of user data-related memory used for this message flow parser type during the last measurement period.

KB

The value of this measure cannot be calculated exactly.

Maximum read bit stream

Indicates the largest bit stream parsed by this message flow parser type during the last measurement period.

KB

 

Maximum written bit stream

Indicates the largest bit stream written by this message flow parser type during the last measurement period.

KB

 

Reads

Indicates the rate at which parses were completed successfully by this message flow parser type during the last measurement period.

Reads/sec

Comapring the value of this measure across the parser types will help you identify the parser type that is busy processing the parses.

Failed reads

Indicates the rate at which parses failed in this message flow parser type during the last measurement period.

Reads/sec

A low value is desired for this measure. A sudden/gradual increase in the value of this measure indicates processing bottlenecks.

Writes

Indicates the rate at which writes were completed successfully to this message flow parser type during the last measurement period.

Writes/sec

Comparing the value of this measure across the parser types will help you identify the parser type that is busy writing the messages.

Failed writes

Indicates the rate at which parses failed to be written to this message flow parser type during the last measurement period.

Writes/sec

A low value is desired for this measure. A sudden/gradual increase in the value of this measure indicates processing bottlenecks.