Skip to Content

XI: Sending a message without the use of an adapter not possible?

Sending a message without the use of an adapter…
Is it possible or not? It depends…
If you’re working on a DEV lanscape you can do it quite easily.

There are many situations when you want to check your integration process,
integration scenario but you don’t receive a message from your partner…
So once you create your scenario in Integration Repository you can set your routing in the Integration Directory… what then?
Do you have to wait for a first message? No way:)

When I started working with the XI I was searching for a tool that would be as good
as those two standard services from Business Connector:

– savePipelineToFile

– restorePipelineFromFile


but I coudn’t find anything like this…
Did I give up? Did I start to cry ? 🙂
No, because I discovered that there’s a very similar tool called the “Test Tool”.
It allows you to send test messages directly to the Integration Engine.

How you can do it easily?

Just follow those few steps:

Step 1

– log into your Runtime Workbench – Component Monitoring

– choose Integration Engine and Test Message Tab


As you can see it’s not very sophisticated…
but it does it’s job.
To make it work you have to specify some information like interface name,
namespace etc. for your prepared and configured scenario.
Then you have to paste the payload and that’s it…


But how can you easily create the payload?
Sure you can use standard XML editors available on the market but what for?
You got the Message Mapping – Test Tab !
This tool allows you to create your payload which later on you can paste into our Test Tool.

Step 2

– log on to the Integration Repository and choose the first message mapping that you use in your scenario

– fill the source message with values


– now by clicking on the Document Source View you can get the XML that you can Copy….


Step 3

…into the Component Monitoring Test Tool


Step 4

– you can test your message -> Send Message button


Step 5

– check you message in the Message Monitoring (TCODE -SXMB_MONI)


This tool is very simple but as you can see very useful, that’s why probably it’s good how to use it quickly.

You must be Logged on to comment or reply to a post.
  • It’s similar to Client HTTP html (in fact the same).
    Though I have seen this feature..but still I have
    tendency to use HTML page for testing..dunno why:)
    I will also try to use the test message tab:)


      • >>>Perhaps, we had something more in common other than our XI project..?

        I heard that everyone who’s name start with S
        use the Client HTTP html….
        so that might be truth:))


        • >>I hope the title of the article was
          at least a little bit “catchy” since I got
          you two to read my webglog 🙂

          Catchy..yes :)…But anyways even in this case
          the plain http adapter which runs as service in
          SICF is used internally 🙂

          >>I heard that everyone who’s name start with S

          say Sudhir/Siva/Sri/Satyamites..SAP (including Stefan..not sure) 😉


          • >>>plain http adapter which runs as service in
            SICF is used internally

   was supposed to be a secret… :)) 

            now no one will ever want to read my weblogs anymore…


  • Testing in RWB with the payload is fine but, if we get any error say mapping error, how can we analyze that in RWB? Is that possible and if you know please tell me how to debug the UDF code written , like we use F5,F6 and F7 in abap for step by step analysis.