Predefined and self-defining messages

When you create a message in the IBM Integration Toolkit, you define the fields (Elements) in the message, along with special field types that you might need, and specific values (Value Constraints) to which the fields might be restricted.

When you deploy a message set to a broker, the message model is sent to the broker in a form appropriate to the parser that is used to parse and write the message.

For information about the benefits of predefining messages, see Why model messages?

You can view information about samples only when you use the product documentation that is integrated with the IBM Integration Toolkit or the online product documentation. You can run samples only when you use the product documentation that is integrated with the IBM Integration Toolkit.

You can create and route messages that are self-defining. The best example of a self-defining message is an XML document.

You can also model self-defining messages in the IBM Integration Toolkit. However, you do not need to deploy these message sets to the brokers that support those message flows. For further information about why you might want to model these messages, see Why model messages?.

You can view information about samples only when you use the product documentation that is integrated with the IBM Integration Toolkit or the online product documentation. You can run samples only when you use the product documentation that is integrated with the IBM Integration Toolkit.