Show TOC

Prioritizing the Processing of MessagesLocate this document in the navigation structure

Use

For message processing on the Adapter Engine you can define rules according to which messages with different priorities (low, normal, or high) are processed. Use the attributes from the message header to define such rules.

Prerequisites

You have started the Runtime Workbench , are in component monitoring, and have selected an Adapter Engine as the component.

Procedure

To be able to define rules for a prioritized message processing, proceed as follows:

  1. On the Status tab page, choose Message Prioritization . You need to enter the user and password for the selected Adapter Engine.

    The rules are listed once you have defined these prioritization rules. You can delete or edit any other rules available.

  2. If you want to change a rule, select the rule and make the required changes.

    As long as you have not saved any changes to available rules, you can reject them at any time- Choose Reset for this. All changes that have not yet been saved will be reset.

  3. If you would like to delete a rule, select the rule and choose Delete .

  4. If you would like to define a new prioritization rule, choose Create .

  5. Give the rule a name and select the required priority.

  6. Enter the required header attributes.

    You can enter an asterisk (*) here for this. There is input help available for each attribute.

  7. Save your new/changed rules.

You cannot define any conflicting prioritization rules. When saving such rules you receive an error message.

Example

The rule R1 contains the value pair (A1,B*) and rule R2 contains the value pair (A*,B1). A message with the value pair (A1,B1) would access both rules and cause a conflict. Therefore rule R2 would be rejected during the saving process and an error would be produced.

A rule R3 with the value pair (A*,B*) would conflict with neither R1 nor R2.

Result

Once you have defined the prioritization rules, the Adapter Engine searches for a suitable rule for this message using the header attribute of an incoming message.

  • If a rule is found, the message is processed according to the priority defined within it.

  • If multiple rules are found, it accesses the more specific rule.

  • If no suitable rule is found, the message is processed with normal priority.