GCM Components Tutorial

The GCM component model is hierarchical, so components can be either primitives or composites. A composite can contain one or many inner components (primitive or composite). Non functional and functional interfaces can be defined.

ProActive/GCM provides the following defaults non functional interfaces thanks to the following controllers: binding-controller, name-controller, lifecycle-controller, super-controller, content-controller as specified by the GCM specification. In addition, there are other specific controllers in our implementation, namely migration-controller, multicast-controller, gathercast-controller and component-parameters-controller. In the current implementation, the non functional part of a component can also be customized and extended.

Furthermore, ProActive/GCM allows developers to define what a component needs and provides with its client and server interfaces.

By using collective interfaces, component systems designers are able to specify parallelism, synchronization and data distribution. Collective communications refer to multipoint interactions between software entities. Collective interfaces have two types of cardinalities, multicast and gathercast.

A collective interface gives the possibility to manage a group of interfaces as a single entity. This entity is itself an interface and viewed likewise. The role and usage of multicast and gathercast interfaces are complementary.

Multicast interfaces are used for parallel invocations, parameters dispatching and results gathering. A multicast interface is an abstraction for 1-to-n communications. When a single invocation is transformed into a set of invocations, these invocations are forwarded to a set of connected server interfaces. Both the propagation of the invocation and the distribution of the invocation parameters are customizable (through Java annotations in the Java interfaces definitions). The result of an invocation, if it isn’t a void return type, on a multicast interface will be a list of results wherever applicable.

If some parameters in a given method of a multicast interface are lists of values, these values can be distributed in various ways through method invocations to the server interfaces connected to the multicast interface (see Figure 2). The default behaviour –namely broadcast – is to send the same parameters to each of the connected server interfaces (see Figure 2.a). In case some parameters are list of values, copies of the lists are sent to each receiver. However, similar to what SPMD programming model offers, it may be adequate to strip some of the parameters so that the bounded components will work on different data. In MPI, for instance, this can be explicitly specified by stripping a data buffer and using the scatter primitive. In this case, you will use scatter or one-to-one dispatch mode (see Figure 2.b).

Figure 8.2.  Component parameters

GCM also specify result aggregation, but in the current state of the ProActive/GCM implementation the only available behaviour is the aggregation of results as list.

Gathercast interfaces are used for synchronization, parameter gathering and result dispatching. A gathercast interface is an abstraction for n-to-1 communications. It handles data aggregation for invocation parameters, as well as process coordination. It gathers incoming data, and can also coordinate incoming invocations before continuing the invocation flow, by defining synchronization barriers. Invocation parameters are simply gathered into lists of parameters as showed in the Figure 3.

Figure 8.3.  Invocation parameter with a gathercast interface

The following table summarizes the possible distribution policies based on parameters and return type.

Figure 8.4.  Distribution policies

The Architecture Description Language (ADL) is used to define component type, configure and deploy component systems. You can define component and interface types, describe component membrane, and declare on which Virtual Node and you want deploy each component. The architecture of the system is described in one or many XML file.

Components are defined in files ending with the .fractal extension. The syntax of the document is validated against a DTD retrieved from the classpath classpath://org/objectweb/proactive/core/component/adl/xml/proactive.dtd . This DTD extends the Fractal ADL DTD and the implementation reuses and extends the FractalADL project [2]. You can find tutorial and document on ADL in this project1. The GCM specification [1] adds some keywords in the ADL definition which are supported by ProActive/GCM. The following section illustrates how you can use these files to describe a component assembly, and how you can use it with the Fractal/GCM API.

We want to create a primitive component, called PrimitiveComputer. It exposes one server interface called computer-itf which provides the two following methods: compute and doNothing. To do that, we need to write the two following classes.

package org.objectweb.proactive.examples.components.userguide.primitive;

public interface ComputeItf {
   int compute(int a);

   void doNothing();
}

package org.objectweb.proactive.examples.components.userguide.primitive;

import java.io.Serializable;


public class PrimitiveComputer implements ComputeItf, Serializable {
   public PrimitiveComputer() {
   }

   public int compute(int a) {
       int result = a * 2;
       System.err.println(" PrimitiveComputer-->compute(" + a + "): " + result);
       return result;
   }

   public void doNothing() {
       System.err.println(" PrimitiveComputer-->doNothing()");
   }
}

Now, we will discuss on the different ways to use this component. First, we must create the component with the ProActive/GCM framework. Two kinds of component instantiation are shown. In the first case, we can do all these steps in the application. However, in the second case, we will show how we can use the ADL files to simplify the application and create it in a simpler way.

In order to illustrate these different ways, a new class, Main, containing the possible main method of our application (see the source code below), is written. In this main method, four different methods are called and will be described in the following parts of this document, launchFirstPrimitive, launchWithoutADL, launchWithADL, and finally the last launchAndDeployWithADL. To launch this class, you must put in your classpath all the libraries contained in the lib directory and subdirectories and the ProActive jar. And finally, you must set the three Java properties (fractal.provider, java.security.policy, log4j.configuration) as shown in the command line:

java 
  -Dfractal.provider=org.objectweb.proactive.core.component.Fractive 
  -Djava.security.policy=file:<change_this_part>/
                              ProActive/dist/proactive.java.policy 
  -Dlog4j.configuration=file:<change_this_part>/
                             ProActive/dist/proactive-log4j 
  org.objectweb.proactive.examples.components.userguide.Main

package org.objectweb.proactive.examples.components.userguide;

import java.util.HashMap;
import java.util.Map;

import org.objectweb.fractal.adl.Factory;
import org.objectweb.fractal.api.Component;
import org.objectweb.fractal.api.control.LifeCycleController;
import org.objectweb.fractal.api.factory.GenericFactory;
import org.objectweb.fractal.api.type.ComponentType;
import org.objectweb.fractal.api.type.InterfaceType;
import org.objectweb.fractal.api.type.TypeFactory;
import org.objectweb.fractal.util.Fractal;
import org.objectweb.proactive.api.PADeployment;
import org.objectweb.proactive.core.component.Constants;
import org.objectweb.proactive.core.component.ContentDescription;
import org.objectweb.proactive.core.component.ControllerDescription;
import org.objectweb.proactive.core.component.factory.ProActiveGenericFactory;
import org.objectweb.proactive.core.descriptor.data.ProActiveDescriptor;
import org.objectweb.proactive.core.descriptor.data.VirtualNode;
import org.objectweb.proactive.core.node.Node;
import org.objectweb.proactive.examples.components.userguide.primitive.ComputeItf;
import org.objectweb.proactive.examples.components.userguide.primitive.PrimitiveComputer;
import org.objectweb.proactive.examples.components.userguide.primitive.PrimitiveMaster;


public class Main {
   public static void main(String[] args) {
       //        System.out.println("Launch primitive component example");
       //        Main.launchFirstPrimitive();
       System.out.println("Launch component assembly example");
       Main.launchWithoutADL();

       //        System.out.println("Launch and deploy component assembly example");
       //        Main.launchAndDeployWithoutADL();

       //        System.out.println("Launch component assembly example with ADL");
       //        Main.launchOneWithADL();
       //
       //        System.out.println("Launch and deploy component assembly example with ADL");
       //        Main.launchAndDeployWithADL();

       //System.err.println("The END...");
       //System.exit(0);
   }

If we want to create and call components in a standard Java application, we need to use the GCM API [1]. The method launchFirstPrimitive shows all the steps to create and use our first primitive component. Firstly, define the type of the component. Secondly, create component using a factory. Thirdly, start the component. And finally, retrieve the component’s interface and use it as a standard Java object to access our component.

   private static void launchFirstPrimitive() {
       try {
           Component boot = Fractal.getBootstrapComponent();
           TypeFactory typeFact = Fractal.getTypeFactory(boot);
           GenericFactory genericFact = Fractal.getGenericFactory(boot);
           Component primitiveComputer = null;

           // type of PrimitiveComputer component
           ComponentType computerType = typeFact.createFcType(new InterfaceType[] { typeFact
                   .createFcItfType("compute-itf", ComputeItf.class.getName(), TypeFactory.SERVER,
                           TypeFactory.MANDATORY, TypeFactory.SINGLE) });

           // component creation
           primitiveComputer = genericFact.newFcInstance(computerType, new ControllerDescription(
"root",
               Constants.PRIMITIVE), new ContentDescription(PrimitiveComputer.class.getName()));

           // start PrimitiveComputer component
           Fractal.getLifeCycleController(primitiveComputer).startFc();
           ((LifeCycleController) primitiveComputer.getFcInterface("lifecycle-controller"
)).startFc();

           // get the compute-itf interface
           ComputeItf itf = ((ComputeItf) primitiveComputer.getFcInterface("compute-itf"));
           ;
           // call component
           itf.doNothing();
           int result = itf.compute(5);

           System.out.println("Result of computation whith 5 is: " + result); //display 10
       } catch (Exception e) {
           e.printStackTrace();
       }
   }

Uncomment the line calling the launchFirstPrimitive method in the main method, launch it and see below the expected output. The first lines are ProActive log, and at the end, information printed in the component and in the Main class is visible.

Now that we succeeded to create and use a primitive component, we will learn how to use it in a component assembly. First of all, we want use the previous shown primitive component with another primitive component to explain how to define, implement and use client interfaces. Moreover, in order to use composite component, we put the two primitive components in a composite. The Figure 8.5, “Component assembly ” shows this assembly.

Figure 8.5. Component assembly

To implement this assembly we need one more class, PrimitiveMaster. This class implements the following Java interfaces: java.lang.Runnable and moreover the BindindController to allow binding on the compute-itf client interface. In the run method we put the call to the PrimitiveComputer component, we don’t need to retrieve the compute-itf interface since the assembling it’s done in the launchWithoutADL method or in the following part using ADL.

package org.objectweb.proactive.examples.components.userguide.primitive;

import java.io.Serializable;

import org.objectweb.fractal.api.NoSuchInterfaceException;
import org.objectweb.fractal.api.control.BindingController;
import org.objectweb.fractal.api.control.IllegalBindingException;
import org.objectweb.fractal.api.control.IllegalLifeCycleException;


public class PrimitiveMaster implements Runnable, Serializable, BindingController {
   private static final String COMPUTER_CLIENT_ITF = "compute-itf";
   private ComputeItf computer;

   public PrimitiveMaster() {
   }

   public void run() {
       computer.doNothing();
       int result = computer.compute(5);
       System.out.println(" PrimitiveMaster-->run(): " + "Result of computation whith 5 is: " +
 result); //display 10
   }

   //BINDING CONTROLLER implementation
   public void bindFc(String myClientItf, Object serverItf) throws NoSuchInterfaceException,
           IllegalBindingException, IllegalLifeCycleException {
       if (myClientItf.equals(COMPUTER_CLIENT_ITF)) {
           computer = (ComputeItf) serverItf;
       }
   }

   public String[] listFc() {
       return new String[] { COMPUTER_CLIENT_ITF };
   }

   public Object lookupFc(String itf) throws NoSuchInterfaceException {
       if (itf.equals(COMPUTER_CLIENT_ITF)) {
           return computer;
       }
       return null;
   }

   public void unbindFc(String itf) throws NoSuchInterfaceException, IllegalBindingException,
           IllegalLifeCycleException {
       if (itf.equals(COMPUTER_CLIENT_ITF)) {
           computer = null;
       }
   }
}

In the launchWithoutADL method, we extend component type definition and component creation parts. And we add one more part, the component assembling. In this part, at first we put the two primitives, PrimitiveComputer and PrimitiveMaster in the composite component. Next, we make the binding between each component interfaces.

   private static void launchWithoutADL() {
       try {
           Component boot = Fractal.getBootstrapComponent();
           TypeFactory typeFact = Fractal.getTypeFactory(boot);
           GenericFactory genericFact = Fractal.getGenericFactory(boot);

           // component types: PrimitiveComputer, PrimitiveMaster, CompositeWrapper
           ComponentType computerType = typeFact.createFcType(new InterfaceType[] { typeFact
                   .createFcItfType("compute-itf", ComputeItf.class.getName(), TypeFactory.SERVER,
                           TypeFactory.MANDATORY, TypeFactory.SINGLE) });
           ComponentType masterType = typeFact.createFcType(new InterfaceType[] {
                   typeFact.createFcItfType("run", Runnable.class.getName(), TypeFactory.SERVER,
                           TypeFactory.MANDATORY, TypeFactory.SINGLE),
                   typeFact.createFcItfType("compute-itf", ComputeItf.class.getName(),
 TypeFactory.CLIENT,
                           TypeFactory.MANDATORY, TypeFactory.SINGLE) });
           ComponentType wrapperType = typeFact.createFcType(new InterfaceType[] {
 typeFact.createFcItfType(
                   "run", Runnable.class.getName(), TypeFactory.SERVER, TypeFactory.MANDATORY,
                   TypeFactory.SINGLE) });

           // components creation
           Component primitiveComputer = genericFact.newFcInstance(computerType, new
 ControllerDescription(
               "PrimitiveComputer", Constants.PRIMITIVE), new ContentDescription(PrimitiveComputer.
class
                   .getName()));
           Component primitiveMaster = genericFact.newFcInstance(masterType, new
 ControllerDescription(
               "PrimitiveMaster", Constants.PRIMITIVE), new ContentDescription(PrimitiveMaster.
class
                   .getName()));
           Component compositeWrapper = genericFact.newFcInstance(wrapperType, new
 ControllerDescription(
               "CompositeWrapper", Constants.COMPOSITE), null);

           // component assembling
           Fractal.getContentController(compositeWrapper).addFcSubComponent(primitiveComputer);
           Fractal.getContentController(compositeWrapper).addFcSubComponent(primitiveMaster);
           Fractal.getBindingController(compositeWrapper).bindFc("run",
                   primitiveMaster.getFcInterface("run"));
           Fractal.getBindingController(primitiveMaster).bindFc("compute-itf",
                   primitiveComputer.getFcInterface("compute-itf"));

           // start CompositeWrapper component
           Fractal.getLifeCycleController(compositeWrapper).startFc();

           // get the run interface
           Runnable itf = ((Runnable) compositeWrapper.getFcInterface("run"));

           // call component
           itf.run();
       } catch (Exception e) {
           e.printStackTrace();
       }
   }

This way isn’t the simplest one to create and use component. There is a lot of code to write, that could introduce mistakes or errors in an assembly. We will show an easier one next.