Message processing is stopped - Exactly Once Async Abap Proxy

[Former Member]

Hi Guys

I have two JDBC->Xi->Abap Proxy scenarios. The Abap Proxiy server is in a BW 3.1 with SAP WebAS 6.20 (XI 2.0) and the XI is the XI 3.0 (NetWeaver 2004s).

First scenario is synchronous. It works without problem.

Second scenario is asynchronous and a processing of message stops at the Receiver Grouping stage.

So, there are only 3 stages in Integration Engine:

1. Inbound Message (CENTRAL)

2. Receiver Grouping

3. Response (I don't understand why Response is appeared!!!)

Message don't go to BW. Nevertheless message status is successful !

Can somebody help me?

Best regards,

Denis.

Edited by: Denis Vezhov on Feb 5, 2008 1:01 PM

[rodrigoalejandro_pertierr · Accepted solution]

hi

in bw, check tcode

sxi_monitor and see if message passed to bw, here, the status could be error, but in XI success.

if no message, in proxy define next code

data: i_aux type int value 1

while i_aux EQ 1

endwhile

execute your scenario, them in bw go to SM50 and look for your proxy ZAIIXXX.

go to programs/session --> program --> debugging and chek the proxy execution.

also verify the configuration of your CC

Addressing type: URL Address

Target Host: the host you create the proxy (bi,bw)

service number: Port http, you can get it in TCODE SMICM

Path: /sap/xi/engine?type=receiver

QoS = EO

Hope it helps.

Thanks

Rodrigo

Edited by: Rodrigo Pertierra on Feb 5, 2008 9:43 AM

[Former Member · Accepted solution]

It is incredible, but after I went sxi_monitor in BW the scenario begins to work!

[udo_martens · Accepted solution]

SDN waves?

[Former Member · Accepted solution]

it's cool

[prateek]

Make sure that u r using the QOS as EO and not BE

Regards,

Prateek

[Former Member]

I'm sure. It's defined in CC and also I see it in message content.

[udo_martens]

Hi Denis,

did you define your interfaces as asynchronous?

Regards,

Udo

[Former Member]

Yes, sure.