Skip to Content

OK, you’ve configured a scenario in the Integration Directory of SAP NetWeaver Exchange Infrastructure; now how would you like to test it without sending a test message? Well, if you have SP12 for XI 3.0, you can! Included in the new support package is a Test Configuration Tool for the Integration Directory. This tool simulates pipeline processing (with or without a sample message) to let you know if your configuration is correct.

Suppose you are implementing an IDOC scenario in XI, but do not yet have the ALE configuration done in the sending system. Or you have configured an exchange of business data with a partner, but they are not yet ready to begin actual message testing. These are sample scenarios in which the test configuration tool could come in handy.

You can access the test tool in the Integration Builder by navigating the menu path T ools è T e st Configuration . You will see the following screen in the editing area:


In addition to the menu bar, the test screen has areas for entering header data and a payload (optional), following and controlling the test progress, and viewing the configuration objects and test log.

To start the test, you must have all of the configuration objects activated; the test won’t run if there are active change lists. Start the tool as described above, and then enter the header data for the incoming message. You can enter the header data directly, by using drag-and-drop, or with F4 help. I like to drag the sender Service (and optionally, Party) into the field, then use F4 help to select the interface and namespace. This way I only see the interfaces that are valid for the given sender.

You can enter the Receiver information here, but if you leave it blank you will test if the pipeline can successfully determine a receiver. You can also paste a sample payload document into the Payload area; if you do not specify the payload, any mapping programs will not be tested.

Once you have entered the test data, you can click on either the “Run” ( image) or the “Step Over” ( image) icon to start the test. In “Run” mode, the tool will try to run all the way through the configuration without stopping. In “Step” mode, it will execute each pipeline step and then wait for another click on the icon. To start the test again (perhaps changing test data first), click on the “Reset” ( image) icon.

You can view the test results in the log window:


You can drill down to see detailed information for any step, and if are any gaps in the configuration, you will see them. When I remove my interface determination and repeat the test, I see:


As you can see, the trace information is exactly what would be written to the trace header in the Integration Server at runtime. This will be useful in anticipating problems with the given scenario.

Once you have upgraded your XI system to SP12, I recommend you try the Test Configuration tool to help you streamline your interface configuration!

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Michal Krawczyk
    Hi Paul:)

    I tried this new tool a week after sp12 was released, it’s good but…:)
    can you tell me if there will be a test tool for sending messages too?
    it would be great if we test RFC, or soap or jdbc message once and then paste it somewhere for testing the interface againg & again 🙂

    if you could give me some info about such an idea it would be great:)



    1. Paul Medaille Post author
      As far as I know, there are no plans to create a general purpose test client – but it wouldn’t be a bad idea.  In the meantime, of course, the component monitoring of the Runtime Workbench allows you to send test messages.  Have you tried it?

      1. Michal Krawczyk
        Hi Paul,

        sure I did:)
        have you tried posting a long xml message into this?:) (like matmas idoc)

        my point is that: don’t you thing it would be great if this new test tool could be combined with the ability to send real messages?
        since you specify the payload in this new tool too why don’t extend it’s abilities? 🙂
        I’m not saying it’s a must I can deal with resending real data or using Test Message tab in the component mon. but the easier and more user friendly the tool is the easier it is to convince our potencial clients to buy it:) that’s the point:)
        it the payload filling could look like the one from the test tab of the message mapping program (java graphical mapping) it would be much easier too 🙂

        just a few of my thoughts:)

        Kind Regards,

      2. Anonymous
        I have used this tool a couple of time with great success. I have run in to a situation where I have 2 receivers for my message. I specify the second reciever in the test tool but when I run the test it always brings back the results for the first. If I leave the receiver blank I would expect to see 2 success messages but only the 1st appears. Any ideas? Bug?
      3. t z

        thanks for this blog!.

        I tried to test a HTTP to RFC scenario through this tool, but my receiver determination step errored saying the following,

        Internal Error
        HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://[host]:[port]/sap/xi/simulation?sap-client=001 User: [username]

        Is there any user related settings we need to do for this tool to work?



Leave a Reply