ABAP Client proxy - IF_WSPROTOCOL_ASYNC_MESSAGING

[Former Member]

I have a question regarding the value for the attribue ASYNC_MESSAGING. In every client proxy, this attribute is defaulted to IF_WSPROTOCOL_ASYNC_MESSAGING. (inherits the value from IF_WSPROTOCOL).

Does that mean that the client ABAP proxy uses EOIO ? If so, how do you change it to EO?

If the change of QoS from EOIO to EO is not possible, would creating custom queues and using the SERIALIZATION CONTEXT to specify the custom queue help me alleviate issues with stuck EOIO queues on the sender/receiver sides while using proxy? Since the QoS is determined by the sender, I would assume that if there is way to set it on the Sender client proxy, that would prevent the queues from stopping processing if a message fails. In my case, I am not too concerned about preserving the sequence of the messages.

Any input will be appreciated.

Thanks

Sridhar

[former_member185995]

Hello Sridhar,

I'm not sure if I understand your question right, but I think following applies : ABAPProxy client (SAP sends data to SAP PI) behaves as EO by default. And if one needs to have messages to be delivered to the destination system in order, you need to "tell" this to SAP PI, when you send the data from ABAPProxy client. Thats the case you need include coding as mentioned here: http://help.sap.com/saphelp_nw04/helpdata/en/65/40c9a4a1fa476288ac61b5fcc6bbde/frameset.htm.

Please note, that for WAS 620 ABAPProxy client another routine applies. For more information see the link: http://help.sap.com/saphelp_xi20sr1/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm

Regards

Tomas