Shared libraries can contain XML or DFDL schema files. Shared libraries can also access schema files that are contained in referenced shared libraries, either by using the import or include options.
When the first shared library is deployed, a model is compiled that contains all the schema files in that shared library and any referenced shared libraries.
The application or applications that reference the shared libraries can also contain their own schema files. A separate model is compiled that contains only the schema files from the application. The schema files in the application cannot access schema files in a shared library.
To validate against the deployed schema files, the compiled representation of the XML schemas is passed to the parser. Therefore, you must specify the name of the shared library that contains the appropriate compiled model. For example, when you create a message flow, you can configure the input node to validate against the message model for a shared library that is called hl7 by specifying a value of hl7 in the
Message model property on the
Input Message Parsing panel of the node. To access the
Message model value in the
Validate node, you can set the
MessageSet field of the Properties tree by including the following ESQL statement in a
Compute node:
SET OutputRoot.Properties.MessageSet = '{Shared LibraryName};'
You can use the following methods to view the relationships between applications and shared libraries:
- The mqsilist command
- User trace and system trace
- The web user interface
- The Integration Nodes view of the IBM® Integration Toolkit