Chapter 6: Common Topics in Real Time Messaging

Adaptive Server-specific message properties

To help with debugging, monitoring, and so forth, predefined properties specific to Adaptive Server are included in the properties portion of the message. These properties typically handle messages that originate from another Adaptive Server, or are useful in debugging.

Many of these message properties are included only when running diagserver, or when certain trace flags are turned on. All properties beginning with “ASE_” are reserved. They cannot be set using msgsend or msgpublish.

Table 6-2 describes these message properties.

**Table 6-2: Adaptive Server-specific messages**
Property	Description	When to use
ASE_RTMS_CHARSET	Character set encoding of data sent.	Always
ASE_MSGBODY_SCHEMA	The schema describing the message body (payload), or null. This schema is nonnull only if the user sends the message schema as part of msgsend. If ASE_MSGBODY_FORMAT is xml, this property contains the XML schema describing the message body. This schema is not truncated, even if its value exceeds 16K.	Always
ASE_MSGBODY_FORMAT	The format of the message body: xml, string (in server character set), binary, and unicode (unichar in network order).	Always
ASE_ORIGIN	Name of the originating Adaptive Server.	Present with diagserver.
ASE_RTMS_VERSION	Version of Real Time Messaging Services in Adaptive Server.	Always
ASE_SPID	SPID that sent the message.	Present with diagserver.
ASE_TIMESTAMP	The timestamp of Adaptive Server showing the time the message was sent.	Present with diagserver.
ASE_VERSION	Version of Adaptive Server that published message.	Always
ASE_VERSIONSTRING	Version string of the Adaptive Server. Gives information about platform, build type, and so on. Useful for debugging.	Present with diagserver.

These properties are shown for informational purposes only. They may change in the future.

View this book as PDF