FW: [ws-caf-implement] WS-CAF Implementation Plan

["Simeon M Greene" <simeon.m.greene@oracle.com>]

Hi,
As discussed in the call this morning I am forwarding an email (see below) I
sent the implementation sub-group regarding the use of the WS-I SCM
Application as a basis for a ws-caf demo.  I have also attached the SCM
Architecture document that describes the WS-I application in a little more
detail.  I plan to write a more formal proposal if the implementation group
decides to go with this idea.
Hope this helps,
Simeon

-----Original Message-----
From: Simeon M Greene [mailto:simeon.m.greene@oracle.com]
Sent: Tuesday, December 16, 2003 7:03 PM
To: krishna@inventicasystems.com;
ws-caf-implement-chair@lists.oasis-open.org
Cc: ws-caf-implement@lists.oasis-open.org
Subject: RE: [ws-caf-implement] WS-CAF Implementation Plan


Hi,
Please excuse the disorganized brain dump that follows... I did not have
time to write a formal proposal... I will soon but I just wanted to see if I
could start discussion on this.
	As Malik mentioned, I propose we use the SCM Application (see attached doc)
that WS-I uses for our demo.  Here are some quick points on why I think the
SCM will be good to use for the types of demo we intend to write:

1) The WS-I SCM Sample App is built for web services interoperability:
The WS-I Sample App consists of 4 web services -
	i) Retailer Service - A service that shows a catalog of items and allows
users to select items for purchases.
	ii) Warehouse service - There are 3 implementations of this service.  Each
implementation offers a limited quantity of products that are listed in the
Retailer service's catalog.
	iii) Manufacturer service - There are 3 implementations of this service.
Each implementation offers a unique set of product types listed in the
retailer service's catalog (ex. VCR's, TV's, etc.)
	iv) LoggingFacility service - This service performs logging and order
tracking of purchases, and warehouse transactions made from the retailer
service.
Each WS-I SCM implementer implements all four services along with a web
application that can combine the services.  For example if company A and
company B are implementers, they will each have a web app that allows a user
to select for example Retailer A, Warehouse B (or a permutation of 3
warehouses from each company), Manufacturer A (or a permutation of 3
manufacturers from each company), LoggingFacility B.  Interoperability is
determined as successful when a user can select products from the Retailer
Service, make a purchase, and view the status of his order.

2) It employs multiple web services (as I've explained above) that can be
collocated or distributed.

3) An architecture, spec, wsdls, and sample implementations (including
source code) are publicly available (spec attached) in both Java and C#
(maybe even C++).

4) The design is flexible enough to add WS-CTX, WS-CF and WS-TXM in stages.

This is how I envision adding WS-CAF to the SampleApps:

- First add WS-CTX by allowing users to place items from the Retailer
service catalog into a shopping cart using a shopping cart service.  The
shopping cart service will use Context like a Session object.  Since this
first phase of the demo does not use the Coordinator, the Context will be
shared by passing around the uri (pass by reference) and relying on the
timeout value to determine that the context is no longer valid.  When a user
first places items in the shopping cart, the shopping cart service will
begin a new shopping activity and return a reference to the newly created
context.  Subsequent additions to the cart will result in the shopping cart
service augmenting the existing context.  Before augmenting the context
however, the service will check to see if the context is timed out, if it is
the cart will be destroyed and the user will have to create a new cart with
new items.

- Add WS-CF by allowing all the services involved to register with a WS-CAF
coordinator.  Once scenario of where this will be useful may be allowing a
Warehouse service to indicate to other participants in the shopping activity
that it cannot deliver some of the goods in the shopping cart because they
suddenly were made unavailable (for example, another user in another
application has completed an order that removed them).  When the user
attempts to check out an error should be raised because one Warehouse
service has indicated it cannot complete the activity.

- Add WS-TXM (ACID Transactions - I haven't thought beyond that) by allowing
the purchase to constitute as real transactions.  Beginning a purchase will
now mean starting a distributed web service transaction.  If the context
times out, the transaction should be rolled back.  If a warehouse cannot
ship an item, the transaction should be rolled back.  Only when the Retailer
and the Warehouses return successful completion outcomes should the entire
transaction be committed.

Hopefully everyone gets a gist of what I am proposing.  Even if we decide
not to use the Sample App SCM, I still think an application that can show
CAF components working in steps will be a good idea.

Thoughts?
-Sim

PS  If anyone needs more info I'll be happy to provide it.
-----Original Message-----
From: malik saheb [mailto:malik.saheb@arjuna.com]
Sent: Tuesday, December 16, 2003 2:19 PM
To: krishna@inventicasystems.com;
ws-caf-implement-chair@lists.oasis-open.org
Cc: ws-caf-implement@lists.oasis-open.org
Subject: RE: [ws-caf-implement] WS-CAF Implementation Plan


The implementation plan will not be available before Christmas.

The goal of this subcommittee is mainly; from different implementation
we could provide an interoperable application as a proof of concept to
promulgate the ws-caf specification, and not to produce a reference
implementation.

Some points to consider for the demo application are:
- Do we consider only one single application that can be improved step
by step (how ws-ctx is used, then ws-cf then ws-txm) or several
applications according to what we want to demonstrate? I guess that the
first case is more appropriate.
Simeon is proposing a demo based on the "Supply Chain Management
application" implemented by the WS-I Sample Apps Group.
- According to the chosen application, we should think about the
possible transactions model (or models) to use.
- From the programming language point of view, no language is obviously
mandated. We have listed Java and C++, any other language is welcome.

Several implementations are expected so I don't think that a CVS access
is appropriate, unless requested!!

I guess that most you will take some holidays (as me) during this
period, therefore it will be difficult to provide a plan for the next
ws-caf con-call meeting (January 5th). May I ask everyone here on his
availability for a con-call meeting, and then ask who could host the
meeting call?

Discussion on the mailing list is now open; it will be fine to make
available our plan by mid-January.

Malik SAHEB
-----Original Message-----
From: Krishna Cheemalamarri [mailto:krishna@inventicasystems.com]
Sent: 16 December 2003 00:43
To: ws-caf-implement-chair@lists.oasis-open.org
Cc: ws-caf-implement@lists.oasis-open.org
Subject: [ws-caf-implement] WS-CAF Implementation Plan

Hi Malik,

	Will the implementation plan be available before Christmas? If
you can send me an outline of the plan, I can work on a detailed project
plan and distribute it. Do you have any plans about setting up the CVS
yet?

Cheers!
Krishna

SCMArchitecture1.0BoardApprovalDraft.doc