RE: [ebxmlms-general] ebXML sample client question

[Tripathi, A. (GXS) <Aji...@gx...>]

Patrick,
 
    Got it! Question is ... what in the MSH resolves a (service, action) to
a (protocol, URL)?
 
    If I understand it right, the service is a part of business process in
this context. An interface... 
 
    However, in the end, based on the action and the service, doesn't the
MSH have to figure out what endpoint to relay the message to?
 
    If yes, do I need to write a custom URL resolver to do that and plug it
in using the config file?
 
regards,
Ajit
 
    
-----Original Message-----
From: Patrick Yee [mailto:kc...@ce...]
Sent: Thursday, November 13, 2003 4:00 PM
To: ebx...@li...
Subject: Re: [ebxmlms-general] ebXML sample client question



Ajit,

No, the service field is not of that purpose. Let's put it this way, 2
companies do business over ebXML. They develop their own applications at
each side. They are said to be offering a "service" to their counterparts.
Each application at one side may handle one or more types of business
request. So we said the "service" includes one or more types of "action".

In ebXML messaging service, the service and action are defined as above.
When the business documents are delivered through ebMS, that "service" and
"action" are marked in the ebMS message headers, the purpose is let MSH be
able to route the received messages to the correct application. Of course,
the application should beforehand notify the MSH that which "service" and
"action" are supported by this application too.

Hope this helps.

Regards, -Patrick