Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Appendix A Provided Services : Transaction Trigger Service

Transaction Trigger Service
The Transaction Trigger service is used to provide a mechanism to trigger any scheduled transaction in the queue. This service accepts a transmissionID and protocol, or a and protocol, and sends a queued batch or a scheduled transaction.
What Is the Service Used For
The Transaction Trigger service can be used for triggering the following:
Since these batches are not processed by the scheduled task poller, this is one of the two mechanisms to send them out; the other way is to send this grouped batch from the Message Queue logs in the GUI.
How the Service Works
The Transaction Trigger service can be used to perform the following:
When transmissionID is used as a request attribute to trigger, the protocol value has to be Gateway; when documentID is used as a request attribute to trigger, the corresponding protocol name has to be given.
The response returned for a Transaction Trigger service indicates the status, which shows whether the transaction has been triggered successfully or not.
The status in the response does not indicate the actual delivery of the message to the partner: if you want to check the transport delivery status of your transactions, use the audit log to check whether the transaction was delivered to the partner, or write your own user service to check the delivery status.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved