Importing from other model representations to create message definitions

One way to populate your message set with message definitions is to import existing application message formats. You can import the following message formats into a message set:

When you import one of these formats, a new message model is created consisting of the elements, attributes, groups and types needed to represent your message format. You choose the name of the message definition file; if it already exists the content is deleted and recreated as part of the import operation.

The new message model created can consist of both logical and physical information, if appropriate physical formats exist in the message set at the time of the import.

All imports can be performed using the New Message Definition File wizard. In addition you can also import C header files, COBOL copybooks, XML DTDs, or XML Schema using the mqsicreatemsgdefs command line utility. mqsicreatemsgdefs allows you to import several message format files in a single operation, and allows you to create a new message set (based on an existing message set) into which the message definition files will be placed.

WSDL definitions can be imported using the mqsicreatemsgdefsfromwsdl command line utility. This will only import a single WSDL definition at a time.

Client application access to messages

Client applications also need access to message definitions to be able to construct messages they send, and interpret messages that they receive.
  • If the message formats have been imported from C or COBOL structures using the workbench, your applications can continue to use the same C and COBOL data structures that were imported to create the message dictionary that will be used by the brokers.
  • If the messages are self-defining XML, the client applications must construct valid messages using the structures that can be understood be the recipients of the message.