[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: TPA & ebXML; more and more thoughts...
>Eventually we need to think about the end to end sequence within the ebXML >environment, meaning, when does the RegRep get accessed for such configuration >information, etc. Here is a scenario regarding regrep access. A business process application produces the document to be sent. The ebXML engine does the following. 1. Access the regrep and determine if there is a tpa with the to-be receiver. 2. Construct the ebXML document using the information in the tpa. i.e., possibly apply security, etc. 3. Send it according to the receiver's transport profile as specified in the tpa. The primary assumption at line 1 is that two trading partners exchange documents ONLY if there is a contract (legal and all) established between them. Although I agree with the need for a tpaID, the tpaContext is apparent from the above and therefore unnecessary. The caching of the tpa is a good idea. Otherwise every transaction would require a regrep access, expensive during multiple exchanges. However, this is an implementation issue which should not affect tr&p and is better left to the ebXML vendors, don't you think ? Sohaib.J.Kidwai Architect EComXML Inc. Reply To: sohaibk@ecomxml.com Phone: (215)321-5569 (x104) Fax: (215) 321-1172 http://www.ecomxml.com -----Original Message----- From: srh@us.ibm.com [mailto:srh@us.ibm.com] Sent: Thursday, July 06, 2000 4:12 PM To: Sohaib.J.Kidwai Cc: john_ibbotson@uk.ibm.com; ebXML-Transport@lists.oasis-open.org Subject: Re: TPA & ebXML; more thoughts Some more thoughts: Eventually we need to think about the end to end sequence within the ebXML environment, meaning, when does the RegRep get accessed for such configuration information, etc. Thinking of the TPA as a configuration file, requires identification (TPAid) but further requires context (not to go into this here as CC/BP are currently wrestling this concept). So, I suggest we think TPAidContext and TPAid. Performance and Configuration Changes leads to thoughts toward a TRP implementation should be able to cache a Config file (TPA) document as a configuration for a process between specific partners. We could consider some sort of "dry-run" capability of a business process where it would give the TRP engines the opportunity to insure they are ready with the correct configuration by TPAidContext and TPAid. They could remain "ready" (have cached the config file if needed, alocated system resources if needed, etc) for a given period, and could expose TRP-level common query interfaces (more thoughts here abound) to obtain the ready-timeout period, etc. This leads to thinking about the ability to force a cache purge during the dry run for cases where the config file has changed. etc etc. Scott Hinkelman Senior Software Engineer, SWG IBM Austin 512-823-8097 (TL 793-8097) (Cell: 512-940-0519) srh@us.ibm.com, Fax: 512-838-1074 "Sohaib.J.Kidwai" <sohaibk@ecomxml.com>@lists.oasis-open.org on 07/06/2000 01:33:59 PM Sent by: owner-ebxml-transport@lists.oasis-open.org To: John Ibbotson/UK/IBM@IBMGB, <ebXML-Transport@lists.oasis-open.org> cc: Subject: TPA & ebXML Hello John, Thanks for this document. Just to add a comment, the negotiation of a Trading Partner Agreement itself can be done using the ebXML framework. A tpaML document could be exchanged (possibly several times) between two trading partners over the ebXML framework until the trading partners have come to an agreement over its final form. The final tpaML document could then be used to provide configuration information as you mentioned in your email, for all future ebXML exchanges. Although this brings us to a chicken and egg problem of, how the first exchange was possible without a trading partner agreement! Just some thoughts. Regards, Sohaib.J.Kidwai Architect EComXML Inc. Reply To: sohaibk@ecomxml.com Phone: (215)321-5569 (x104) Fax: (215) 321-1172 http://www.ecomxml.com -----Original Message----- From: owner-ebxml-transport@lists.oasis-open.org [mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of john_ibbotson@uk.ibm.com Sent: Thursday, July 06, 2000 11:23 AM To: ebXML-Transport@lists.oasis-open.org Subject: TPA - Initial thoughts As discussed on the conference call, here is the initial draft document on Trading Partner Agreements (See attached file: ebXML TRP and TPAs.doc) John MQSeries Technical Strategy & Planning, IBM UK Ltd, Hursley Park, Winchester, SO21 2JN Tel: +44 (0)1962 815188 Fax: +44 (0)1962 816898 Notes Id: John Ibbotson/UK/IBM email: john_ibbotson@uk.ibm.com ======================================================================= = This is ebxml-transport, the general mailing list for the ebXML = = Transport project team. The owner of this list is = = owner-ebxml-transport@oasis-open.org = = = = To unsubscribe, send mail to majordomo@lists.oasis-open.org with = = the following in the body of the message: = = unsubscribe ebxml-transport = = If you are subscribed using a different email address, put the = = address you subscribed with at the end of the line; e.g. = = unsubscribe ebxml-transport myname@company.com = ======================================================================= ======================================================================= = This is ebxml-transport, the general mailing list for the ebXML = = Transport project team. The owner of this list is = = owner-ebxml-transport@oasis-open.org = = = = To unsubscribe, send mail to majordomo@lists.oasis-open.org with = = the following in the body of the message: = = unsubscribe ebxml-transport = = If you are subscribed using a different email address, put the = = address you subscribed with at the end of the line; e.g. = = unsubscribe ebxml-transport myname@company.com = =======================================================================
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC