OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: Re[2]: Trading Partner Logical Identification based on EDIFA


I was thinking that simply in the process of preparing the TPA, both
partners include individually assigned IDs.  Each ID only has to be unique
within the partner which owns it.  The cobmination is unique across both
partners. Both of these TPA IDs are then carried in the message header for
conversations under that TPA.

By copy of this, I am asking John Ibbotson about MQ.  Hopefully he will
have an answer when he returns from whatever exotic place he is vacationing

(and please forgive my misspelling your name in the previous posting.)



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

David RR Webber <Gnosis_@compuserve.com>@compuserve.com> on 08/15/2000
08:13:29 PM

To:   Martin W Sachs/Watson/IBM@IBMUS
cc:   ebXML-Transport@lists.ebxml.org, Mark NOBLES <MNOBLES@lmi.org>
Subject:  Re: Re[2]: Trading Partner Logical Identification based on EDIFA

Message text written by INTERNET:mwsachs@us.ibm.com
Question:  Has anyone yet worried about the uniqueness of the TPA ID?  To
make routing work based on the TPA ID, the TPA has to be unique at least
within the run-time that is being used by each partner.  To avoid the need
to require uniqueness across both partners, the TPA ID could have a
separate subelement for each partner.  Alternatively, it could be required
that the TPA be stored in one registry that both partners accept.  This
would also guarantee a unique identifier.

Marty - does IBM have an public algorithm for this?  MQSeries seems
like a good place to find such already...

Unique session ID's is same deal.  Again MIME may have something in
tracking side of things it uses too.  I've seen some pretty long "handle"
strings in MIME headers...


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC