Before you begin
Tip: In WebSphere® Message
Broker Version 8.0 and
later, message model schema files contained in applications,
integration services, and libraries are the preferred way to
model messages for most data formats. Message sets are required if
you use the MRM or IDOC domains. For more information about message
modeling, see Message modeling concepts. For information about
how to create an XML schema, see
Creating an XML Schema file by using the New Message Model wizard.
you must have
completed the following tasks:
Before you begin this task, you should be aware of the following
points:
- If you are importing a collection of related XML Schema files,
you are advised to use the mqsicreatemsgdefs command.
This imports all the XML Schema files in a single operation, and automatically
adjusts the import and include paths.
- If the message set to which you are adding the new message definition
file does have an XML wire format layer, but no namespace
support, the imported schema is modified to remove namespaces. For
this reason, you should enable namespace support before importing
a schema.
- If the message set to which you are adding the new message definition
file does not have an XML wire format layer, but does have
namespace support, only the logical information appears in the model.
For this reason, you should add the physical layer to the message
set before importing the schema. This ensures that the message set
is populated with the settings and values from the schema. The XML
Schema is not modified to remove namespaces.
- If the message set to which you are adding the new message definition
file does not have an XML wire format layer, and does not have
namespace support, only the logical information appears in the model
and the imported schema is modified to remove namespaces.
- If you are working with a message set that does not have namespace
support, you must specify the preferences that apply when you import
a schema into the message set. These preferences allow you to specify
how the importer treats certain individual schema constructs. You
can either reject the schema if any occurrences of the construct are
encountered or modify occurrences of the construct. If you choose
modify, the importer modifies all occurrences of the construct.
- The extension to the XML Schema file must be .xsd in
lowercase.
About this task
The following steps create a completely
new message definition file or overwrite the contents of an existing
file.
To create a message definition from an XML Schema file: