| Join wMUsers | Blog at wMUsers | User Control Panel | Site Map | webMethods Jobs |For Employers |
![]() |
![]() |
IntroductionTrading Networks facilitates document exchange between partners or systems within an organization. This article describes how to use profiles, document types and processing rules to define the processing rules of inbound and outbound documents. One limitation of TN that new users often find surprising is the one-to-one nature of TN processing -- a document submitted to TN can be delivered to just one recipient. Various approaches can be used to overcome this limitation:
There are pros and cons to each approach but each can be used successfully. This article details the first option, with the added twist that the intended recipients are unknown to the document publisher. With minor changes to processing rules the presented solution can be applied to the second option as well. One Document, Many RecipientsSometimes it is desirable to send a document to many recipients that have an interest in that document, but the source of the document does not know who these recipients might be. Thus the source cannot provide a list of the profile identifiers needed by TN to do delivery. What is needed is a way to look up the profiles that are to receive documents of a particular type. TN provides the ability to store custom profile attributes, referred to as extended fields. The desire to receive a particular document type can be easily stored in an extended profile field. A service tasked with delivering a document to all subscribers looks up the extended field for all profiles. Based on the extended field setting, the document can be delivered to all subscribers. Step One: Add the Extended Profile FieldAdding an extended field to profiles is easily accomplished using the TN Console. Extended fields have a group and a name. A reasonable convention is to place subscription fields in a group named "Subscriptions" and to name the field using the form docType, where docType is a descriptive name of the document type being subscribed to. For the steps below, we’ll create an extended field named "CustomerChange".
Step Two: Set the Extended Profile Field for Selected ProfilesNow that the extended field is available, we need to set each profile that is to subscribe to our document type. Once again, TN Console provides a simple way to do what we need. The steps below establish a subscription for the "CustomerChange" document for an existing profile named "XYZ Corp." (Refer to the webMethods documentation for profile creation instructions.)
Go Deeper on the Subject: The wMUsers Discussion Forums Rob Eamon is a consultant with SBI and Company and has over 17 years experience in IT-related areas. He has completed several successful integration projects using the webMethods Platform.
Rob can be reached via email at |
| © All Rights Reserved, 2001-2008. |