Creating an XML Document Type
When you create an XML document type you specify the following:
The destination folder in which you want
Designer to place the generated XML document types, XML fields, IS schemas, and folders.
The source XML schema definition.
Whether or not
Integration Server use the Xerces Java parser to validate the XML Schema definition before creating XML document types.
There are no additional options, making the process of creating an XML document type less complex than that of creating an IS document type.
When you create an XML document type, keep the following information in mind:
You can create only one set of XML document types per folder. If you used folderA as the destination for the XML document types and other assets created for mySchema.xsd, you cannot use folderA as the destination for the XML document types and other assets generated from another XML schema definition. However, you could use a subfolder in folderA as the destination for the XML document type and other assets created for another XML schema definition.
Do not use a folder created by
Integration Server to store assets generated for an XML schema definition as the destination folder for new XML document types.
To create an XML document type from an XML Schema definition in
CentraSite,
Designer must be configured to connect to
CentraSite.
To create an XML document type
1. In the Service Development perspective of Designer, click File > New > XML Document Type.
2. In the Create a New XML Document Type dialog box, select the folder in which you want to save the XML document types, XML fields, IS schemas, and folders generated from the XML schema definition.
3. Click Next.
4. On the Select a Source Location panel, under Source location, do one of the following to specify the source XML schema definition for the XML document type:
To use an XML schema definition in
CentraSite as the source, select
CentraSite.
To use an XML schema definition that resides on the Internet as the source, select
File/URL. Then, type the URL of the resource. (The URL you specify must begin with
http: or
https:.)
To use an XML Schema definition that resides on your local file system as the source, select
File/URL. Then, type in the path and file name, or click the
Browse button to navigate to and select the file.
5. If you want Integration Server to use the Xerces Java parser to validate the XML Schema definition, select the Validate schema using Xerces check box.
Note:Integration Server automatically uses an internal schema parser to validate the XML Schema definition. However, the Xerces Java parser provides stricter validation than the Integration Server internal schema parser. As a result, some schemas that the internal schema parser considers to be valid might be considered invalid by the Xerces Java parser.
6. If you selected CentraSite as the source, click Next. Then, under Select a Schema, select the XML schema definition that you want to use as the source and click Finish.
If Designer is not configured to connect to CentraSite, Designer displays the CentraSite> Connections preference page and prompts you to configure a connection to CentraSite.
7. Click Finish.
Notes:
Integration Server uses the internal schema parser to validate an XML schema definition. If you selected the
Validate schema using Xerces check box,
Integration Server also uses the Xerces Java parser to validate the XML Schema definition. With either parser, if the XML Schema does not conform syntactically to the schema for XML Schemas defined in
XML Schema Part 1: Structures (which is located at
http://www.w3.org/TR/xmlschema-1),
Integration Server does not create an XML document type. Instead,
Designer displays an error message that lists the number, title, location, and description of the validation errors within the XML Schema definition. If only warnings occur,
Designer generates the XML document type and the other assets.
When validating XML schema definitions,
Integration Server uses the Perl5 regular expression compiler instead of the XML regular expression syntax defined by the World Wide Web Consortium for the XML Schema standard. As a result, in XML schema definitions consumed by
Integration Server, the pattern constraining facet must use valid Perl regular expression syntax. If the supplied pattern does not use proper Perl regular expression syntax,
Integration Server considers the pattern to be invalid.
Note:
If the watt.core.datatype.usejavaregex configuration parameter is set to true, Integration Server uses the Java regular expression compiler instead of the Perl5 regular expression compiler. When the parameter is true, the pattern constraining facet in XML schema definitions must use valid syntax as defined by the Java regular expression.