Why aren't adapter errors visible in SXMB_MONI?

[Terry_KPMG]

My client has an integration scenario that updates an Oracle database through a JDBC receiver channel. Occasionally an insert/update statement will fail. The adapter engine logs the Oracle error message, but that error message doesn’t show up in SXMB_MONI. SXMB_MONI happily displays the checkered flag. You can only see the adapter error in runtime workbench.

Why aren’t adapter errors “visible” in SXMB_MONI?

[Terry_KPMG · Accepted solution]

Thanks for the quick replies!

It seems odd that error messages aren’t propagated from one stack to the other so that we have a COMPLETE view of the lifecycle of our messages. The left hand doesn't communicate with the right.

Thanks again!

[prateek · Accepted solution]

Nice thought.

Although v have something called end-to-end monitoring in RWB, but yes not the complete lifecycle.

But that differentiation could be seen logically. XI sits on ABAP+JAVA. So in maintenance perspective, handling and monitoring the stacks will prove out to be much less a headache for the administrators.

Of course, for the developer perspctive, we want everything at one place

Regards,

Prateek

[henrique_pinto · Accepted solution]

> It seems odd that error messages aren’t propagated

> from one stack to the other so that we have a

> COMPLETE view of the lifecycle of our messages. The

> left hand doesn't communicate with the right.

You can't propagate an error which occurs in a later point of the pipeline to a previous point.

They error may occurr in the adapter, but when the message gets to the AE, the Integration Engine pipeline is already complete.

But you know, the later point can carry on errors occurred at a earlier point. That is why you can see the Integration Engine errors in the Messsage Monitoring.

It is a matter of culture. SAP consultants, in general, are more confortable with ABAP stack (SXMB_MONI) than with Java Stack (Message Monitoring). But, in this case, the Java tool is more complete.

Regards,

Henrique.

[Former Member · Accepted solution]

i understand ur question is for sxmb_moni

but is the error visible in the communication channel

[prabhu_s2]

message that passes the Integration pipeline are visible in sxmb_moni. Errors related to CC can be traced in CC monitoring or adapter monitoring in RWB.

[Former Member]

Hi

Adapter engine works on Java Stack.sxmb_moni shows the errors of ABAP Stack, therefore adapter errors are not visible at sxmb_moni.

Thanks

[prateek]

BCoz adapter engine resides on Java stack and u view sxmb_moni on the ABAP stack which displays only Integration Server related errors

Regards,

Prateek