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


Help: OASIS Mailing Lists Help | MarkMail Help

asap message

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

Subject: Re: [asap] RE: Demo questions

I think it could be of value to start looking at how BPSS
models can be applied to these interchange definitions.
We're still grappling with all the nuances of multi-party -
but we will be getting there in V3 - and your diagrams
provide some use cases to get started.
Having BPSS able to define the interchange metrics
obviously adds significant value - especially around
state management, tracking, document handling,
QoS settings and much more.
I've got a tutorial and a sample model (JPG and XML)
out at my resource site.
This model could also output ASAP related XML as well
sinc one model can output multiple syntax components.
I'm also going to be adding signals (obviously of potential
ASAP use!) to the model in the next couple of
weeks - we just discussed that on the BPSS team call
Anyway - checkout what's there right now:
Enjoy, DW
----- Original Message -----
Sent: Friday, June 18, 2004 1:39 PM
Subject: [asap] RE: Demo questions

These are good questions, so I am copying the entire group.
We are preparing an extended demo.  Here is how it works.  We use the .Net reference client to invoke a process in iFlow.  We can then bring up a graphical depiction of the process.  The iFlow process (whic simulates the retailer) then makes 3 parallel calls to the other engines: Handysoft, EasyASAP, and Staffware.  The octagons below represent the ASAP interaction with these systems. We then wait for the three responses.  The color of the octagon will change when the response is received, so we will actually see a visual indication of the response from manufacturing.  Finally, when all three responses are back, the process is completed, and then the reference client receives it's notification.  In the response message is the three manufacturer's names and the three delivery dates.
The great thing about this demo is that it is a single demo, lasting less than 5 minutes, that involves all 5 of the participants.  The down side is that it requires every one of the participants to work.
We have tested each of the interactions individually, but so far every test of the integrated demo has failed because of technical glitches.  We will be trying again today.  I think we are very close to getting this to work, and I think this graphical representation with real time update will be MUCH flashier and show the action of the protocol in the best light.
So far I think we have not had problems with the Handysoft implementation.  I will give you an update on the status in a little while.
Here is a role interaction diagram:

Keith D Swenson, kswenson@us.fujitsu.com
Fujitsu Software Corporation
1250 E. Arques Avenue, Sunnyvale, CA 94085
(408) 746-6276   mobile: (408) 859-1005

-----Original Message-----
From: Cain, Robert [mailto:rcain@handysoft.com]
Sent: Friday, June 18, 2004 9:26 AM
To: Keith Swenson
Subject: Demo questions

Just following up with a few questions.
Did you ever decide to use the expanded scenario, utilizing a parent process to call all other processes in parallel?
Did you test this?
Did any other vendors test this?
What time during the overall presentation, will the actual demo occur.  I'd like to near our server at that time.
Robert Cain

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