Tracker resubmit endpoint

The Tracker resubmit endpoint is a custom Integrate endpoint used in conjunction with the
Tracker search index. Logging transactions in Tracker provides an
audit trail for every transaction and their
state. Should a transaction fail for any reason, the error can be discovered
using data stored in the Tracker search index. The Tracker resubmit endpoint enables a user to arbitrage errors and then
retry failed transactions by either processing them through the original service or a custom service
that may have been designed to handle failed transactions.

The Tracker resubmit endpoint needs to be registered against a
Tracker document type and an associated
state. The endpoint will be active against documents that are of the same type
and state. You then specify which service should be invoked by the Tracker resubmit endpoint should it
get triggered. When the endpoint is finally started, a resubmit option is added to the Tracker UI1
(highlighted below):

In the UI above, the Tracker resubmit endpoint is registered for Tracker documents of
type JMS with the state Started. When the resubmit option is clicked, the service associated to
this endpoint is executed.

The document state's content, ported in a file. This is a temporary file that will be deleted after your endpoints are invoked. It will point to a file containing the actual content of the document state. If there is no content, this will be null.

Example

Consider the following Tracker resubmit endpoint configuration:

This registers the Tracker resubmit endpoint for Tracker documents of type JMS with the state Started. The service
assigned to this endpoint is as follows:

(1) Logs a message to underlying log engine(2) Looks for the Tracker property keyed Resubmit Count.(3-4) Checks and increments the property accordingly, to keep track how many times this was resubmitted(5) Re-persist the property

Using this feature, developers can potentially re-execute customized logic based on the tracked content of the original
Tracker document.

Want more examples?

The distribution ships with an Integrate package called examples, which contains services
demonstrating more use cases.

Only for document states that match the endpoint's configured document state and type. ↩