The CHOReOS ‘Large Scale Choreographies for the Future Internet’ European FP7 project that started 2 years ago, and is linked to OW2 Future Internet initiative, has now reached a certain level of maturity that is starting to gives concrete answers on how to move from choreography enactment theory, to its actual practice. More precisely, CHOReOS has defined several methods, toolkits and artifacts to enable this innovative distributed way of coordinating services, while at the same time dealing with some of the inherent difficulties to enacting choreographies in an [Ultra] Large Scale context. For instance, this covers being able to ‘execute’ choreography specifications over a network of discovered, dynamic, Business and Thing-based services. This presentation will cover the aforementioned topics and specific CHOReOS developments that were undertaken in its second year, while putting them in perspective of a simple practice-oriented and business-driven use-case in Air-Traffic Management.

1. © scillystuff on flickr
CHOReOS - Large Scale Choreographies for the FI
from theory to practice
Pierre CHÂTEL – Thales
Template v6
OW2 Annual Conference
November 29, 2012

2. What is CHOReOS?
Choreography-centric SOA for Services & Things
 Why?
Sustaining decentralized service choreographies
In order to support Future Internet, Large Scale
 Focus on Internet of Services and Internet of Things
 How?
Introducing a specific Development Process and Integrated
Development and Runtime Environment (IDRE) for coordination of
services through choreographies
Ultra
Future
CHOReOS Large
Internet
Scale
OW2 Annual Conference
2
November 29, 2012

3. Outline
1. Orchestration vs. Choreography
2. Choreography exemple in Airport UC
3. CHOReOS contributions extract
1. IDRE
2. Development process
3. Choreography synthesis
4. Conclusion
OW2 Annual Conference
3
November 29, 2012

4. Outline
1. Orchestration vs. Choreography
2. Choreography exemple in Airport UC
3. CHOReOS contributions extract
1. IDRE
2. Development process
3. Choreography synthesis
4. Conclusion
OW2 Annual Conference
4
November 29, 2012

5. Orchestration vs. Choreography
Orchestration: Choreography:
 Local / centralized  Global / distributed
perspective perspective
 "Each player in the orchestra  “Dancers dance following a
strictly follows instructions from
the conductor“ global scenario, without a single
point of control“
 SOA: Refers to a business
process, with a specific  SOA: describes a protocol for
(business) goal peer-to-peer interactions
OW2 Annual Conference
5
November 29, 2012

6. Choreographies help deal with FI “…ities”
Scalability
 … in the number of users, service instances,
composed services, …
Heterogeneity
 … in the diversity of service types, technologies, …
Mobility
 … leading to mobile and volatile services…
Awareness & adapability
 … overcoming the volatility of services…
OW2 Annual Conference
6
November 29, 2012

7. Outline
1. Orchestration vs. Choreography
2. Choreography example in Airport UC
3. CHOReOS contributions extract
1. IDRE
2. Development process
3. Choreography synthesis
4. Conclusion
OW2 Annual Conference
7
November 29, 2012

8. Use case
 Passenger-friendly Airport
 Context: air transportation / service to passengers
 Goal: improvements in services, airport fluidity  proof of concept
 CHOReOS innovation highlights
 To enable dynamic rebinding and replacement of services
(loose coupling)
 Distributed coordination
 Partners
 THALES: business Web services provider
 Inria: large scale aspects through Things (sensors, actuators) interoperability
framework
 Linagora: bus provider (EasyESB)
Inside
At home In plane Landed
airport
Image: photostock /
FreeDigitalPhotos.net
OW2 Annual Conference
8
November 29, 2012

9. Use case
 Passengers arrival handling and
tracking at the airport
OW2 Annual Conference
9
November 29, 2012

10. Use case
OW2 Annual Conference
10
November 29, 2012

11. Outline
1. Orchestration vs. Choreography
2. Choreography example in Airport UC
3. CHOReOS contributions extract
1. IDRE
2. Development process
3. Choreography synthesis
4. Conclusion
OW2 Annual Conference
11
November 29, 2012

12. IDRE
The “Integrated Development and Runtime Environment”
 Aim: integrate all CHOReOS components in one platform
Formally Dynamic
grounded choreography-
abstractions and models centric
development process
Integrated
Development and
Runtime
Environment
Service
governance,
verification, and Service-oriented
validation middleware
OW2 Annual Conference
12
November 29, 2012

13. Specific development process
Technology-
independent
characterization of the
“strategy” to be used
during the
choreography life cycle
Usual software
definition activities, but
structured in a
CHOReOS-specific way
High-level development
process model
specified in BPMN2 Deployment and
Execution
OW2 Annual Conference
13
November 29, 2012

14. OW2 Annual Conference
14
November 29, 2012

15. OW2 Annual Conference
15
November 29, 2012

16. Choreography synthesis
From BPMN2 Choreography Specification to (runtime
artifacts) Synthesis and (service) Discovery
 Step 1: BPMN specification  model to model
transformation  choreography labelled state transition
systems (CLTS)
 Choreography global coordination logic specified by the CLTS
 Step 2: Projecting the global coordination logic into
individual expected participant sub-CLTSs
 Expected participants behaviors
 Step 3: Discovery of available services, generation of
Coordination Delegates (CDs) code, based on actual
behaviors + expected behaviors of services
 CDs will manage the services at runtime, based on the
choreography coordination logic
OW2 Annual Conference
16
November 29, 2012

17. Choreography synthesis – Step 1
Airport UC choreography CLTS extract
OW2 Annual Conference
17
November 29, 2012

18. Choreography synthesis: CLT projection – Step 2
Choreography CLTS Projected expected participant CLTSs
OW2 Annual Conference
18
November 29, 2012

19. Choreography synthesis: Airport UC – Step 3
Stand and gate Airport Bus
ATC CD-SGM-
AIR
management Company
CD-ATC CD-ABS- Amenity
AIR Provider
Airport Speaker
Actuators aggregator
CD-AIR- CD-AIR- CD-AIR-
SGM ABC AP
CD-AIR-
Airport ASAA
CD-LHC
CD-AIR- CD-AIR- CD-AIR-
LHC SC ANSA CD-AISA
Luggage Handling
Company Airport infrared
Sensors aggregator
Airport Noise Sensors
Security Company CD-SC
aggregator
OW2 Annual Conference
19
November 29, 2012

20. Conclusion
 Enables choreography-centric SOA
 While Sustaining decentralized service choreographies
 While Supporting Future Internet, Large Scale
 Focusing on IoS and IoT
 Coordination Delegates are the “policemen” of the
choreography and ensure its proper execution/enactment,
following its coordination logic, formally defined by a CLTS
 1/3 of the project time still to be completed, end of the
project on schedule for end of 2013
 All CHOReOS-specific development will be released as
Open Source software (BSD-like license)
OW2 Annual Conference
20
November 29, 2012

21. Contact
http://choreos.eu
 Address :
Pierre CHATEL
Thales Defense &
Security C4I Division
Campus de Polytechnique
1, avenue Augustin Fresnel
91767 Palaiseau Cedex - France
 Mail :
pierre.chatel@thalesgroup.com
 Phone:
+33 (0)1 69 41 55 65
OW2 Annual Conference
21
November 29, 2012