TRADING NETWORK

What is Trading Network?

▪ The basic concept of Trading Network is that group of

organizations Exchange Business Documents to each
other.This is also Known as Business to Business
Communication.
▪ Trading Network is a Package that resides in Integration
Server.
▪ Trading Network is a format-neutral, business document
gateway that can recognize and process multiple XML and
FlatFile formats that flow between distributed Trading
Partners.Trading Partner may be any System, within or
without the Enterprise.
TN Architecture
 Trading Network Components
■ My webMethods server: When a user monitors a transaction, MywebMethods
Server handles the request by interacting with Trading Networks to perform the
function and return information to the user.
■ Trading Network Console: Console is a Trading Networks user interface. It is used
for designing Trading Networks to recognize documents using TN document types
and how TN processes Documents.
■ Trading Network: Wm TN package runs within the Integration Server. The package
provides the logic to handle the management of partners on your network and the
exchange of documents
■ RDBMS: Trading Networks uses to store all information about the trading network:
partner information, the types of documents to process, how to process business
documents, information about business documents that pass through the network,
log information.
■ Integration Server: The hosts packages that contain services and related
documents.
Document Processing in TN
Minimum required set up for TN to process documents
■ Partner Profiles: A Partner’s profile is information about a
Partner in our trading network.
■ TN Document types: TN document type represent the
type of documents that we expect to come into TN.
■ Processing Rule: PR Specifies how TN to Process
Documents. It also define the actions that Trading
Networks to take for a particular document.
Overview of Sending Documents to TN
Document Processing - Design Time

Following set up should present to process the document.

■ Sender’s profiles : To ensure the user sending the document is
an active partner in your network.
■ Receiver’s profiles : To obtain information specific to the
receiving partner for processing Document.
■ TN document : types to recognize the type of document that
was sent and to determine document attributes to associate
with the document.
■ Processing rules : to determine the actions you want Trading
Networks to perform against the inbound document.
 Document Processing - Run Time
During Run Time processing the TN performs for an inbound document can be
divided into four areas:
■ Recognition processing: determines the TN document type that matches the
inbound document using the identification information that we defined in TN
document types, and after locating the matching TN document type, obtaining the
values of the document attributes that we specified in the TN document type.
■ Processing rule selection: determines the processing rule to use for the inbound
document based on the criteria that we defined in processing rules.
■ Pre-processing actions: performs the pre‐processing actions that we defined in
the TN document type and processing rule.
■ Processing actions: performs the processing actions that you defined in the
processing rule.
Excercise
■ Sending xml to TN
■ 1)Create client to send data to TN
Design Time components
■ 2)Create doc type
■ 3)Profile – Sender and Receive
■ 4)Processing Rule
■ 5)Service invoked by PR to insert data in DB
■ 6)Sending Ack to partner
Sending file To Trading Network
■ We have to create the Xml Document and it send to Trading Network .
■ Before to send the document to TN, we can define the root tag in TN.
■ The file is send to TN with the help of using
wm.tn.receive or wm.tn.routeXml service.
■ Unlike XML files, the flatfile structure is different,it is record-based
storage format.
■ First we create the document gateway service, then the Flatfile is send
to the document gateway service.
 What happens in TN once data is
received
When Trading Network receives the document, it processes the document as
defined by TN document types and processing rules
■ Recognize the document using TN Document types.
■ Extract the attributes value from the document as instructed by matching TN Document
types.
■ Performs the pre‐processing actions against the document as defined in the TN
document type and/or processing rule.
■ Performs the processing actions against the document as defined in the processing
rule.
■ After received the document the TN checks a document against all enabled TN
Document types. Suppose the document is not matched means it considered to be an
unknown type. It shows “unmatched” in User status Column in TN Console.
■ If the document is matched means the processing status column should be done.
Create Partner Profile

■ A partner’s profile is information about a partner in our trading

