RE: [ebxml-dev] ebMS TR&P tags

["Anarkat, Dipan" <DAnarkat@uc-council.org>]

Title: RE: [ebxml-dev] ebMS TR&P tags

Martin,
        with reference to #2,3 and 4
        As I understand, the value for 'Service' is an identifier for a 'logical' endpoint that processes the business message contained in the payload and this is specified by standards organizations or individuals who define the business process standards. Now to actually process the payload the 'logical' endpoint will have to be mapped to a physical endpoint like, for example, a web-service, EAI app, Java servlet etc, and the entire message then routed internally to the physical service. Is this the way it works?

        If this is true, then the ebXML MSH software will have to be configured with the mapping information for every 'Service/Action' pair to the physical service, right?

Also, after the header-container is processed, what gets passed/routed to the 'Service/Action' ? :
        # the entire ebXML Message
        # the payload only

Also, what is the rationale for identifying and defining values for 'Service', 'Type' and 'Action'?

Thanks

Dipan Anarkat
Systems Analyst, Standards Development
Uniform Code Council, Inc.
Tel: (609)-620-4509
http://www.uc-council.org/

-----Original Message-----
From: Martin W Sachs [mailto:mwsachs@us.ibm.com]
Sent: Thursday, December 06, 2001 3:05 PM
To: Anarkat, Dipan
Subject: Re: [ebxml-dev] ebMS TR&P tags

#1:  CPAId is a pointer to the runtime state information for this CPA.
Various levels of middleware reference various information there.
#2, 3, and 4 are indeed used for routing from the receiving MSH to the
correct software input point.  Details are left to the implementer.

Regards,
Marty

*************************************************************************************

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

"Anarkat, Dipan" <DAnarkat@uc-council.org> on 12/06/2001 02:27:54 PM

To:    "Ebxml-Dev (E-mail)" <ebxml-dev@lists.ebxml.org>
cc:
Subject:    [ebxml-dev] ebMS TR&P tags

Hi,
    Can anyone provide explanation on how the following tags are processed
by the ebXML B2B app with an inbound ('To' MSH) and outbound ('From' MSH)
message ?

#1    eb:MessageHeader/eb:CPAId
#2    eb:MessageHeader/eb:Service
#3    eb:MessageHeader/eb:Service/@type
#4    eb:MessageHeader/eb:Action

Also is #2 and #3  and #4 used for further routing of the recieved message
,
on arrival at the destination ?

Pardon me, but the explanation provided in the ebMS TR&P 1.0 specification
is not helpful.

Thanks

Dipan Anarkat
Uniform Code Council, Inc.
Tel: (609)-620-4509
http://www.uc-council.org/

----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>