Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Trading Networks Administrator's Guide | Understanding webMethods Trading Networks | Asset Definition | Document Types | XML Document Types
 
XML Document Types
The XML document type definitions are listed in the table as follows:
Definition
Description
Document recognition criteria
Content that an inbound XML document must have to be a match for the XML document type. You can specify one or more of the following:
*Root tag the document must have.
*System or public identifier from the DOCTYPE declaration the document must have.
*Nodes and, optionally, values the document must have. You define XML Query Language (XQL) queries that Trading Networks executes to find the nodes and values.
*Pipeline variables (that is, variables inserted into the pipeline by the service that sends the document to Trading Networks) and, optionally, values the variables must have.
Attribute extraction
System and custom attributes to extract from the document. You define XQL queries that Trading Networks executes to extract the attributes. You can also specify transformations for extracted attributes; for example, you might want to transform an extracted string value into all uppercase characters.
Pre-processing actions
A document type can specify one or more of these actions:
*Format as IS Document Type action, to transform the document into an IS document that can be parsed into an IData object. An IData object is a collection of name/value pairs on which services can operate. An IData object can contain any number of elements of any valid Java objects, including additional IData objects.
*Verify Digital Signature action, to make sure the signed body of the document arrived unchanged and the sender is who it claims to be. Trading Networks checks the sender by matching the certificate from the digital signature to the certificate in the partner’s profile.
*Validate Structure action, to validate the structure of the document against a specified schema.
*Check for Duplicate Document action, to check whether Trading Networks has already received the document. Trading Networks saves the results of the check to the pipeline, so you can use the results in the Save Document to Database pre-processing action (below) to save only unique documents, and in processing rule actions.
*Save Document to Database, to save the document to the Trading Networks database. For example, you save documents to the database when you want to make multiple attempts to deliver documents to partners.
*Indicate whether to use a processing rule to further process the document. You might not want to use a processing rule if you want to simply persist the document to the Trading Networks database, or to process the document using a business process instead of a processing rule. For information about business processes, see Business Process Definition.