In this section: |
How to: |
Schema sets can now be configured, which consist of logically related schemas in a hierarchical structure. This provides support for importing schemas within schemas. In iIT, a schema set has the same role as a standalone schema, and is lifecycle managed.
To create a schema set:
The New Schema Set window appears and a unique ID is assigned to the new schema set instance, as shown in the following image.
Note: Existing schemas can be converted to schema sets from the main menu. The content of the schema set can then be edited using the Integration Explorer.
To edit a schema set:
A sample .iwresource file is provided below. Notice that there is no <file> element specified.
<?xml version="1.0" encoding="UTF-8"?> <cli:IWResource xmlns:cli="http://registry.iwaysoftware.com/xml/client"> <Name> Dtp Schema Set </Name> <Type>schema</Type> <File>schema</File> <Description/> <GUID>88D1081F11CF09F9D1A17E0E26037964</GUID> <targetServer>7.0.0</targetServer> </cli:IWResource>
To export managed schema from iSM using iWay Explorer:
The .xsd file node for the schema is created, as shown in the following image.
To export managed schema from iSM using Integration Explorer:
Note: All managed and unmanaged schemas have the Convert to Schema Set option.
The .xsd file node for the schema is created, as shown in the following image.
You can assign a schema set for a Start object in a process flow to describe the input document.
The New Process Flow Wizard opens and displays the General Properties pane, as shown in the following image.
The new process flow is created in the designer workspace with a default Start object, as shown in the following image.
The Properties tab in the lower pane displays the properties for the selected Start object.
The Select Schema dialog box opens, as shown in the following image.
The input schema properties for the Start object are now defined in the Properties tab, as shown in the following image.
You can also assign a schema set for an End object in a process flow to describe the output document.
To import a schema set from a process flow:
The Import window appears, as shown in the following image.
The Import Schema Set window appears.
There are two ways to import schema sets from the file system to the workspace. You can:
In both cases, the Schema set root folder is the iwresource folder.
The Select Schema window appears.
On the Start or End object of a process flow, you can pick a schema set or a standalone schema.
In the XML for the process flow, the schema entry on the Start object does not distinguish between the schema set and standalone schema.
VALUE="schemas/3C07F99DD76EF24785344FD6AAEAB771/ExchangeSchemaLibrary /wsdl-schema/exchange/dtp/Dtp.xsd"
The following sample shows the dependency entry in .iwresource:
<Dependency> <Name>Dtp</Name> <Type>schema</Type> <GUID>3C07F99DD76EF24785344FD6AAEAB771</GUID> <Path>/schemaLis/ExchangeSchemaLibrary/wsdl-schema/exchange/dtp/Dtp.xsd </Path> <UsageCount>1</UsageCount> </Dependency>
Notice that the GUID value matches that of the schema set.
When an unmanaged schema in the workspace is used on a process flow, the schema is converted to managed format.
When a schema set is published to iSM, either independently or as a dependency of a process flow, all the schema files in the package are published. Each schema file is wrapped in a server interface ComponentFile that has a path attribute set to its relative path in the package.
When the process flow publisher requests the schema path from the schema publisher, the schema publisher navigates through the resource tree until it finds the .iwresource file. Then, it publishes all resources from that level down.
When the schema is exported from the registry, it goes to the default folder for schemas. A container folder is created with the name attribute of the schema set. All schema files are wrapped in server interface ComponentFiles, with paths defining where to place them within the schema set.
A schema set can be deployed as a dependency of a process flow. The deploy support is similar to publish, in that each schema file can be deployed relative to the parent folder.
Similar to the schema publisher in the Publish section, when the iIA builder encounters a schema file, it navigates the resource tree until it finds the .iwresource file and takes contents from that level down into the iIA package.
The console deployment mechanism can deploy all folders and files of a schema type, while preserving the directory structures.
|
iWay Software |