1. Right click on the projects panel
   • Choose New Project …, SOA category and BPEL Module project.
   • Click the Next button.
2. Choose a meaningful name as Project Name,
   • Use the $JSEDUITE_HOME/orchestrations folder as Project Location
   • Click the Finish button.

1. Right click on the Process Files directory, and choose New, Folder …
   • Name it Partners
2. Right click on this newly createdfolder, and choose New / External WSDL Document …
   • Select the From Local File System option, and browse to the $JSEDUITE_HOME/architecture/contracts directory
   • Pick up all WSDL interface description you'll need as partner of this orchestration
   • Tips: Even if it's not mentioned, you can pick up a set of file in this wizard

This section assumes you're familiar with BPEL process development using the Netbeans environment. It essentially focuses on expressing naming conventions.

• Important readings: http://www.netbeans.org/kb/trails/soa.html

1. Right click on the Process Files, and choose New / Xml Schema …
   • Use OrchestrationName as FileName
   • Edit the Target Namespace to match the following naming convention:
     • http://provider/jSeduite/orchestrations/schema/OrchestrationName
     • e.g. http://modalis.i3s.unice.fr/jSeduite/orchestrations/schema/WeatherProxy
2. Switch to the Design view, and add:
   • If you're manipulating complex data structures: Complex Types describing such structures
   • Invocation message:
     • Define an OperationNameIn complex type which represents the structure of expected input messages
     • Replace In by Out in the previous sentence to describe expected output messages.
   • Invocation elements: Following the Document Literal standard, request and response message MUST be defined as elements/
     • Define an OperationNameRequest element, of type OperationNameIn.
     • Replace Request by Response and In by Out
3. You newly created data model should be ok
   • Choose the Run menu, and then Validate XML
   • The XML Check window will pop, and must say 0 Error(s).

1. Right click on the root project, and choose New, WSDL Document …
   • Warning : WSDL Document … is a definitively different wizard than the External WSDL Document(s) … one.
   • Choose OrchestrationName as File Name
   • Edit the Target Namespace to match the following naming convention:
     • http://provider/jSeduite/orchestrations/wsdl/OrchestrationName
     • e.g. http://modalis.i3s.unice.fr/jSeduite/orchestrations/wsdl/WeatherProxy
   • Tick the Import XML Schema File(s) check box, and load the OrchestrationName.xsd file.
   • Click on the Next button.
2. Customize the Abstract Configuration:
   • Replace the Operation Name by a meaningful name (CamelCase convention, first letter in upper case).
   • Edit the Input part:
     • Rename part1 as in
     • Change its element to the OperationNameRequest one.
   • Edit the Output part: (replace in by out and request by response).
3. Customize the Concrete Configuration:
   • Select the Document Literal binding subtype

1. Right click on the project root, and choose New, BPEL Process …
   • Use OrchestrationName as File Name.
   • Change the Target Namespace to match the following naming convention:
     • http://provider/jSeduite/orchestrations/bpel/OrchestrationName
     • e.g. http://modalis.i3s.unice.fr/jSeduite/orchestrations/bpel/WeatherProxy
2. Import the public interface:
   • Just drag'n drop the WSDL file on the left part of the designer
   • Rename the partner link as external (instead of PartnerLink1 or whatever)
3. Import all partners inside the process
   • For each partner, drag'n drop ots WSDL file on the right part of the designer
   • Use an explicit Name (i.e. partner's name)
4. Implements your BPEL process !!

1. Right click on the left panel, and chosse New / SOA, Composite Application Project.
   • Use the OrchestrationNameComponent naming convention
   • Be sure that Project Folder is under orchestrations folder.
2. Once finished, right click on the project root, and choose Add JBI Module …
   • Select the OrchestrationName project
   • Click on the Add Project JAR Files button to wrap the process into a JBI Module
3. Right click on the project root, and choose the Clean And Build action
4. Right click on the Test folder, and add a New Test case.
   • The name will be Invoker (as we'll use it to invoke the process), click Next.
   • Choose OrchestrationName.wsdl from the OrchestrationName folder, click Next
   • Select the OperationName binding operation, click finish
5. Edit the XML Input message to send meaningful data
6. Right click on the Invoker test case, end choose Run !

You'll have to publish your WSDL contract (and XSD data model) into the $JSEDUITE_HOME/architecture/contracts folder.

• A script called add_bpel_contract.sh can help you to perform such a task:

mosser@asmodeus:$JEDUITE_HOME/architecture$ ./add_bpel_contract.sh FeedReader
# Retrieving XSD data model [Partners => '']
../orchestrations/FeedReader/src/FeedReader.xsd -> contracts/FeedReader.xsd
# Retrieving WSDL descripton [HttpDefaultPort => 9080]
../orchestrations/FeedReader/src/FeedReader.wsdl -> contracts/FeedReader.wsdl 
mosser@asmodeus:$JEDUITE_HOME/architecture$ svn add contracts/FeedReader.*
A         contracts/FeedReader.wsdl
A         contracts/FeedReader.xsd
mosser@asmodeus:$JEDUITE_HOME/architecture$

1. Select all the relevant projects
   • i.e. OrchestrationName and OrchestrationNameComponent
   • right click and select Subversion / Commit …
2. Enter a commit log message describing the orchestration