OASIS ebXML Messaging Services TC

  • 1.  Groups - intermediary routing examples.doc uploaded

    Posted 08-01-2008 11:05 
    The document named intermediary routing examples.doc has been submitted by
Mr. Pim van der Eijk to the OASIS ebXML Messaging Services TC document
repository.

Document Description:

Some text that shows some routing scenarios for ebMS, to show some of the
benefits of the intermediary profile, input for the intermediary profile.
   






View Document Details:
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/document.php?document_id=28981

Download Document:  
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/download.php/28981/intermediary%20routing%20examples.doc


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration


  • 2.  RE: [ebxml-msg] Groups - intermediary routing examples.doc uploaded

    Posted 08-01-2008 14:06 
    Pim,

	This is a good and clear description of the value and
functionally provided by "routing" and a good introduction for people.

Thanks for the effort to write this up.


Ian Jones
Chair OASIS ebXML Messaging Services TC 
Email: ian.c.jones@bt.com
 


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 3.  Sequences and sequence sharing

    Posted 09-02-2008 20:07 
    
Hello,

To follow up on the discussion on (re-)using sequences from two weeks ago:
which ebMS messages are sent on the same WSRM sequence? This is more about
ebMS 3.0 in general than about multihop.

Jacques mentioned a default assumption that each Pmode is associated with a
distinct sequence.

1) In the document on routing examples
(http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/document.php?documen
t_id=28981) I discuss a number of routing scenarios. The simplest case
assumes routing is based on To:PartyId only.  It basically asserts for an
I-Cloud that any ebMS message, including messages to be sent reliably, is
handled by the same final MSH.   This means that an ebMS MSH can optimize
its sequence creation, as some Pmodes can use the same sequence. It was
suggested to leave this out of the multihop specification and leave this to
implementers as it is an optimization rather than a potential conformance or
interoperability issue.   

2) Section 2.5 mentions a situation where a message is routed differently
based on a message property value. This means that there have to be
different sequences based only on property values.  Can there be two Pmodes
that are the same except for a particular message property value? If not,
the routing document should not refer to routing based on properties.

3) The ebMS 2.0 message ordering module associates ordering with
ConversationId. Do we want to support a similar model with ebMS 3.0?  If we
have a business process where "conversations" consist of a "PlaceOrder"
action, followed by one or more "ChangeOrder" actions followed by an option
"CancelOrder" action and they are to be processed in order, then the MSH
must use the same sequence to send them.  How and where is this specified?

Pim


  • 4.  RE: [ebxml-msg] Sequences and sequence sharing

    Posted 09-03-2008 06:22 
    Pim:
inline 


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 5.  RE: [ebxml-msg] Sequences and sequence sharing

    Posted 09-03-2008 07:54 
    Jacques,

Thanks for clarification. To summarize: multiple messages are sent on a
single sequence if (1)-(3) apply:

(1) if the messages are correlated based on Xpath expressions in
Pmode.Reliability.Correlation, the must have the same Delivery Assurance
Pmode. (The Xpaths should be written to make sure this is always the case
for any pair of messages that are correlated using these expressions).

In addition to this, when using an in-order contract:

(2) the Xpath expressions specified in the Pmode.Reliability.Correlation
MUST include eb:UserMessage/@mpc. 

When using Delivery Assurances other than in-order:

(3) constraint (2) applies, except that it is a SHOULD instead of a MUST.

Pim


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 6.  RE: [ebxml-msg] Sequences and sequence sharing

    Posted 09-03-2008 19:36 
    Pim: 


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


Related Content