SenderID and ReceiverID System Attributes
When Trading Networks has a value for SenderID and ReceiverID, you can perform these tasks:
Use the sender or receiver to determine whether a document is a duplicate (Check for Duplicate Document pre-processing action).
Use the sender or receiver as criteria for determining the processing rule to use for the document.
Deliver a document.
Search for the document in
My webMethods based on sender or receiver.
Have a business process perform steps based on sender or receiver.
On the Extract panel, select the external ID type (for example, DUNS) for each attribute so that Trading Networks can match the externals ID in TN_parms/SenderID and TN_parms/ReceiverID with the external IDs in the profiles. This is how Trading Networks verifies the identities of the sender and receiver. When Trading Networks finds a match, it transforms the externals ID in TN_parms/SenderID and TN_parms/ReceiverID into its internal IDs before storing them in the BizDocEnvelope.
Be sure to select an external ID type that your partners specify in their profiles. You can choose from a list of external ID types. If the external ID type you need is not in the list or if you have agreed on a non-standard format with a trading partner, select the external ID type Mutually Defined and add an appropriate ID value.
You can use the
Retrieve SenderID from session option as an alternative way to set the value of the SenderID system attribute. When this option is set, rather than looking into
TN_parms\SenderID for the value to use,
Trading Networks uses the connected user. This means that when the client sends the document to
Trading Networks, it has to present credentials (an
Integration Server user name and password). That user name/password pair directly correlates to a
Trading Networks partner. When you create a profile, you associate one or more
My webMethods user accounts with the profile. For more information on associating
My webMethods user accounts, see
Associate
My webMethods User Accounts with a Profile. So, if
Retrieve SenderID from session is set to true in a document type,
Trading Networks determines the sender of the document based on the user account you associate with the profile, finds the profile (and therefore the internal ID), and puts that value in the BizDocEnvelope.
Important: | When you resubmit a flat file document with the Retrieve SenderID from session option selected, the resubmit might fail. If you set up Sender criteria in a processing rule, the first time the document arrives, the criteria matches a processing rule based on the SenderID value that is determined through the Retrieve SenderID from session option. However, if you resubmit the document, that same processing rule will not be selected based on the Retrieve SenderID from session option. This is because when you resubmit the document from My webMethods, the user account that you used to log in to My webMethods (for example, Administrator), will not match the Sender criteria of the processing rule. It could end up matching another processing rule and then go through completely different processing. |
