IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Client Communications attributes

The Client Communications attributes display overall statistics about server-side monitoring and a client-side API to retrieve performance data.

The attributes within this group are used to build the Client Communications workspace.

Attributes in this group are only provided for WAS version 6.0 or later.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

API Connections

The number of API sessions being used by clients that are currently network connected to this application server. Some of these API connections might be being by internal system processes on behalf of a client. Format is positive integer.

Buffered Read (bytes)

The number of bytes of data that have been received from the network and are held pending further processing. Large values might indicate that the application server is unable to process data fast enough to keep up with the clients attached. Format is positive integer.

Buffered Write (bytes)

The number of bytes of data being held pending transmission. Large values might indicate network congestion or clients which are unable to process data fast enough to keep up with the application server. Format is positive integer.

Clients Attached

The number of distinct client processes currently network connected to this application server. Format is positive integer.

Errors

The communication errors that have occurred and resulted in a network connection to a client being disconnected. Format is positive integer.

Instrumentation Level

The instrumentation level for the client communications. For WebSphere 5, the valid values are None, Low, Medium, High, and Maximum; for WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec)

The length (in seconds) of the sampling interval. Format is positive integer.

Message Read (bytes)

The number of bytes of message data received from client processes over network connections. This does not include data used to negotiate the transmission of messages. Format is positive integer.

Messages Received at JMS 0 Priority

(bytes)

The number of messages received at JMS priority 0. Format is positive integer.

Messages Received at JMS 1 Priority (bytes)

The number of messages received at JMS priority 1. Format is positive integer.

Messages Received at JMS 2 Priority (bytes)

The number of messages received at JMS priority 2. Format is positive integer.

Messages Received at JMS 3 Priority (bytes)

The number of messages received at JMS priority 3. Format is positive integer.

Messages Received at JMS 4 Priority (bytes)

The number of messages received at JMS priority 4. Format is positive integer.

Messages Received at JMS 5 Priority (bytes)

The number of messages received at JMS priority 5. Format is positive integer.

Messages Received at JMS 6 Priority (bytes)

The number of messages received at JMS priority 6. Format is positive integer.

Messages Received at JMS 7 Priority (bytes)

The number of messages received at JMS priority 7. Format is positive integer.

Messages Received at JMS 8 Priority (bytes)

The number of messages received at JMS priority 8. Format is positive integer.

Messages Received at JMS 9 Priority (bytes)

The number of messages received at JMS priority 9. Format is positive integer.

Messages Sent at JMS 0 Priority

(bytes)

The number of messages transmitted at JMS priority 0. Format is positive integer.

Messages Sent at JMS 1 Priority (bytes)

The number of messages transmitted at JMS priority 1. Format is positive integer.

Messages Sent at JMS 2 Priority (bytes)

The number of messages transmitted at JMS priority 2. Format is positive integer.

Messages Sent at JMS 3 Priority (bytes)

The number of messages transmitted at JMS priority 3. Format is positive integer.

Messages Sent at JMS 4 Priority (bytes)

The number of messages transmitted at JMS priority 4. Format is positive integer.

Messages Sent at JMS 5 Priority (bytes)

The number of messages transmitted at JMS priority 5. Format is positive integer.

Messages Sent at JMS 6 Priority (bytes)

The number of messages transmitted at JMS priority 6. Format is positive integer.

Messages Sent at JMS 7 Priority (bytes)

The number of messages transmitted at JMS priority 7. Format is positive integer.

Messages Sent at JMS 8 Priority (bytes)

The number of messages transmitted at JMS priority 8. Format is positive integer.

Messages Sent at JMS 9 Priority (bytes)

The number of messages transmitted at JMS priority 9. Format is positive integer.

Message Written (bytes)

The number of bytes of message data sent to client processes over network connections. This does not include data used to negotiate the transmission of messages. Format is positive integer.

Messaging Engine Name

The name of the message engine. The value format is an alphanumeric string, with a maximum of 256 characters.

Multicast Send Messages

The number of messages transmitted using multicast protocols. Format is positive integer.

Multicast Write

The number of bytes transmitted using multicast protocols. Format is positive integer.

Node Name

The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node

The name of the server subnode. Alphanumeric string. Maximum 128 characters.

Reads

The number of read operations used to receive data from client processes through network connections. Format is positive integer.