network
■ Partner profile must be filled out before we can exchange business
documents with some other partners.
■ Trading Networks maintains external IDs for a partner and uses those
external IDs to identify sending and receiving partners that are
identified within a document.
■ TN uses the value of the DUNS number.It finds in the document and
matches it to profiles in its system. When it finds a profile with an
external ID of type DUNS that matches the value from the document,
it determines the sender of the document is the partner with the
matching profile.
Viewing Partner Profile Creating
HOW TO CREATE THE DOCUMENT TYPE IN TN CONSOLE

To define XML document types, We specify the following types of information:

Root tag: Specify the value of the root tag within the XML
document that you want documents that match this TN XML
document type to have.
 If Trading Networks successfully extracts the Sender ID/ Receiver ID system
attributes from a document and match it to a partner profile on your Trading
Networks system.TN Networks compares the name of the partner to the partner
that we specify in the processing rule.
double Click the Sender Id->Edit Attribute Window is open
->Click Built-in->Select DUNS->Ok.Similarly the Receiver Id.
Viewing the created document type
Processing Rule Selection
Trading Networks matches information from the
inbound document against the criteria you specify in
processing rules. The information from the document that
you can use as processing rule criteria is:
■ Sender identified in the inbound document.
■ Receiver identified in the inbound document.
■ Whether Trading Networks encountered errors during
recognition processing.
■ Values of the custom attribute values that Trading
Networks extracted from the document.
HOW TO CREATE THE PROCESSING RULE
Go to TN Console->Type the Name->Click the Criteria->Select the Sender,Receiver and Document type->ok.
Select the Service Invoked By PR

Click Action->Select Execute a Service->Click Find Service Tab->Select a

Service->Ok.
Illustration of the Processing Rule
Create Another PR and Changing the Sender And
Receiver
 Viewing Partner Agreement details
A Trading Partner Agreement in TN is a set of parameters use to govern how
documents are exchanged between two trading partners. To use a TPA, both partners in
the agreement must have existing profiles in Trading Networks.
Document received in TN
After received the Document the Processing Status Should be Done.
The Sender and Receiver name Should be Shown.Double click the document it shows
document details.
Received Document Details
The document details shows the sender and receiver.
Recognition processing
When Trading Networks receives an inbound document, the first
step is recognition processing.It determines the TN document type to
use.
After determines the TN document type, TN uses the matching TN
document type to determine the document attribute values to
associate with the document and the initial list of pre‐processing
actions to perform against the document.
The final step of recognition processing is to form a BizDocEnvelope
that contains the original document, the extracted attribute values,
and additional information that Trading Networks requires for routing
and processing the document.
Recognition processing varies based on whether the inbound
document is an XML document or a flat file document.
PR invoking the Following Service
Steps to Convert bizdoc to Document
■ Processing Rule invokes the service.
■ Retrieve the document from TN .The Document is in Bizdoc format.
■ Use wm.tn.doc.xml:bizdocToRecord Service to convert the bizdoc
format to document format.
■ To Exchange the sender and receiver Id.
■ After changing the document ,the document is send to TN.
Delivery Settings In Partner Profile
Set the http URL Address
Go to MywebMethods->Administration->Partner profiles->Delivery settings->Add delivery
method->set the protocols->ok.
Deliver tab settings
PR Action-Deliver Document

Go to TN Console->type the name->select Deliver document by->

select immediate delivery->select the http protocols->ok.
Steps to send Ack to Partner
■ The changed document is send back to TN
■ Invoke the PR and deliver the document to partner through http.
Overview of Delivering Documents
Trading Networks can deliver the documents using one of the following
delivery option.
Suppose We specify with Deliver Document By processing action in a processing rule:
■ Immediate Delivery: TN attempts to deliver a document directly to the receiving
partner. We can create immediate delivery methods using the standard delivery
methods such as HTTP and FTP.
■ Scheduled Delivery: TN queues documents to be delivered at scheduled times. We
define scheduled delivery queues in Trading Networks.
■ Queued for polling: TN places the document in an internally‐defined queue. The
receiving partner later polls for documents, and Trading Networks returns all the
documents in the queue for which that partner is the receiver.
■ Receiver’s Preferred Protocol: TN looks up the receiver’s profile and uses the delivery
method that is identified in the profile as the preferred delivery method.
Status of Received Document
Viewing of Document details:
Thank You

36