![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Table 42 Tracing Fields Timestamp of occurrence. For example, 2003 Feb 22 20:14:51:718 GMT -8. 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, ADB.publisher1 identifies a TIBCO Adapter for ActiveDatabase service named publisher1.
• Information. 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.
• Warning. 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.
• Request-Response Client Service. The Request-Response Invocation service is reporting this trace message. 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. 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.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |