ADS Message Types Reference

This chapter presents detailed reference information that you need to use Cisco AON Development Studio (ADS) to assign message types.

Note For more information on implementing an AON network, see the following:

–

AON Installation and Administration Guide (for information on the AMC server and nodes)

–

AON Programming Guide (for information on custom Bladelets, custom adapters, and application program interfaces)

Information About Message Types

A message type is a filter that determines what type of message a PEP is to process. An AON node identifies a message of interest based on the details you specify in a message type. These details, which can include items such as message content, IP addresses, or message headers, are used to trigger the associated PEP. They can also be used to trigger encoding and message delivery properties.

Message Type Window and Dialog Boxes

Common tasks involving creating PEPs are discussed in "Getting Started with Cisco ADS" chapter. This section describes how to assign message types.

You assign message types by means of the Message Type Definition window ( Figure 5-1) and subsequent dialog boxes.

Message Type Choices

Note

•

Only the name is a required field. Other fields are optional, although you will want to configure as many fields as possible to ensure that the node properly identifies messages of interest.

•

Many of the following windows allow you to specify values in one or more of the following ways:

Table 1 Message Type Definition Window
Field	Description
Name	Name for the message type.
Message Classifier	Message classifier. IP address and port of the originator and destination of a message. Must already be configured on the AMC server. The full path in AMC is AMC > Network Nodes > Configure > ACL/Classifier.
URI	Uniform resource identifier (URI) for the message.
Rule Type	Rule type: •Parameter Rules—Identify messages based on data contained in their URLs. •Header Rules—Identify messages based on data contained in their headers. •Content Rules—Identify messages based on content in the message body.
Rules	Rule, typically with the following components: •Item that the node should identify •Equals or Not Equals •Value associated with the item The following example shows an XPath-expression content rule: `//PO/poRequestInfo[1]/poRequest/purchaseInvoiceNumber equals 100000` When the node receives an XML message in which the invoice number equals 100000, the message is further processed by the associated PEP and other policies. Note Due to limitations within the Windows user interface, it is possible to unknowingly include spaces before or after an expression, especially if you are pasting a lengthy string from another application. These extra spaces can cause processing errors when actual messages arrive without the spaces. To avoid including extra spaces, check the "Trim trailing and leading spaces..." box.
PEP	Existing PEP to be used to process messages identified by the message type.
Encoding	Encoding property that defines how and when a message is to be compressed. This must already be configured on the AMC server. The full path in AMC is Properties > Application > Node > Edit Properties > Encoding.
Delivery	Delivery property that affects the ordered and reliable delivery of messages to destinations. Depending on the configuration, multiple messages can be delivered in a predefined order, and the node continues attempting to deliver a message until successful. This must already be configured on the AMC server. The full path in AMC is Properties > Application > Node > Edit Properties > Delivery Connection.
QoS	Mapping real Application QoS value to a ToS/DSCP value using a global policy in AMC. This policy is available under Application. This must already be configured on the AMC server. The full path in AMC is Properties > Application > Global > QoSMapping. Note If you do not choose an application QoS value for an AON message then by default Application QoS is set to the DSCP value of 0 (zero).

Table Of Contents