WebSphere Message Brokers
File: ad06130_
Writer: Terry Cowling

Reference topic

This build: July 31, 2007 21:22:19

Global group logical properties

Valid children in a global group that depend on both Composition and Content Validation are shown in MRM content validation.

Property Type Meaning
Name String Specify a name for the object when you create it.

Names can consist of virtually any alphanumeric character including the letters A through Z, a through z and the digits 0 through 9.

They may also include the following punctuation characters;
  • - the hyphen
  • _ the underscore
  • . the period

Names can only start with a letter or the underscore character and not with a number, hyphen or period.

Names beginning with xml or any variant (for example XmL) are reserved by the XML standards specification.

Further details of naming conventions and allowable characters can be found in the Extensible Markup Language (XML) specification that can be found on the World Wide Web Consortium (W3C) Web site.

Composition Enumerated type

Define the order, and the number of occurrences, of the elements and groups in your messages. Composition does not affect the attributes in a complex type.

Select from:

  • Empty
  • sequence. If you select this option, you can define members that are elements or groups. These members, if present, must appear in the specified order in the message. They can repeat, and the same element or group can appear more than once.
  • choice. If you select this option, you can define members that are elements or groups. Exactly one of the defined members must be present in the message, and can repeat.

    Use this option if you want to model C unions and COBOL REDEFINES in a Custom Wire Format, or an XML DTD element that uses choice in an XML Wire Format, or a SWIFT field that has more than one option.

  • all. If you select this option, you can define members that are elements; groups are not allowed. The elements in an all group can appear in any order. Each element can appear once, or not at all. An all group can only be used at the top level of a complex type - it cannot be a member of another group within a type.
  • unorderedSet.

    This option is supported only by the MRM domain.

    If you select this option, you can define members that are elements. The elements can repeat but the same element cannot appear twice in the list of members. The elements can appear in any order in the message.
  • orderedSet.

    This option is supported only by the MRM domain.

    If you select this option, you can define members that are elements. The elements can repeat, but the same element cannot appear twice in the list of members. The elements must appear in the specified order in the message.
  • message.

    This option is supported only by the MRM domain.

    If you select this option, you can define only messages as members. Each member can repeat, but the same message cannot appear twice in the list of members. Like choice, only one of the defined members can be present in a message.

    Unlike choice, when writing a message, if the complex type or group has more than one member, the bit stream is not padded to the length of the longest member.

    Use this option to model multipart messages, which are used in some industry standards, for example, SWIFT. For more information, see the section on multipart messages in Multipart messages.

Content Validation Enumerated type

Content Validation is used only by the MRM domain. If validation is enabled in your message flow, Content Validation specifies the strictness of the MRM validation for members of a complex type or group. See MRM content validation for further details.

Options:
  • Closed. The complex type can only contain the child elements that you have added to it.
  • Open Defined. The complex type can contain any valid element defined within the message set.
  • Open. The complex type can contain any valid element, not just those that you have added to this complex type.

See Combinations of Composition and Content Validation for further details of these options.

Related concepts
The message model
Related tasks
Working with message model objects
Related reference
Message model object properties
Logical properties for message model objects
Message model object properties by object
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:22:19

ad06130_ This topic's URL is: