List of Figures

1.1. ProActive Features

1.2. MOP architecture

5.1. The active objects in the c3d application

5.2. A GUI is started that illustrates the activities of the Reader and Writer objects.

5.3. The Dining Philosophers Example

5.4. Informal description of the C3D Components hierarchy

6.1. Client-Server architecture - the Main class acts as a client and uses the CMAgent class as a server

6.2. CMA Architecture and Skeleton Code Using intialization

6.3. Deployment process

6.4. Distribution of the Test Range (Example with 2 Workers)

6.5. Architecture of the Distributed Version

6.6. Killing a JVM from IC2D

6.7. Architecture of the Master-Worker Version

7.1. Component with inner component distributed

7.2. Component parameters

7.3. Invocation parameter with a gathercast interface

7.4. Distribution policies

7.5. Component assembly

8.1. Three different computational models

8.2. Proactive Active Object structure

9.1. PAActiveObject class

9.2. Activity algorithm

9.3. The components of an active object and of a referencing object

9.4. A future object

9.5. Single-threaded version of the program

9.6. The components of an active object and of a referencing object

9.7. The components of a future object before the result is set

9.8. All components of a future object

9.9. Call flow when a future is set before being used

9.10. Call flow when the future is not set before being used (wait-by-necessity)

10.1. PAGroup class and Group interface

13.1. Master-Worker API main class

13.2. Deployment of the Master-Worker framework

13.3. Tasks definition and submission

13.4. Results gathering

14.1. Task Flow in Calcium

15.1.

15.2. Behaviour example of a total barrier

16.1. File transfer and asking for resources

16.2. State transition diagram

16.3. MPI to ProActive communication

16.4. ProActive to MPI communication

16.5. File transfer and asking for resources

16.6. Jacobi Relaxation - Domain Decomposition

16.7. IC2D Snapshot

16.8. Proxy Pattern

16.9. Process Package Architecture

21.1. File Transfer Design

26.1. Multicast interfaces for primitive and composite component

26.2. Broadcast and scatter of invocation parameters

26.3. Comparison of signatures of methods between client multicast interfaces and server interfaces.

26.4. Gathercast interfaces for primitive and composite components

26.5. Aggregation of parameters with a gathercast interface

26.6. Comparison of signature of methods for bindings to a gathercast interface

26.7. Example: architecture of a naive solution for secure communications

26.8. Structure for the membrane of Fractal/GCM components

26.9. The primitives for managing the membrane.

26.10. Higher level API

26.11. Using shortcuts for minimizing remote communications.

27.1. ProActive's Meta-Objects Protocol.

27.2. The ProActive MOP with component meta-objects and component representative

28.1. Client and Server wrapped in composite components (C and S)

28.2. Without wrappers, the primitive components are distributed.

28.3. With wrappers, where again, only the primitive components are distributed.

32.1. The nbody application, with Fault-Tolerance enabled

33.1. Setting up virtual distributed sandboxs at runtime

33.2. Certificate chain

33.3. Hierarchical security

33.4. Syntax and attributes for policy rules

33.5. Hierarchical Security Levels

33.6. The ProActive Certificate Generator (for oasis)

33.7. The ProActive Certificate Generator (for proactive)

33.8. The ProActive Certificate Generator (for proactive)

33.9. The ProActive Certificate Generator (for proactive)

33.10. The ProActive Certificate Generator (for proactive)

33.11. The ProActive Certificate Generator (for proactive)

34.1. This figure shows the steps when an active object is called via SOAP.

34.2. The dispatcher handling all calls

34.3. The first screenshot is a classic ProActive application

34.4. C# application communicating via SOAP

35.1. The OSGi framework entities

35.2. The Proactive Bundle uses the standard Http Service

36.1. This figure shows the JMX 3 levels architecture and the integration of the ProActive JMX Connector.

38.1. A Drawing using the FIGURE tag

38.2. Main ant targets used in manual generation

40.1. core.process structure

43.1. Metabehavior hierarchy

44.1. The API architecture.

44.2. Broadcasting a new solution.

45.1. Usage example P2P network (after firsts connections)

45.2. A P2P Service which is sharing nodes deployed by a descriptor

45.3. A network of hosts with some running the P2P Service

45.4. New peer trying to join a P2P network

45.5. Heart beat sent every TTU

45.6. Asking nodes to acquaintances and getting a node

45.7. Nodes and Active Objects which make up a P2P Service.

45.8. Dynamic Shared ProActive Typed Group.

45.9. nBody application deployed on P2P Infrastructure.