cancel
Showing results for 
Search instead for 
Did you mean: 

Soap Sender Adapter EOIO Queue

Former Member
0 Kudos

Hi,

I have a scenario IDOC(Sender) to SOAP (Multiple Receivers - based on condition in receiver determination)


We have requirement where we need to send mesages in a queue to one of the recivers and that specific recivers has some frequent time out issues, so we cannot go with idoc serilaization and EOIO concept usinf sender IDOC adapter as it impacts all the receivers

We have used 2 way scenario for routing (1st - IDOC to Soap Reciever) (2nd Soap sender to web service) the scenario works great however when I see the soap document from rwb payload it shows Exactly once)

I dont see the queue name mentioned in soap sender adapter from  2nd scenario

I made sure the Queue name is registered in manage queues/ Sxmb_adm, also tried with XBQ9_123, XBQ1_123, no go

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member184720
Active Contributor
0 Kudos

Instead of creating the second flow, did you try selecting the checkbox for "maintain order runtime" under interface determination for whatever the receiver that requires EOIO?

Former Member
0 Kudos

I wish I could do that but we are on 7.3 sp04 and when using ICO we dont have that option

former_member184720
Active Contributor
0 Kudos

Are you sure? I got the higher version but not 7.30 to validate

However as per the below SAP document maintain order runtime should be available in 7.3?

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0d70f21-e7f4-2f10-0380-e1f5ff496...

If you have configured ICo then i couldn't understand what sxmb_adm/queues got to do with this scenario?

or is your second flow not an ICo? If so make sure that you have configured the right URL in soap receiver(first flow)

It should be :

http:// <host name> : <port name> /XISOAPAdapter/MessageServlet?channel=<party name> : <service name> : <channel name>

If you have configured the IE url then you must add the qos at the end of the URL.

Former Member
0 Kudos

Thank you for the qucik replys !!!

Absolutely I am sure that for current version we are in does not have maintain order runtime may be it is avaiable from other sp's but not 7.3 sp04

I can try change the second flow to abap stack objects instead of ICO but analysis why the queue is not detected at runtime

the current URL i am using in (1st scneario soap reciever is http://xxxxxxxxxxx:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_xxx&receiverPart...)

I have added the Queue to the end of URL but does not seems to be working for EOIO

Any work arounds or a fix suggestions are appreciated

former_member184720
Active Contributor
0 Kudos

Try the other URL i mentioned in my previous reply and do not add the QOS and queuename in the URL.

Former Member
0 Kudos

Can you suggesr which service name and channel name should be in the URL

former_member184720
Active Contributor
0 Kudos

of you second interface...(from second flow soap sender channel, copy the details)

Former Member