Stages at Which Events Are Passed to the Broker
Important:
webMethods Broker has been deprecated.
After completing the processing of a document, Trading Networks collects the monitorable attribute values and creates events to be passed to the broker(deprecated).
The processing rule action for a TN document type you are monitoring determines how events are passed to the broker(deprecated), as follows:
If you choose to turn off the routing for the document, the event is passed to the broker (deprecated) immediately after document recognition is done and is persisted.
If you use the
Execute a Service processing action, different methods can be used to invoke the service. The timing for when the event is passed to the broker (deprecated) is determined based on which of the following methods is used to invoke the service:
Synchronous: The event is passed only after the service execution is complete and the document processing is successful.
Asynchronous or Reliable Execution: The event is passed after service execution is complete, regardless of the document processing status.
Service execution task: The event is passed after the service execution is complete and the service execution task status is updated, regardless of the document processing status.
If you use the
Deliver Document By processing action, the event is passed to the broker (deprecated) only when the document processing status is complete.
For more information about processing rule actions, see
webMethods Trading Networks Administrator’s Guide. For more information about configuring TN document types for monitoring, see
Configuring TN Document Types and Attributes
for BAM.
When the events are passed to the broker (deprecated) is determined by the TN document type's processing rule actions and the setting on the Send BAM Event After field on the Document Type Attributes page.