Skip to Content
avatar image
Former Member

Maintain order at runtime

I am doing IDOC to JMS Scenario(2 receivers).

for example....jms1 and jms2 are receivers..

in interface determination,I have checked as Maintain order at runtime. First JMS1 then JMS 2 should receive the message.

if i do so ,it is going for holding in run time workbench message monitoring....

But, i need order at runtime...what shall i do...

Edited by: Harsha reddy on Oct 15, 2008 9:32 PM

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 16, 2008 at 07:06 PM

    Harsha

    Did you get solution for this ?

    I too have exactly the scenario 😔

    thanks,

    Giridhar Kommisetty

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      write a UDF or java mapping to stop the interface for few minutes....but,its not the better option.

      orelse,BPM would be best option.

  • avatar image
    Former Member
    Oct 15, 2008 at 08:26 PM

    >>in interface determination,I have checked as Maintain order at runtime

    If JMS1 and JMS2 are two separate business system/service then you dont need to set the order in interface determination.Order is set in interface determination when you have multiple interfaces on 1 single receiver.

    Thanx

    Aamir

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Harsha

      Note does talk about the problem you are facing.

      Without using Maintain Order at Runtime it act as EO. You have two mappings right.

      is the order Configured is also JMS2 and JMS1 when u didnt used Order at runtime. Try to reverse and see if it shows the reverse effect

      For JMS to implement EOIO i relied on Maintain order at runtime and it worked.

      If nothing work then apply the note. 😊

      Thanks

      Gaurav