Testing the Configuration

You can simulate the processing of a message on the basis of existing configuration data. You can enter the header and payload of the message as the input parameters. You can display and analyze the status of the message after each individual substep and once the message has been fully processed.

Caution Caution

The test will only include active configuration objects.

End of the caution.

Caution Caution

At present, the configuration test does not support adapter-specific attachments.

End of the caution.

During the configuration test, the individual pipeline services are called, and the change to the message in each case is simulated in the individual processing steps.

More information: Pipelines and Pipeline Services

Prerequisites

To call the configuration test, in the Integration Builder main menu, choose Tools Test Configuration .

Features

The tool for the configuration test comprises the following screen areas:

Screen Areas and Functions
Screen Area	Function
Menu bar	Calls the functions for starting and resetting the test
Test message and test results	Tab page Test Message Entries for the header and payload of the test message Tab page Results Displays the result messages from the test run for the entire pipeline or for individual processing steps.
Progress display	Displays the steps that have already been processed Calls the functions for starting and resetting the test
Configuration Objects and Error Log	Detailed analysis of errors Tab page Configuration Objects Displays the configuration objects that are relevant for the selected messages Tab page Error Log Display the detailed error log (trace)

This graphic is explained in the accompanying text.

Screen Area of Configuration Test Tool

Activities

Define Input Parameters

On the Test Message tab page, enter the header and, if applicable, the payload of the test message (in XML format).

Recommendation

It only makes sense for you to enter a payload if you want to test some configuration settings that are dependent on the application data. This includes mappings and routing conditions, both of are dependent on the contents of the payload.

End of the recommendation.

You have the following options for specifying the fields of the header:

Using Input Help
Drag and drop
When you use the cursor to drag a logical-routing or collaboration-agreement object from the navigation area in the Integration Directory to the Header area on the Test Message tab page, the header fields of the message are filled with the values of the object key of the configuration object.

You have the following options for specifying the payload of the message:

Manual entry
Copy a message from the test tool of the mapping editor (see Test Environment)
Copy a message from message monitoring

Start the Test

You start the test in the test-progress display. You can do the following:

Start the test run for the whole pipeline (Start)
Start the test run for a single processing step (Single-Step)

You can reset the test by choosing Reset.

The graphical test-progress display shows which steps in message processing have already been simulated.

If the step has executed all the messages successfully, it displays the icon.
If all the messages had to be stopped due to an error, it displays the icon.
If one or more messages (but not all) had to be stopped due to an error, it displays the icon. In the case of the latter, the test can be continued; however, we recommend that you analyze the error.

Display the Result Message(s)

Display the List of Result Messages

The Results tab page displays all the test messages for either the whole test run or just the sub-step specified in the test-progress display.

Example Example

For example, multiple result messages are created by a receiver determination with multiple configured receivers.

End of the example.

The table lists all the messages that were created after the executed processing step. Here, you have the option of specifying which information is displayed for each message. To do so, choose Maintain Table and then select the columns that you want to display in the table.

The following columns are available:

Information for Result Messages
Column	Description
Status	Displays the status of the result message. Message processed successfully Message not processed further due to an error Check the Error Log tab page (see below) to analyze the error further. (once the whole pipeline has been tested): Message processed successfully by entire pipeline.
Stopped At	Only if the message was not processed further: Displays the configuration object (icon) in which the error occurred. Note For a list of configuration object icons, see Legend (Integration Directory). End of the note. For more information about the configuration object and the error, see the Error Log tab page (see below).
Sender	Displays the header values of the result message.
Receiver
Interface

Display the Payload of a Result Message

In the table, select the message whose payload you want to display. The payload of the selected message is then displayed in the Payload frame.

Troubleshooting

Display Relevant Configuration Objects

The Configuration Objects tab page lists the configuration objects that define the processing of the message for the steps executed. The object key for each configuration object is displayed. To open the configuration object, double-click the relevant line of the table.

If a processing step creates multiple messages, you can use a filter function to restrict the display to leave only those configuration objects that are relevant for a particular message. To do so, activate the filter (icon on the Configuration Objects tab page) and select a message in the table (Results tab page).

Display Detailed Error Log

The Error Log tab page displays an error log for the test.

The error log contains the following:

A list of the configuration objects involved, in the order in which the message was processed. To open the configuration object, double-click the object key.
A trace entry for each processing step
You can expand the trace and display the individual trace entries.

Here too, you can open the listed configuration objects by navigating forwards.