Skip to Content

XI: Why don’t start searching for all errors from one place?

Many times while working with the XI we might encouter some errors. It may be our wrong communication channel configuration
or maybe the connection to one of the systems is lost. When we log on to the XI we usually stop when we see the first error.
Then we try to find out what causes this error. But there are quite many (so many) applications from where we can find our errors:

– Message monitoring – (TCODE – SXMB_MONI)

– Adapter Monitor

– Messaging System monitor

– Alert Framework

– SLD server logs

– all sorts of XI cache monitors

Where to start searching?
…and do we have to go through all of those with any kind of error?
No. Very often we can use just one tool.
Why don’t we use Visual Administrator logs?

In this weblog I’ll show you some logs that you can use to monitor XI landscapes.
Let me give you an example:

Step 1

Let’s suppose we have an error in our integration process:


Sure we can take a look at the trace from the technical log but….
what if this error is caused by some other error?

With Visual Administrator we can get a much broader view.

Step 2

Let’s take a look at the default trace first:

– log on to the Visual Administrator

– start service – Log Viewer

– cluster -> server -> logs

– choose defaultTrace.trc


Now you can not only see your error but many other errors from this trace. This might mean that something else is wrong
apart from the error we saw in the SXMB_MONI – technical workflow log.

If we want to make sure that the rest of the applications are running without any problems we can check applications.log (in the same node).


If there are too many messages inside this log but you’re sure that the rest of the applications are running correctly we can go to XI log :

– applications


– xi.log

This way you’ll only see logs from the Exchange Infrastructure.

One other useful trace is the dev_jrfc.trc trace file. With it’s help you can check the status of your RFC connections.


But remember that inside sapgui we also have a tool to monitor our RFC logs (TCODE – SM59):


The reason for this weblog is simple – XI error messages are not that easy to find. The better you know all of the tools
that help you locate those errors the more you’ll like working with the XI (if you’re a developer)
and the more satisfied you’ll be (if you’re a customer).

You must be Logged on to comment or reply to a post.
  • Hi Michael,
    Thia is a very excellent log.I am trying this scenario now,
    But can u tell mi on how i should log into the the visual administrator tool, any Tcode???
  • Hi MIchal,

    Great information. I have been reading your blogs for a while and always learn something new from you, which is great.
    I also go to VA to check logs, however I do not know that many places on WAS to go to, to verify logs and errors. Of course, SXMB_MONI and SM59 are obvious, but what about others you listed in the top of your message:

    -Adapter Monitor
    -Messaging System monitor
    -Alert Framework
    -SLD server logs
    -all sorts of XI cache monitors
    Do you have tcodes or menu paths for these?

    Thanks a lot!
    Zycze powodzenia – Malgorzata

  • michael,

    Like all your blogs this one is superb. Can you send me the information about using this tool in more effective way?


    • Hi,

      thnanks 🙂

      there’s a lot of info on VA
      on – just do a search for
      visual admin
      on google 🙂