Denis Caromel, et al'

1

Model and Architecture, Standards and SOA
Integration

• Denis Caromel, et al.
• OASIS Team
• INRIA -- CNRS - I3S -- Univ. of Nice
  Sophia-Antipolis, IUF
• 3rd ProActive User Group, Nov. 29 2006

1. Architecture and Principles 2. Whats new 3.
ProActive and SOA
2
PlugTests going on
3
PlugTests going on
4
PlugTests going on
5
ProActive
Open Source PROFESSIONAL SUPPORT
6
Inside ProActive

• IDE
• PROGRAMMING
• COMPOSING
• DEPLOYMENT

7
ProActive GUIs

• IC2D Eclipse, TimIt,

8
Interface with The Scientific Free Software
SciLab
9
Major Improvements since 2005 ProActive User
Group

• Restructured and Upgraded Documentation
• Creation of groups of Active Objects in Parallel
• Non Functional Exceptions (NFE)
• OO SPMD (Spanning Tree for Broadcast, MPI to PA
  translation)
• gLite EGEE deployment updated
• Fault-Tolerance and Checkpointing mechanism
• P2P Infrastructure, Load-Balancing
• ProActive Class loader
• Variables in XML descriptors
• Interface with OAR, Easy Deployment on Grid5000

10
Completely New Featuressince 2005 ProActive User
Group

• IC2D as Eclipse Plugin
• Interface (API and GUI) with
• The Scientific Free Software Package SciLab
• TimIt
• MPI Wrapping, Control, and Deployment
• NAS Benchmarks in 100 Java ProActive
• File Transfer (D, E, R)
• OSGi integration

11
ProActive and SOA Integration
12
SOA Main Principles

• Loosely coupled software services to support the
  requirements of business processes (Flexibility,
  Portability)
• A Service-Oriented Architecture is not tied to a
  specific technology
• Information systems for applications built by
  combining loosely coupled and interoperable
  services
• Wrapping of Legacy code
• Service discoverability
• Services inter-operate based on a formal
  definition (or contract, e.g., WSDL, Interfaces)
  
• Independent of development technos and platforms
  (Java, .NET etc).
• Settable Properties declared by the
  implementation
• Configuration of codes by wiring of references to
  specific target services

ProActive A middleware to Program Tightly
Coupled //, Dist, M.-Threaded applications and
seamlessly integrate in SOA
SOA An architecture to Loosely Couple
applications as services
13
ProActive and SOA Integration
14
Conclusion

• Classical Grid Solutions
• Middleware-Centric
• (Underwear-centric)
• Enterprise-Pervasive
• ProActive
• Application-Centric
• Flexibility
• Agility
• Openness
• Customizability

15
(No Transcript)
16
(No Transcript)
17
Perspectives

• Monitoring the Futures