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

Self-defining elements and messages

An instance element is predefined if it is possible for the parser to find a matching element definition in the message model with an appropriate set of properties and in the correct context. Otherwise, it is self-defining. Similarly, an entire message is self-defining if no corresponding message is present in the message model.

Self-defining elements can be used only when the format of the message is a self-describing one, such as XML or JSON. For general text or binary formats (for example, comma separated), you must ensure that your message model defines every message and every element that must be parsed.

If you have chosen not to model your messages, or you have a model but have chosen not to deploy it to the broker, all messages and elements are self-defining. In this situation, you cannot use message definitions to influence the parsing and writing of elements; the self-defining elements are parsed and written according to the default behavior of the parser and writer.

Self-defining elements, and all elements within a self-defining message, are not validated against value constraints, and any missing fields are not assigned default or fixed values, and all data is assumed to be string type unless the parser is able to deduce the type in a reliable manner.


ad10520_.htm | Last updated Friday, 21 July 2017