Trace Message Examples
The following trace messages are written during a session where TIBCO ActiveMatrix Adapter for Database receives a message from a business process, and then processes the message.
Example 1: Adapter Started
The following message indicates that TIBCO ActiveMatrix Adapter for Database has started. The timestamp indicates when the adapter started, and the role indicates that the trace message is informational, which means the activity is normal for the adapter. The category is identified, and the corresponding status code is displayed. The status code indicates that the adapter has started successfully.
2015 Mar 26 14:30:36:068 GMT +0800 jmsServer Info [Instance] AEADB-100004 Active Database Adapter has started successfully.
Example 2: Message Received
The next set of trace messages indicates the adapter has received a message that is sent on the JMS destination. The #sUUUhFMQJAcV9UKXuKQcePoEb5k# tracking identifier that is included in the trace message uniquely identifies the message. The adapter from which the message originated provided the identifier.
2015 Mar 26 14:34:35:634 GMT +0800 jmsServer Info [RPC] AEADB-500001 RPC Service Thread <RPC.JMSTopic.Thread.1> receive data. tracking=#sUUUhFMQJAcV9UKXuKQcePoEb5k#BW.operation_ora.application.operation_ora.JMS_7 Execute-procedure-getPrice_output.Invoke-an-Adapter-Request-Response-Service#
Example 3: Object Moved
The final trace message indicates the message has been moved to the output directory, which completes the interaction of the adapter with the message. Because the trace message is the termination point, the tracking identifier is not displayed.
2003 Feb 22 20:15:42:812 GMT -8 FileAdapter.FileAdapterConfiguration Info [Adapter] AEFA-000070 File customers.txt is moved to the Output Directory F:\ca\integration\001\data_sets\files\solutions\output