This document provides an overview and summary of key concepts in webMethods Trading Networks. It discusses profiles, document types, attributes, processing rules, trading partner agreements, tasks, delivery queues, and reprocessing transactions. The document is an agenda for a training session on Trading Networks concepts and functionality.

1. Agenda
 Trading Networks Overview/Concepts
 Profiles
 TN Document types
 TN Processing Rule
 TPAs
 Transaction Analysis/Viewing Documents.
 Tasks
 Reprocessing /Resubmission of transactions
 Queues - Immediate/Scheduled delivery
- 1 -
1

2. webMethods Trading Networks is a component that runs on the webMethods Integration Server.
Trading Networks enables your enterprise to link with other companies (buyers, suppliers, strategic partners) to
form a business‐to‐business trading network.
Trading Network
2

3. A profile is a collection of information about a corporation that is a part of a trading network.
Trading Networks maintains your profile (called the Enterprise profile), as well as the profile of each of your
trading partners on your network.
The information in the profile includes the following types of information:
o General information about the corporation, for example, the corporation name and its address.
o Contact information for the corporation, for example, a technical contact.
o Information about how documents should be delivered to the corporation, for example, the HTTP host name and port number to use to deliver a
document to the corporation via HTTP.
o Certificate information for digital signing of documents, verifying digital signatures, encrypting and decrypting documents.
Profiles
3

4. Trading Networks maintains a status for the profile of each partner.
After you add a profile for a partner and Trading Networks validates the fields, Trading Networks saves the profile and sets profile status to
“Inactive”.
Before you can exchange documents with the partner, you must enable the profile by updating the status to “Active”.
When you enable your own profile, you are able to exchange documents with partners
Profile Status
4

5. TN document types represent the types of documents that you expect to come into your trading network
Trading Networks supports TN document types for two categories of documents:
1. XML documents
2. Flat file documents
TN XML Document Types:
Trading Networks checks XML documents against the identification information to determine whether the document matches a defined TN XML
document type. Root tag that the XML document must have to match the TN XML document type.
TN Flatfile Document Types:
TN flat file document types are definitions that Trading Networks uses to recognize flat file documents
TN Document Types
5

6. Document attributes identify selected content from the documents that pass through your trading network.
This selected content is information in the documents that you are interested in, for example, a purchase order number or
the account number of a purchaser.
Document Attributes
6

7. Extracted attributes can be used in the following ways:
You can select a processing rule based on the value of an extracted attribute. For example, you
can select one processing rule if the sender is Partner A or another processing rule if the sender is Partner B. Another example might be to select a
processing rule if the receiver is Partner B and the custom attribute for total amount of a purchase order (Total_Order_Amount custom attribute that
you define) is greater than $10,000
If you save attribute values to the database, you can query the database based on attribute values
to locate specific documents. For example, you might want to locate all documents that were sent by Partner A and have and for which the custom
attribute for total amount of a purchase order (Total_Order_Amount custom attribute that you define) is greater than $10,000.
If Trading Networks is BAM enabled, Trading Networks passes the attribute values to Optimize for monitoring: For example, extracting the custom
attribute PO_Quantity and the system attributes, SenderID and ReceiverID, to generate a report on the purchase order quantity by a particular
sender from a particular receiver
How Trading Networks Uses Document Attributes
7

8. TN Processing Rules
Processing rules specify how you want Trading Networks to process documents. Processing rules define the actions that you want
Trading Networks to take for a particular document.
Actions: Trading Networks can perform the following processing actions:
• Execute a service that you create. Trading Networks can execute the service synchronously or asynchronously.
• Send an alert e‐mail message.
• Change the User Status system attribute that is associated with the document.
• Deliver the document to the receiver identified in the document. Trading Networks can deliver the document in the following
ways: Immediately using delivery methods such as SMTP, HTTP, FTP, or FTPS
• Queue
8

9. Unknown TN Document Type
An unknown document type can occur when a document (XML or flat file):
 Does not match any TN document type.
 Matches more than one TN document type. The document is considered to be an unknown
type because Trading Networks does not know which of the multiple matching TN document types to use.
When Trading Networks cannot match a document to exactly one TN document type:
 Trading Networks cannot extract any attribute information from the document;
 Processing rule routing will be enabled for this document;
9

10. Optionally, you can define trading partner agreements for pairs of partners.
Each TPA contains specific information for two trading partners, where one partner represents a sender and the other represents the receiver.
Trading Partner Agreement (TPA)
10

11. Transaction Analysis
Trading Networks gives you visibility into your network to track run‐time information about the documents that your Trading
Networks system has sent/received, delivery and service execution tasks that have been run/started, and activity log entries
relating to the server.
11

12. Tasks
Trading Networks creates delivery tasks to keep track of its attempts to deliver documents when it is using reliable delivery
Stopping, Restarting, and Deleting Tasks:
Stopping a task. If you want to stop an immediate delivery of a document or stop the execution of a service, you can stop the
associated delivery task or service execution task.
Restarting a task. If you previously stopped a task, you can restart it. Additionally, if a task failed (e.g., Trading Networks was
unable to deliver a document and the maximum retry limit was reached), you can restart the task. When you restart a task,
Trading Networks resets the retry count to zero. As a result, after restarting the task, Trading Networks will attempt to retry the
task up to the maximum number of allowed retries.
Deleting a task. You can manually delete tasks when you no longer need them in the system.
12

13. Reprocessing /Resubmission of transaction
You can have Trading Networks process a document again, if necessary. For example, you might want to process a document
again if the document did not match any of your TN document types or if the document triggered the wrong processing rule. In
this type of situation, you could add an appropriate TN document type or correct your processing rules, then process the
document again. For Trading Networks to be able to process a document again, the content of a document must be saved in the
database.
There are two ways you can process a document again: resubmit or reprocess.
 Resubmit. Trading Networks sends the document back to recognition processing as a new document. As a result, Trading
Networks determines the TN document type for the document, extracts the document attributes, selects a processing rule, and
processes the document
 Reprocess. Trading Networks sends the document back to processing rule selection. As a result, Trading Networks uses the TN
document type it already has saved for the document as well as the document attributes it already has saved for the
document. It simply selects a new processing rule and processes the document again.
13

14. Delivering Documents to Partners
Immediate Delivery.
Scheduled Delivery
14

15. Immediate Delivery
15

16. Scheduled Delivery
Scheduled delivery is a way to batch multiple documents that are acted on (delivered) at scheduled times
There are two types of scheduled delivery queues:
public queues and private queues.
Public queue is a queue that you define to schedule the delivery of documents that are aimed at multiple different receiving
partners. When you define a public queue, the name of the public queue is added to the list of queues you can select when
specifying a scheduled delivery method with the Deliver Document By processing action.
Private queue is a queue that you define to schedule the delivery of documents that are aimed at one specific trading partner.
You define a private queue in the profile of the partner to receive the documents. To use this queue, you select Receiver’s Queue
for the scheduled delivery method of the Deliver Document By processing action. When the Deliver Document By processing
action indicates Receiver’s Queue.
16

17. 17
https://www.youtube.com/c/TechLightning/