Central Monitoring

[Former Member]

Hi

I am wondering if there is really a central monitoring that could detect both the message flow and adapter errors.

As you know, the messages are processed in the pipeline of the Integration Engine. The first part of the pipeline processing occurs at the ABAP stack. After the technical adapters, there is a switch to the Java side.

Could a message error be detected in the RWB (Java)?

Could an adapter error (wrong parameter in the communication channel) be detected in the message monitoring at ABAP?

Thanks

Regards

Go:khan

[bhavesh_kantilal · Accepted solution]

Hi Gokhan,

This is possible using the Visual Administrator. Just check this blog my michal for the same,

/people/michal.krawczyk2/blog/2005/09/07/xi-why-dont-start-searching-for-all-errors-from-one-place

Also, if you want to moniotor for errors in real time , XI Alerts can be used and they trap both the Integration Engine and Adapter Engine Errors.

To create Alerts , just check this blog,

/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step

Regards,

Bhavesh

[Former Member · Accepted solution]

Hi Bhavesh

Thanks for the remark that a central monitoring for all the error is possible. But what about my questions.

Could a message error be detected in the RWB (Java)?

Could an adapter error (wrong parameter in the communication channel) be detected in the message monitoring at ABAP?

Regards,

Go:khan

[bhavesh_kantilal · Accepted solution]

Hi gokhan,

The JAVA Stack is going to contain only the ADAPTER ENGINE errors .

Reason : The ADAPTERS ( except IDOC and HTTP ) interact with the ADAPTER ENGINE in the J2EE STACK and this passes the messages picked to the INTEGRATION ? ABAP engine.

The exectuion of your Scenarios or message flow is going to happen in the INTEGRATION EGNINE and so, errors in INTEGRATION ENGINE can be viewed in SXMB_MONI only.

<i>Could an adapter error (wrong parameter in the communication channel) be detected in the message monitoring at ABAP?</i>

No, as the Integration Engine would have passed the message to the ADAPTER ENGINE and its task is succesful and it will show success in MONI. But, the task of actually sending / receiving the message is with the ADAPTER ENGINE and so, this error can be traced only in RWB.

Hope this info clears things up,

Regards,

Bhavesh

[Former Member · Accepted solution]

Hi Bhavesh

I think we are coming closer to the solution.

But what about my second question:

Could a message error (mapping error) be detected in the RWB (Java)?

Regards,

Go:khan

[bhavesh_kantilal · Accepted solution]

Gokhan,

You mapping program is executed on the JAVA stack, but , the errors if any that occur are passed on to the INTEGRATION ENGINE and so, even your MAPPING erorr can be traced only in the INTEGRATION ENGINE or MONI, and not from the RWB.

Gokhan, to see what errors can be traced in which part, would suggest a workaround.

Go to RWB--> ALERT CONFIGURATION --> ALERT RULE --> you will be able to see the errors related to INTEGRATION ENGINE and ADAPTER ENGINE .

These errors can be seen only in the RWB and SXMB_MONI respectively.

Regards,

Bhavesh

[Former Member · Accepted solution]

Hi Bhavesh

Wow, the problem is solved. That was important for me.

Thanks to you and Udo.

Regards,

Go:khan

[bhavesh_kantilal · Accepted solution]

GOkhan,

Great to be of help.

Regards,

Bhavesh

[udo_martens]

Hi Gökhan,

in SXMB_MONI you can monitor only the ABAP stack (integration engine). For monitoring the Java and ABAP stack go to RWB message monitoring, where you can see both. The ABAP stack monitoring is more comfortable, so usually you use it except you expect adapter errors.

Regards,

Udo