Re: [ebxml-dev] Interface between MSH and Applications

[Patrick Yee <kcyee@csis.hku.hk>]

Hima,
In my model, I need to support multiple applications to utilize one MSH for
transport. Do you mean we should build one more layer in between the
applications and MSH to route the message to the applications? Initially, I
suspect it is the role of MSI to do that. Please advise.

Thanks and Regards,
-Patrick

----- Original Message -----
From: "Himagiri(Hima) Mukkamala" <himagiri@sybase.com>
To: "Patrick Yee" <kcyee@csis.hku.hk>
Cc: "Martin W Sachs" <mwsachs@us.ibm.com>; <ebxml-dev@lists.ebxml.org>
Sent: Thursday, March 28, 2002 10:38 PM
Subject: Re: [ebxml-dev] Interface between MSH and Applications


> <hima> inline
>
> Patrick Yee wrote:
>
> > Thanks Martin, but I still have a followup question:
> > It seems to me that we have 2 choices to support routing of received
> > messages to the correct application:
> >
> > 1. CpaID + Service + Action
> > We assume each application has a handler to handle a specific Service
and
> > Action. This is relatively easy to implement, since the role and
> > responsibility of the applications are well defined, and are well known
in
> > the MSH. However, this, in some sense, requires the MSH to know the BP
in
> > place.
> >
>
> <hima> In this case, it may not be the MSH which knows about the
> Business Process. MSH just provides the necessary information
> which is retreived from the incoming message like the
> CpaID, ConversationId, Service, Action, ROle to the upper
> layer which could be the middleware performing the role
> of Business Process Engine. This particular piece of software
> lies between MSH and the business application, understands
> Business Processes and invokes the right application entry
> points.
> </hima>
>
>
> >
> > 2. CpaID + ConversationID
> > This requires a more sophisticated mechanism in MSH to register/monitor
the
> > ConversionID, in order to route the received message. However, there is
a
> > problem when the responding MSH receive a message with unknown
> > ConversationID in the first step, it basically don't know which
application
> > to route. We may overcome by identifying Service + Action in such the
first
> > step, however, this is yet more complicated.
> >
>
> <hima> MSH does not need to carry state information corresponding to
> conversationId, it's the layer about MSH which does this.
>
> >
> > We are wondering which is better? Many thanks for your advice.
> >
> > Regards,
> > -Patrick
> > --
> > Patrick Yee
> > System Architect
> > Center for E-Commerce Infrastructure Development (CECID)
> > Dept. of Computer Science and Information Systems
> > The University of Hong Kong
> > Tel: (852) 22415674   Fax: (852) 25474611
> >
> > ----- Original Message -----
> > From: "Martin W Sachs" <mwsachs@us.ibm.com>
> > To: "Patrick Yee" <kcyee@csis.hku.hk>
> > Cc: <ebxml-dev@lists.ebxml.org>
> > Sent: Thursday, March 21, 2002 10:26 PM
> > Subject: Re: [ebxml-dev] Interface between MSH and Applications
> >
> > >
> > > The MSH supports multiple applications.  The Service and Action
elements
> > > and the CPAId, conversationId, and messageId attributes support
routing of
> > > received messages to the correct  application.
> > >
> > > Regards,
> > > Martin SAchs
> > >
> > >
> >
****************************************************************************
> > *********
> > >
> > > Martin W. Sachs
> > > IBM T. J. Watson Research Center
> > > P. O. B. 704
> > > Yorktown Hts, NY 10598
> > > 914-784-7287;  IBM tie line 863-7287
> > > Notes address:  Martin W Sachs/Watson/IBM
> > > Internet address:  mwsachs @ us.ibm.com
> > >
> >
****************************************************************************
> > *********
> > >
> > >
> > >
> > >                       Patrick Yee
> > >                       <kcyee@csis.hku.h        To:
> > ebxml-dev@lists.ebxml.org
> > >                       k>                       cc:
> > >                                                Subject:  [ebxml-dev]
> > Interface between MSH and Applications
> > >                       03/21/2002 05:19
> > >                       AM
> > >                       Please respond to
> > >                       Patrick Yee
> > >
> > >
> > >
> > >
> > >
> > > Hi Everybody,
> > > We have a question about the interface between MSH and applications.
In
> > the
> > > specification, there is a layer called Message Service Interface
(MSI).
> > The
> > > application will be talking to MSI to access the functionalities
provided
> > > by MSH. My question is: will a MSH serve only one application? Or a
MSH
> > > will serve multiple applications through MSI?
> > >
> > > Why we have this question is that, if the latter case is true, we have
to
> > > define an identifier for each application using the MSH, so that the
MSH
> > > can dispatch the ebXML message received to the corresponding
application.
> > > Is there such an identifier defined in the specification?
> > >
> > > Thanks in advance.
> > >
> > > Regards,
> > > -Patrick
> > > --
> > > Patrick Yee
> > > System Architect
> > > Center for E-Commerce Infrastructure Development (CECID)
> > > Dept. of Computer Science and Information Systems
> > > The University of Hong Kong
> > > Tel: (852) 22415674  Fax: (852) 25474611
> > >
> > >
> > >
>