Integration Server 10.15 | Publish-Subscribe Developer’s Guide | Synchronizing Data Between Multiple Resources | Defining the Structure of the Canonical Document
 
Defining the Structure of the Canonical Document
The following diagram highlights the part of data synchronization that uses the canonical document.
To define the structure for canonical documents, you include a superset of all the fields that are required to keep data synchronized between the resources. Additionally, you must include a field for the canonical ID.
The following table lists options for defining the structure of a canonical document:
Use a...
Benefit
Standard format (e.g., cXML, CBL, RosettaNet)
A standards committee has already decided the structure, and you can leverage their thought and effort.
Complete custom format
You define a unique structure that you tailor for your organization. The document structure might be smaller, and therefore easier to maintain because it only contains the fields your enterprise requires. Also, the smaller size has a positive effect on performance.
Custom format based on a standard
You define a unique structure by starting with a structure that a standards committee has defined. You can take advantage of the thought and effort already put into deciding the standards-based format. However, you can delete fields that your enterprise might not need and add additional fields that are specific to your enterprise.
After determining the fields that you need in the canonical document, use Software AG Designer to define an publishable document type for the canonical document. For more information about how to create publishable document types, see webMethods Service Development Help.