Entering content frameProcedure documentation Defining Rules and Actions for Error Handling Locate the document in its SAP Library structure

Use

In the Integration Engine, you can specify rules for error handling in inbound messages that trigger particular actions. Rules and actions each refer to attributes of the message header.

For each conditioned action, you can define one or more conditions that you then link conjunctively (using a logical AND relation). You can assign more than one action to a rule.

Recommendation

Only create a limited number of conditioned actions to maintain a clear overview of their dependencies and the network of their actions. In production operation, do not create any conditioned actions, otherwise each inbound message is checked by the system to see whether it fits any of the conditions.

Prerequisites

In the menu Integration Engine, you chose Administration ® Settings for Error Handling and the system now displays a screen of the same name.

Creating Conditioned Actions

The procedure for creating a conditioned action is divided into the creation of one or more conditions and one or more actions. To create a conditioned action, proceed as follows:

  1. Choose Create.

    2. The system displays a dialog box with two tab pages. Choose the tab page Rules. The first line in the table displayed is ready for you to enter data. Create a new rule.

    The rule you want to create is activated automatically (This graphic is explained in the accompanying text). The user and the validity period of the rule (date and time) are predefined. If the validity period expires, the rule is automatically deactivated (This graphic is explained in the accompanying text).

  2. Using the input help, select a rule, for example USERNAME.
  3. Enter an argument (a value) for the selected rule, for example SMITH.
  4. If necessary, change the date and time for the end of the validity period for the rule.
  5. To create additional rules, choose Create for each further rule and make the corresponding entries in each of the selected lines.
  6. To deactivate a rule that you created, choose Activate <-> Deactivate (This graphic is explained in the accompanying text).
  7. To delete a rule from the table, select the corresponding line and choose Delete.
  8. Once you have finished creating your rules, choose the tab page Actions.

    9. The first line in the table displayed is ready for you to enter data. Create a new action. The user and the date of the last change are predefined.

  9. Using the input help, select an action. You can choose from the following actions:

Allows you to log the individual processing steps of a message in the trace segment of this message. Display the trace information for messages that were persisted in the database using monitoring.

Note

The action Tracelevel overrides settings for trace that you made for the pipeline.

Allows you to also write the trace information for the message to a file. In the SAP directory /global, the system creates the file TRC_<msgid>.txt, where <msgid> contains the respective message ID.

Allows you to control whether a message is logged in the database following certain processing steps. You can then display the log using monitoring.

Note

Only set the action Logging if you have not already activated or deactivated logging explicitly at pipeline, pipeline element, or pipeline service level.

Allows you to also write the message log to a file. In the SAP directory /global, the system creates the file MSG_<msgid>_<pid>_<msgvs>.txt, where <msgid> contains the respective message ID, <pid> contains the ID of the pipeline involved, and <msgvs> contains each logged version of the message.

Allows you to activate a breakpoint set in code that then starts the debugger at this location. You must also activate HTTP debugging for messages that enter the Integration Engine through the HTTP inbound interface.
  1. Using the input help, select an argument (a value) for the action.
  2. If necessary, create further actions by choosing Create for each additional action and making the corresponding entries.

    3. Note

    Each action may only occur once for each conditioned action.

  3. To delete an action from the table, select the corresponding line and choose Delete.
  4. Save the created actions and rules.

The system displays the conditioned action you created in the screen Settings for Error Handling; you can change or delete the condition at this point.

If you have created multiple conditioned actions, the system automatically links them together disjunctively (using a logical OR relation). If several of the conditioned actions apply, the system executes them in the same sequence that they are displayed on the screen Settings for Error Handling. For multiple identical actions, this means that the results of the last executed action take precedence each time.

Deleting Conditioned Actions

To delete a conditioned action, choose Delete in the corresponding block on the screen Settings for Error Handling. The system removes the conditioned action from view.

Changing Conditioned Actions

To change a conditioned action, choose Change in the corresponding block on the screen Settings for Error Handling. The system displays a dialog window with the tab pages Rules and Actions, where you can make changes to the conditioned action.

 

 

Leaving content frame