Overview of XML and ROD documents

The Data Interchange Services client mapping specialist can create document definitions for XML and record-oriented data documents and then create transformation maps that change one type of document into another.

XML documents

XML documents are defined by either an XML DTD or an XML schema. The Data Interchange Services client mapping specialist creates a transformation map based on the DTD or schema that describes how to translate the XML document to another format. An XML document can be transformed into another XML document, a record-oriented data document, or an EDI transaction.

ROD documents

The term record-oriented data (ROD) refers to documents that conform to a proprietary format. The Data Interchange Services client mapping specialist defines a ROD document definition, which refers to the way a business application structures data in a document. After a document definition is defined, the mapping specialist can create a map to transform the ROD document into another ROD document, an XML document, or an EDI transaction.

Splitters and multiple documents

XML or ROD documents can enter the hub as individual documents or as a group of documents within the same file. Multiple documents might be put in the same file when, for example, a scheduled job at the participant or Community Manager periodically uploads documents to be sent. If multiple XML or ROD documents arrive in one file, the Receiver calls the associated splitter handler (XMLSplitterHander or RODSplitterHandler) to split the set of documents. (The splitter handlers are configured when you create a target. See Preprocess for information.) The documents are then reintroduced into the Document Manager to be processed individually.

Note: The sender and receiver IDs must be part of the ROD document definition associated with the transformation map. The information necessary to determine the document type and dictionary values must also be present in the document definition. Make sure that the Data Interchange Services client mapping specialist is aware of these requirements when creating the transformation map.

Multiple EDI interchanges can also be sent in one file. If multiple EDI interchanges arrive in one file, the Receiver calls the EDISplitterHandler to split the set of interchanges. The interchanges are then reintroduced into the Document Manager to be processed individually.

Note: Splitting is performed on the interchange, not on the individual transactions within the interchange. Transactions within the interchange are de-enveloped.

Copyright IBM Corp. 2003, 2005