![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The TIBCO Adapter SDK tracking facility allows custom adapters to associate tracking information with data (not with trace messages). The tracking information remains associated with the data as they are passed between ActiveEnterprise applications. This makes it possible to see a history of the operations performed on the message.Use of tracking should not be confused with tracing. While tracing provides full detail of custom adapter activities, tracking provides an audit trail for messages as they travel through the ActiveEnterprise.Tracking is implemented by an MTrackingInfo object.
1. The source application places information into the MTrackingInfo objects using the MTrackingInfo::addApplicationInfo() method.
2. As the data is sent through the enterprise, each TIBCO application adds information about its operations to messages that pass through.
3. If an operation on the data fails, the application where it fails can access the information by looking at the message.
MTrackingInfo cannot be used if you are using rvMsg format.Because the MTrackingInfo is sent on the wire, applications should limit the information added through addApplicationInfo(). Each application should call addApplicationInfo() only once per message. The message should contain concise and minimal information.The following pseudo-code fragment illustrates how a subscriber event listener could extract tracking information if serialization failed.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |