Re: [ebxmlms-general] ebXML sample client question

[Patrick Y. <kc...@ce...>]

Ajit,

If you look at the sample code in Hermes client, you can see the constructor
of a Request object has a parameter called toMshUrl. When the client sends
out the message though this Request object, MSH will then in turn send that
message out using that toMshUrl as the endpoint.

And you are right, writing a custom URL resolver can be another way to
"tell" MSH about the end point. You can write a custom URL resolver and
specify it inside msh.properties.xml. Normally, your custom URL resolver
should be capable to resolve a URL by an ebXML message (e.g. using it's
toPartyID, or using it's service/action pair, etc.) In operation, when MSH
gets a message to send out, it will pass the message to your custom URL
resolver, and then your resolver should return a URL, and then MSH will use
that endpoint to send the message out.

Hope this helps.

Regards, -Patrick



----- Original Message ----- 
From: "Tripathi, Ajit (GXS)" <Aji...@gx...>
To: <ebx...@li...>
Sent: Thursday, November 13, 2003 6:48 PM
Subject: RE: [ebxmlms-general] ebXML sample client question


> 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
>
>
>