Choreography component meeting agenda (13th April):

1. Actions from last meeting:
	- Antony should speak to Melanie and get the docs up on the website
	- Koustubh will talk to Jim about joining the BPEL TC

2. Discuss how choreography component will provide no API or assets in 4.0

3. Discuss new doc structure in plugin in CVS and request feedback on any other docs people would like to see
	- new FAQ section can act as a summary of decisions made in the minutes (e. g. deployment)
	- possibility of being linked to from main website via ~checkout~ script to ease updates etc

4. Discuss recent developments in BPEL TC with regard to specification finalisation and Issue 147.


Attending:
	Antony Miguel (Scapa)
	Koustubh Parwar (CA)
	Diana Vega (Fokus)

Apologies:

Absent:	
	Harm Sluiman (IBM)
	Serge Lucio (IBM)
	Jim Saliba (CA)
	Kent Siefkes (IBM Rational)
	Joe Toomey (IBM Rational)
	George Din (Fokus)
	Scott Schneider (IBM Rational)
	Srinivas P Doddapaneni (Intel)
	George Christelis (Scapa)
	Shobhit Maini (CA)
	Augustus Kalimuthu (CA)
	Tejas Patel (CA)
	Paul Brown (Fivesight)

Point 1 discussion:

Antony has uploaded docs to the TPTP website.

These docs can be accessed as follows:

	www.eclipse.org
		-> Platform Project
			-> Documentation
				-> Choreography Component

REQUESTED NEW DOC: Small tutorial for beginners with screenshots and examples of what to do to run bpel files.

REQUESTED NEW DOC: How we are using each Web Services standard - what roles they play.

REQUESTED NEW DOC: Flow chart similar to Koustubh's presentation and points to show where web standards fit in and what they do


BPEL specification is about to be finalised (last heard, 18th April) so we don't have a lot of time to influence the specification.

Koustubh has already joined as an observer and is tracking issue 147.  There are a lot of issues and a lot of activity so it's only possible for him to track a small number of issues in depth.

So far: 
	It appears that Issue 63 may be dropped out of the specification - Koustubh will confirm
	Issue 147 has a proposed resolution that may or may not be accepted

Koustubh will try to make some waves and get people to realise that we consider Issue 147 extremely important for the BPEL 2.0 specification.


Point 2 discussion:

The choreography component will produce no assets or external APIs in 4.0.  This is basically because of dependencies on the new agent controller and because of uncertainty about the BPEL specification finalisation date.

As such, choreography development will continue but all UI extensions will be commented out of the plugin.xml file in 4.0.

For any developers that wish to download and test the choreography functionality, they should get a latest version from CVS and then uncomment out the relevant parts in the plugin.xml



Point 3 discussion:

Add a section to overview page that tells people how to request docs and what new docs are planned

Add a link to a ZIP file with all choreography documentation in case people want to download and read offline.  Should probably just be a zipped version of the component sub-website.



Point 4 discussion:

Already covered in point 1 discussion.



Other discussion:

Koustubh: (related to Issue 147) In a BPEL program where we have 100 machines to do load testing using maybe a parallel foreach as proposed in Issue 147, how would we get the multiple threads under the foreach construct to speak to different partner links?

They can all make invocations against the same partner link.  If we want to specify what they are speaking to separately then we can do that by dynamically specifying the endpoint address.  If we want multiple parallel invocations to speak to the same address but have separate connections then we can use correlation sets where each thread correlates on a unique ID and therefore gets a separate port instance to use.

Correlation sets are as yet unsupported by the engine but support will be added soon.

This should be added to the FAQ on the component web site.


Antony: Because of issues with dependencies on the new Agent Controller, Scapa has decided that our 4.1 product will have no dependencies on the new agent controller even in 4.1.  As such, we plan to export all our agents as web services so that they can be accessed directly via the choreography component.  We will in effect be cutting out the TPTP data collection framework.  This will make access via the choreography component more simple and also likely yield some performance improvements.  We may decide to drop our agents and this functionality (direct agent accessibility via the choreography framework) in a later release depending on people's reaction to whether this would be useful to them.

People need time to think about the concept so we will defer discussion to a later meeting


Koustubh: the choreography component currently shows up in the Profiling launch configurations and the Debug launch configurations - is there any reason why it shouldn't show up in the Run?

Antony: no, we show up in the debug because I am about to drop some additions which will allow you to use the debug perspective to pause the engine and see the state of all BPEL threads etc.  We show up in the profiling section because in TPTP we are expecting to run TPTP profiling and monitoring behaviours so it seemed like a reasonable place to show up.

General agreement that we should show up in Debug, Profiling and Run launch configuration sets.


Actions:
	- Antony should add note about correlation sets to FAQ
	- Antony should make specified website changes
	- Koustubh will attempt to make some noise about BPEL TC issue 147.
	- Antony should have engine show up in Run launch config mode too