Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Working with Document Types | Creating an IS Document Type | Creating an IS Document Type from an XML Document, DTD, or XML Schema
 
Creating an IS Document Type from an XML Document, DTD, or XML Schema
 
Creating an IS Document Type from an XML Document
Creating an IS Document Type from a DTD
Creating an IS Document Type from an XML Schema Definition
You can create an IS document type based on the structure and content of a source file, such as an XML Schema definition, DTD, or XML document. Keep the following points in mind when creating an IS document type from a source file.
*When you base the IS document type on an XML Schema definition or a DTD, Integration Server creates an IS document type and an IS schema. The IS document type has the same structure and field constraints as the source document. The IS schema contains the elements, attributes, and data types defined in the XML Schema or DTD. The IS document type, which displays the fields and structure of the source document, uses links to the IS schema to obtain content type information about named simple types.
*When creating a field from an attribute declaration, Integration Server inserts the @ symbol at the beginning of the field name. For example, an attribute named myAttribute in the source file corresponds to a field named @myAttribute in the IS document type.
*If an IS document type was created from a source, Designer displays the location of the source in the Source URI property. Designer also sets the Linked to source property to true which prevents any editing of the document type contents. To edit the document type contents, you first need to make the document type editable by breaking the link to the source. For information about allowing editing of elements derived from a source, see Allowing Editing of Derived Elements
*Integration Server does not create IS document types or IS schemas from an XML schema definition (XSD) if the XSD contains a type definition derived by extension and that type definition contains a direct or indirect reference to itself. If Integration Server encounters a type definition that contains a recursive extension while creating an IS document type or an IS schema from an XSD, Integration Server throws a StackOverflowError and does not continue creating the IS document type or IS schema.