[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ebxml-bp] State Alignment and Web Services
Serm, You are correct in your analysis below. The BPSS cannot guess what you want done, eh? ; -) Therefore you have to setup a BTA - business transaction activity where the interchange is spelled out. If you look the the link I sent you to the JPG of the example model you can see this clearly. Then in the activity diagram - you reference those BTA definitions - and that controls the state and related signals to transactions. There's also a separate signals section in BPSS - and this is where it gets interesting(!). I'm still in the process of fully exploring the capabilities here - but this would appear to have potential for using transport level signals - and this would then remove the need to use the confirmBOD as a "mother-of-all-signals" as Ron has done for the IV&I scenarios... Right now though there is no apparent way of making associations to signals - but that may be something we need to fix!?! Certainly if you could link these the WSDL or ebMS level responses this could be a cool way of enabling this. Then of course - in the acitvity diagram - you need to be able to add guard conditions that link to those signals and return succeed or failure accordingly.... Thanks, DW ----- Original Message ----- From: "Boonserm (Serm) Kulvatunyou" <serm@nist.gov> To: "ebXML BP" <ebxml-bp@lists.oasis-open.org> Sent: Wednesday, June 16, 2004 11:24 PM Subject: Re: [ebxml-bp] State Alignment and Web Services > Monica, IVI WSDL attached. I can't help you technically with the WSDL. I > hope David can. > > I read your quote below and am still confused. First it says "signals when > message received for PROCESSING", then it says "business document has been > SUCCESSFULLY processed". In my mind, if the document has been successfully > processed the app should return business response like ConfirmBOD or AckPO > etc., because the signal cannot precisely indicate which line items are > successfully processed, for instance. > > - serm > > ----- Original Message ----- > From: "Monica J. Martin" <Monica.Martin@Sun.COM> > To: "Boonserm (Serm) Kulvatunyou" <serm@nist.gov> > Cc: "ebXML BP" <ebxml-bp@lists.oasis-open.org> > Sent: Wednesday, June 16, 2004 7:19 PM > Subject: Re: [ebxml-bp] State Alignment and Web Services > > > > Boonserm (Serm) Kulvatunyou wrote: > > > > > Kulvantyou: Did you try reviewing IVI WSDL to see if it will work with > > > BPSS at least with that limitation? > > > > > > Can you expand on "...with profiles that can be shared across a user > > > community" to why so? > > > - serm > > > > mm1: We've not had access to the IV&I WSDL Serm, but would be happy to > > review against the operation capability we approved on Monday. In > > addition, on your question about Receipt Acknowledgement, this is > > detailed in the previous ebXML BPSS version: > > > > <<<The Acceptance Acknowledgement business signal, if used, signals that > > the message received (Request or Response) has been accepted for > > business processing by the receiving application, or a receiving > > business application proxy......The state of each party is considered to > > be aligned when the receiving application (in general unknown to the > > other party) has signaled, via the BSI and an Acceptance > > Acknowledgement, that the business document has been successfully > > processed.>>> > > > > We should discuss further about the roles of the receiving application > > and the BSI (monitoring, state management, etc). You have raised > > multiple questions related to the validation, business rules, and > > responsibility. Perhaps you can provide greater detail or join us on > > Friday to discuss state alignment, web services, and obligation. Thanks. > > > > > > > > > > > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]