Defining Conditions and Actions for Troubleshooting 

Use

In the Integration Engine , you can specify conditions for troubleshooting inbound messages that trigger particular actions. Conditions 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 using a logical AND relation. You can assign more than one action to a condition.

If you create multiple conditioned actions, the system automatically links them together 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 Troubleshooting Settings. For multiple identical actions, this means that the results of the last executed action take precedence each time.

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.

The system displays the conditioned action you created in the screen Troubleshooting Settings; you can change or delete the conditioned action here.

Creating Conditions

To create a condition, proceed as follows:

...

       1.      Choose Create.

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

The condition you want to create is activated automatically (). The user and the expiration data and time of the condition are predefined. If the validity period expires, the rule is automatically deactivated ().

       2.      Using the input help, select a condition, for example; USERNAME.

       3.      Enter an argument (a value) for the selected condition, for example SMITH.

       4.      If necessary, change the date and time that the condition ceases to apply.

       5.      To create additional conditions, choose Create for each additional condition and make the corresponding entries in each of the selected lines.

       6.      Save the conditions.

       7.      To deactivate a condition that you created, choose Activate <-> Deactivate ().

       8.      To delete a condition from the table, select the corresponding line and choose Delete.

Creating Actions

Once you have created the required conditions, proceed as follows:

...

       1.      Choose the Actions tab page.

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 the predefined entries.

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

○       Tracelevel

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

Depending on the level set, the Tracelevel action can override the tracing settings that were made for the pipeline.

○       Logging

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

The action Logging comes into effect if logging on the pipeline or pipeline service level is deactivated.

○       Debugstring

Allows you to activate a breakpoint set in code that then starts the debugger at this location. You must activate HTTP debugging for this purpose for messages that enter the Integration Engine through the HTTP inbound interface.

       3.      Using the input help, select an argument (a value) for the action.

       4.      If necessary, create additional actions by choosing Create for each additional action and making the corresponding entries.

Each action may only occur once for each conditioned action.

       5.      Save the actions.

       6.      To delete an action from the table, select the corresponding line and choose Delete.

Deleting Conditioned Actions

To delete a conditioned action, choose Delete in the corresponding block on the screen Troubleshooting Settings. 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 Troubleshooting Settings. The system displays a dialog box with the tab pages Conditions and Actions, where you can make changes to the conditioned action.