Reads Blocked

The number of read operations that could not be completed immediately. This number can be used as an indicator of network congestion when communicating with client processes. Format is positive integer.

Received at High Priority (bytes)

The number of bytes of data received at a high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Received at Highest Priority (bytes)

The number of bytes of data received at the highest possible priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Received at JMS 0 Priority (bytes)

The number of bytes of data received at the priority used by JMS priority 0 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Received at JMS 1 Priority (bytes)

The number of bytes of data received at the priority used by JMS priority 1 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Received at JMS 2 Priority (bytes)

The number of bytes of data received at the priority used by JMS priority 2 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Received at JMS 3 Priority (bytes)

The number of bytes of data received at the priority used by JMS priority 3 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Received at JMS 4 Priority (bytes)

The number of bytes of data received at the priority used by JMS priority 4 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Received at JMS 5 Priority (bytes)

The number of bytes of data received at the priority used by JMS priority 5 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Received at JMS 6 Priority (bytes)

The number of bytes of data received at the priority used by JMS priority 6 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Received at JMS 7 Priority (bytes)

The number of bytes of data received at the priority used by JMS priority 7 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Received at JMS 8 Priority (bytes)

The number of bytes of data received at the priority used by JMS priority 8 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Received at JMS 9 Priority (bytes)

The number of bytes of data received at the priority used by JMS priority 9 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Received at Low Priority (bytes)

The number of bytes of data received at a low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Received at Lowest Priority (bytes)

The number of bytes of data received at the lowest possible priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Received at Very High Priority (bytes)

The number of bytes of data received at a very high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Received at Very Low Priority (bytes)

The number of bytes of data received at a very low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Sample Date and Time

The date and time the Tivoli Enterprise Management Agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:


Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006, at 18:32:03.

This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Sent at High Priority (bytes)

The number of bytes of data transmitted at a high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Sent at Highest Priority (bytes)

The number of bytes of data transmitted at the highest possible priority for transmission. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Sent at JMS 0 Priority (bytes)

The number of bytes of data transmitted at the priority used by JMS priority 0 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Sent at JMS 1 Priority (bytes)

The number of bytes of data transmitted at the priority used by JMS priority 1 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Sent at JMS 2 Priority (bytes)

The number of bytes of data transmitted at the priority used by JMS priority 2 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Sent at JMS 3 Priority (bytes)

The number of bytes of data transmitted at the priority used by JMS priority 3 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Sent at JMS 4 Priority (bytes)

The number of bytes of data transmitted at the priority used by JMS priority 4 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Sent at JMS 5 Priority (bytes)

The number of bytes of data transmitted at the priority used by JMS priority 5 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Sent at JMS 6 Priority (bytes)

The number of bytes of data transmitted at the priority used by JMS priority 6 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Sent at JMS 7 Priority (bytes)

The number of bytes of data transmitted at the priority used by JMS priority 7 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Sent at JMS 8 Priority (bytes)

The number of bytes of data transmitted at the priority used by JMS priority 8 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Sent at JMS 9 Priority (bytes)

The number of bytes of data transmitted at the priority used by JMS priority 9 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. Format is positive integer.

Sent at Low Priority (bytes)

The number of bytes of data transmitted at a low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Sent at Lowest Priority (bytes)

The number of bytes of data transmitted at the lowest priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Sent at Very High Priority (bytes)

The number of bytes of data transmitted at a very high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Sent at Very Low Priority (bytes)

The number of bytes of data transmitted at a very low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages. Format is positive integer.

Server Name

The name of the application server. Alphanumeric string.

Summary

Whether this row is a summary row of statistical totals for all messaging engines. Valid values are No and yes.

Total Read (bytes)

The number of bytes of data received from client processes. This includes both message data and data used to negotiate the transmission of messages. Format is positive integer.

Total Written (bytes)

The number of bytes of data sent to client processes. This includes both message data and data used to negotiate the transmission of messages. Format is positive integer.

Writes

The number of write operations used to transmit data to client processes via network connections. Format is positive integer.

Writes Blocked

The number of write operations that could not be completed immediately. This number can be used as an indicator of network congestion when communicating with client processes. Format is positive integer.

Additional information:


Parent topic:

Attributes for ITCAM Agent for WebSphere Applications