Trading Networks 10.7 | Optimizing B2B Interactions | Configuring Trading Networks Transaction Data for Optimize for B2B | Monitoring Trading Networks-Specific Data
 
Monitoring Trading Networks-Specific Data
You can analyze Trading Networks-specific data, such as transaction status and task status, to get results on successful transactions, the percentage of documents resubmitted or reprocessed, and so on. However, because these data are dimensions, you cannot analyze them using Optimize for B2B without completing additional configuration tasks. To analyze Trading Networks-specific data, you must either create custom attributes or use the required system attributes to monitor the data and then create the associated KPIs.
*To analyze Trading Networks-specific data based on status
1. Create the required attributes in the TN document type. Alternatively, you can use the following business-monitoring system attributes to create B2B-specific KPIs to analyze data:
The following table describes the system attributes:
System Attribute
Description
Total Count
Total count of executed transactions.
Successful Transaction Count
Total count of successful transactions.
Resubmit Count
Total count of resubmitted transactions.
Reprocess Count
Total count of reprocessed transactions.
Successful Delivery Count
Total count of successfully delivered transactions.
You can also use the individual KPIs that you create using the above system attributes to create composite KPIs. For example, you could create a composite KPI that uses a Successful Transaction Count for a particular partner or region (an individual KPI) in combination with the Total Count system attribute (a second individual KPI) to calculate what percentage of transactions were successful.
2. Configure and enable the TN document type for monitoring, as described in Configuring TN Document Types and Attributes for BAM.
3. Create the required KPIs for the data that you want to monitor and analyze, for example, using the Successful Transaction Count system attribute. Create one KPI for total count and another KPI for successful transaction count. Create another composite KPI using these two individual KPIs that divides the successful transaction count by the total count to get a percentage of successful transactions. You can follow the same procedure for analyzing data using other attributes.
4. After you configure the required KPIs, associate a service execution task with the TN document type's processing rule that updates the attributes after the completion of the service execution.
For more information about any of the tasks described in this section, see the sources listed in the following table:
To...
See this source...
Create custom attributes
"Defining and Managing Document Attributes" chapter in webMethods Trading Networks Administrator’s Guide
Configure and enable TN document types for monitoring
Create individual KPIs and Dimension hierarchies
Administering webMethods Optimize
Configure the processing rule action.
"Defining and Managing Processing Rules" chapter in webMethods Trading Networks Administrator’s Guide