Copyright © TIBCO Software Inc. All Rights Reserved

Trace Message Fields

Each trace message includes the following fields:

Table 24 Tracing Fields 

Field Name	Description
Timestamp	Timestamp of occurrence. For example, 2003 Jul 09 10:58:54:984 GMT +5.
Adapter Identifier	Name of the adapter that wrote the trace message. This is a combination of the adapter acronym and adapter configuration name. For example, the application identifier, LDAP.publisher1 identifies a TIBCO ActiveMatrix Adapter for LDAP service named publisher1.
Role	A role can be: • Info. Indicates normal adapter operation. No action is necessary. A tracing message tagged with Info indicates that a significant processing step was reached and has been logged for tracking or auditing purposes. Only info messages preceding a tracking identifier are considered significant steps. • Warn. An abnormal condition was found. Processing will continue, but special attention from an administrator is recommended. • Error. An unrecoverable error occurred. Depending on the error severity, the adapter may continue with the next operation or may stop altogether. • Debug. A developer-defined tracing message. In normal operating conditions, debug messages should not display. When configuring the adapter you define what roles should or should not be logged. For example, you may decide not to log Info roles to increase performance.
Category	One of the following: • Adapter. The adapter is processing an event. • Application. The adapter is interacting with the LDAP server. • Configuration. The adapter is reading configuration information. • Database. The adapter is interacting with a database. • Metadata. The adapter is retrieving metadata from the LDAP server. • Palette. The adapter is interacting with the palette. • Publisher Service. The publication service is reporting this trace message. • Request-response Server. The request-response service is reporting this trace message. • Shutdown. The adapter is shutting down. • Startup. The adapter is starting. • Subscription Service. The subscription service is reporting this trace message. • System. This category is not linked to a specific event process. The trace message may be related to a Microsoft Windows service related messages, memory allocation, file system error, and so on. • TibRvComm. The adapter is communicating with TIBCO Rendezvous. • XML. The adapter is parsing XML documents.
Status Code	Unique code for the message and description. Status codes are identified by a unique number and description. If a trace message includes an error or warn role, the status code documentation includes a resolution. See Status Messages for details.
Tracking Identifier	A unique identifier that is "stamped" on each message by the originating adapter. The tracking identifier remains in effect from a message’s beginning to its completion as it is exchanged by TIBCO applications. If the adapter is the termination point of the message, the tracking identifier is not displayed in the trace message. You cannot modify the tracking identifier format or configure what information is displayed.

Copyright © TIBCO Software Inc. All Rights Reserved