Message Sets: Message set resources

Resources in a message set are created as files, and are displayed under the message set folder in the Application Development view.

  • Message set file messageSet.mset

    There is always one, and only one, messageSet.mset file in a message set. This file contains message model properties that are common to all the content of the message set. It is also where you define the physical formats that you want for this message set. These can be Custom Wire Format (CWF), Tagged Delimited String Format (TDS), and XML Wire Format (XML).

    The file is created for you when a new message set is created, and you manipulate its content with the Message Set Editor.

  • Message definition files that have the suffix .mxsd

    You can have many message definition files in a message set. Each file contains the logical model and the associated physical model, in XML Schema form, for a group of related messages.

  • Deployable WSDL files that have the suffix .wsdl

    These files are used by the SOAP domain. You can have many WSDL files in a message set.

  • Message category files that have the suffix .category

    These files are optional. You can have many message category files in a message set. A message category provides another way of grouping your messages, perhaps for documentation purposes.

When you have completed the resources in your message set, you can generate the content of the message set in a form that can be used by an integration node parser or an application. This might be:
  • a message dictionary for deployment to an integration node
  • XML Schema for use by an application building XML messages, or for deployment to an integration node
  • Web Services Description Language (WSDL) for a web services client, or for deployment to an integration node
  • documentation to give to programmers or business analysts