Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Additional TIBCO Object Service Broker Tools : Monitoring Message Traffic Data

Monitoring Message Traffic Data
Using the @TRACEMESSAGES Table
The @TRACEMESSAGES(0) table provides message traffic data between the Execution Environment and its Data Object Broker. You can use this Message Trace facility, with TIBCO Support assistance, as a diagnostic tool and for tuning the performance of your applications.
Message traffic generated by the PROCESS_TABLE tool is not collected because this tool does not use the FORALL statement. For more information about the PROCESS_TABLE tool, refer to TIBCO Object Service Broker Shareable Tools.
Invoking the Message Trace Facility
To invoke the Message Trace facility, complete the following steps:
1.
2.
3.
4.
Refining Collection of Message Traffic
Setting the TRACE field to Y in the @TRACEMESSAGES(0) table causes the messages to be logged in the @MESSAGETRACE session table. You can refine the collection of message traffic data by modifying control fields in the @TRACEMESSAGES(0) table.
Control Fields to Refine the Collection of Message Traffic
The following control fields can be modified to refine the collection of message traffic. Fields not listed in this table are reserved.
Y means trace all messages in @TRACEMESSAGES table. This entry is ignored if MESSAGELOG=Y.
Only trace access of the named request type (for example, N=FORALLs). Can be specified with or without a table name.
The maximum number of rows that the system creates in @MESSAGETRACE and @MESSAGEDUMP session (SES) tables. When the number of rows in the table reaches the number given in COUNT, the table is cleared and restarted.
Y means create HEX dump of messages in table @MESSAGEDUMP; ignored if MESSAGELOG=Y. Use this field only on the advice of TIBCO Support.
Y means create a HEX dump of all messages in the message log. It suppresses inserts to tables and can be used to prove that table inserts are not interfering with other processing. Use this option only when advised by TIBCO Support.
Y means show all messages on message log, including those normally erased by TIBCO Object Service Broker. It causes the message log to increase in size dramatically. Use only when advised by TIBCO Support.
Monitoring Accesses to Tables
Unless you specifically route messages to the message log or to the @MESSAGEDUMP table, all messages are logged in the session table @MESSAGETRACE. By analyzing the occurrences in the @MESSAGETRACE table, you can determine the access paths requested by the Execution Environment for each table access. This information can be used to optimize applications by using different variations of table access statements.
See Also
TIBCO Object Service Broker Shareable Tools for a description of the fields in the @MESSAGETRACE table.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved