Show TOC

Procedure documentationPrioritizing the Processing of Messages Locate this document in the navigation structure

 

Caution Caution

SAP NetWeaver Administrator for PI and all monitoring tools it includes are not supported for use in production scenarios. We recommend to use Runtime Workbench for PI monitoring in production scenarios. The information provided below is only for reference.

For more information, see SAP notes 1446507 and 1247043.

End of the caution.

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 SAP NetWeaver Administrator for PI and have chosen an Adapter Engine as component.

Note Note

You can also use message prioritization locally, if you use a non-central Adapter Engine.

For this, choose   SOA Management   Monitoring   PI Message Prioritization   in your local SAP NetWeaver Administrator.

End of the note.

Procedure

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

  1. Choose Message Prioritizing.

    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 using enhanced input help.

    So long as you have not saved any changes to the existing rules you can discard the changes at any time by reloading the rules.

  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 enhanced 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 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.

End of the example.

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.