The Rhapsody Integration Engine provides facilities for receiving, managing and transmitting messages between remote systems. Each message may have a logical structure which can be utilized by the engine to manipulate the content or to control the path the message takes through the engine.
Message tracking provides the ability to identify the path a message has taken through the engine and to identify the status of delivery attempts. As a consequence of the engine's business logic capabilities, the state of a message and its associated events can be monitored, and appropriate exception handling can be invoked if required. This functionality is required primarily to support TCP communications with remote systems to provide a guarantee of delivery.
When a message tracking scheme is attached to a communication point, it automatically overrides the Out->In retry settings. Therefore, the settings for any communication point with a message tracking scheme attached are ignored. Alternatively, the Out->In can be disabled by setting an infinite response timeout; that is, set it to 0 or -1.
The Message Tracking tab on the communication point properties dialog allows message tracking schemes to be assigned to communication points. Refer to Message Tracking Schemes for details.
