Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.0 » QAnywhere » QAnywhere API Reference » Message headers and properties


Message properties

Each message contains a built-in facility for supporting application-defined property values. These message properties allow you to implement application-defined message filtering.

Message properties are name-value pairs that you can optionally insert into messages to provide structure. For example, in the .NET API the pre-defined message property ias_Originator, identified by the constant MessageProperties.ORIGINATOR, provides the message store ID that sent the message. Message properties can be used in transmission rules to determine the suitability of a message for transmission.

There are two types of message property:

  • Pre-defined message properties   These message properties are always prefixed with ias_ or IAS_.

  • Custom message properties   These are message properties that you defined. You cannot prefix them with ias_ or IAS_.

In either case, you access message store properties using get and set methods and pass the name of the pre-defined or custom property as the first parameter.

See Managing message properties.

Pre-defined message properties
Custom message properties
Managing message properties