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 predefined 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:

Predefined message properties These message properties are always prefixed with ias_ or IAS_. See Predefined message properties.
Custom message properties These are message properties that you defined. You cannot prefix them with ias_ or IAS_. See Custom message properties.

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

Predefined message properties

Some message properties have been predefined for your convenience. Predefined properties can be read but should not be set. The predefined message properties are:

ias_Adapters
ias_DeliveryCount
ias_MessageType
ias_RASNames
ias_NetworkStatus
ias_Originator
ias_Status
ias_StatusTime

For details about message properties, see Message properties.

Discuss this page in DocCommentXchange.