How Trading Networks Processes Transaction Data
After you have completed the necessary configuration steps in
Design-Time Actions, at run time,
Trading Networks processes the data that you have configured for monitoring, as described in the following steps:
1. After the recognition of a document, Trading Networks creates a BizDocEnvelope that contains the following items:
![*](bullet.gif)
The original document
![*](bullet.gif)
The extracted attribute values
![*](bullet.gif)
Any additional information required for routing and processing the document
2. Trading Networks checks whether that TN document type and Trading Networks itself are enabled for BAM. If BAM is enabled, Trading Networks collects all of the attribute values for monitoring and stores those attribute values in a hash map within the BizDocEnvelope until the document processing is complete.
3. After the document processing is complete, Trading Networks once again synchronizes the actual attribute values to the values existing in the hash map. Synchronization is necessary because the attribute values stored in the BizDocEnvelope may have been updated either during any of the service execution tasks (both Synchronous /Asynchronous) or due to any other services in Trading Networks.
4. Trading Networks maps the attributes to the event maps (in accordance with the configuration completed during design time) and creates events.
For more information about the BizDocEnvelope and the processing of documents in Trading Networks, see webMethods Trading Networks Administrator’s Guide.
5. Trading Networks passes the events to Broker. If an error occurs while passing the events, an exception is thrown. This exception will be logged as a warning in the Activity Log associated with the specific document.
During the document processing, the point at which
Trading Networks actually passes the event to the broker depends on the processing rule actions defined for the TN document type. For more information about when
Trading Networks passes the events to the broker, see
Stages at Which Events Are Passed to the
Broker .
6. Optimize for B2B subscribes to the events from the JMS queue and feeds the events to the Optimize for B2B Analytic Engine. The Analytic Engine analyzes these events and saves the data to the Optimize database.
7. During monitoring,
My webMethods Server retrieves the required data from the
Optimize database at run time and allows the user to view the data in various formats such as charts, tables, and graphs. For an overview, see
Working with Trading Networks KPIs.