IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Message Sets: Creating a message set

Use the New Message Set wizard to create a message set.

Tip: A message set is the original container for message models used by IBM® Integration Bus. In WebSphere® Message Broker Version 8.0 and later, message model schema files contained in applications and libraries are the preferred way to model messages for most data formats. Message sets continue to be supported, and are required if you use the MRM or IDOC domains. If you need to model data formats for use in the MRM or IDOC domains, you must first enable message set development in the IBM Integration Toolkit. For more information, see Enabling message set development .

The New Message Set wizard also creates a new message set project.

Note: You can also use a Quick Start wizard to create a message set, a message set project, and other resource files that you need to create a new application.

The New Message Set wizard allows you to select what kinds of message format you want to model in your message set. The message domain and the physical format created is inferred from the selection that you make. Note, however, that you can change the inferred domain using the message set editor.

The options are:
  • XML documents (general)
  • Web services (SOAP)
  • Binary data (for example, C or COBOL structures)
  • Text data (for example, CSV, SWIFT, or HL7)
  • MIME documents other than Web services
  • Data for WebSphere Adapters
  • Database records

The default value is XML documents (general).

Below the list of message formats there are check boxes corresponding to each of the message formats. The check box corresponding to the message format that you selected is not available, but you can select any of the other check boxes to add other message formats to your message set.

If you later select a different default message domain, the checked state for the domain that you originally selected as the default does not change, but the check box is enabled.

As you can now select more than one message domain you can, for example, use the default value of XML documents (general) together with Binary data (for example, C or COBOL structures) and Text data (for example, CSV, SWIFT or HL7). This results in the selection of the XMLNSC and MRM domains (to handle non-XML documents) within the same message set if you require this functionality.

The mapping between the selection, the domain, and the wire format created is described in the following table:
Selection Inferred message domain Physical format created
XML documents (general) XMLNSC XML
Web services (SOAP) SOAP and XMLNSC XML
Binary data (for example, C or COBOL structures) MRM CWF
Text data (for example, CSV, SWIFT, or HL7) MRM TDS
MIME documents other than Web services MIME None
Data for WebSphere Adapters DataObject None
Data for CORBA DataObject None
Database records DataObject None
Depending on your selection, an appropriate IBM supplied message will be imported into the message set.
Note: The XML physical format is created only in case the user switches to MRM XML.
If you click Finish on the second page of the New Message Set wizard, the message set that is created has the following default property values:
Property Default value
Message Domain XML documents (general)
Physical Format XML Wire Format (XML1)
Namespace support Enabled

To create a new message set:

  1. Switch to the Integration Development perspective.
  2. Open the New Message Set wizard. To do this, right-click anywhere in the Application Development view, then click New > Independent Resources > Message Set.
  3. In the Message set name field, type the name for the message set that you are creating. The name that you type is also displayed in the Message set project name field.
  4. Optional: You can choose a different message set project name; to do this, type this name into the Message set project name field.
  5. Optional: You can specify a directory in which you want to store the project contents. If you do not specify a directory, the default workspace is used. To specify a directory, first clear the Use default check box, then either type into the Directory field the location of the directory, or click Browse to see a list of the folders that you can choose from for the location of the directory.
  6. Optional: If you want to create a new message set whose definition is based on existing message set, click Message Set in the Copy message set contents from another message set pane and choose from the list of message set definitions that are shown; then click Finish. The new message set (and the message set project that contains it) is created immediately and the New Message Set wizard automatically closes.
  7. Optional: If you want to create a message set whose definition is not based on an existing message set, click Next. You are presented with the next pane which allows you to choose the type of message data that you want to process.
    1. Expand the list shown under Select the type of message data that you will be working with most often and choose a value from the list shown. The value that you choose determines the default message domain of the message set. If you choose XML Documents (general), the default message domain XMLNSC is used.
    2. Optional: You can now select additional types of message data. Under Select any other types of message data that you will be working with there are check boxes for each of the following message data types:
      • XML documents (general)
      • Web services SOAP
      • Binary data (for example, C or COBOL structures)
      • Text data (for example, CSV, SWIFT or HL7)
      • MIME documents other than Web services
      • Data for WebSphere Adapters
      Note: These check boxes correspond to the list of data types from which you chose the data type that you will be working with most often, but the check box that corresponds to the data type that you chose from that list is not available.
      By default, all these check boxes are cleared. You can select any, or all of these check boxes, to add the corresponding data types to your message set.

      If you select the check box for text data, either for the type of message data that you will be working with most often or as another type of message data that you will be working with, you can additionally choose from the displayed list of text messaging standards. This list is the same as that given in the description of the Messaging Standard property in Message Sets: TDS Format message set properties.

    3. Click Next. A new panel is displayed that summarizes some information about the message set that you have created. Specifically, it lists:
      • Supported message domains
      • Physical formats to be created
      • IBM supplied messages to be imported
  8. Click Finish on this page to create the message set, and the message set project that contains it. The New Message Set wizard closes.
After the New Message Set wizard finishes, the message set editor is opened.
You can now create some message definitions in the new message set. You can either create new message definitions from scratch, or create them based on existing artifacts such as WSDL, XSD, DTD, C, COBOL files, or EIS metadata. Use the Message Definition File wizard and the Message Definition File From wizard to help you with this.

ad20808_.htm | Last updated Friday, 21 July 2017