Overview

OpenSpaces allows to configure, package and deploy a Processing Unit. The OpenSpaces Mule integration allows you to run a pure Mule application (with or without OpenSpaces special extension points and transports) as a Processing Unit.

Configuration

In order to run Mule as a Processing Unit within the pu.xml file (which is a Spring application context), the following needs to be defined:

<bean class="org.openspaces.esb.mule.pu.OpenSpacesMuleContextLoader">
    <property name="location" value="/META-INF/spring/mule.xml"/>
</bean>

In the example above, the OpenSpacesMuleContextLoader loads a Mule application as defined in the mule.xml configuration file. The location parameter is optional and defaults to the value specified in the example above.

Packaging

Packaging of the Processing Unit should follow the Processing Unit structure.

When deploying a Processing Unit into the SLA-driven container, Mule JAR files should be "installed" into the GigaSpaces installation (on each node). The following minimum set of JARs need to be copied into <GigaSpaces Root>\lib\platform\mule (if the Mule directory does not exists, create it).

• Copy the following JAR files from <Mule Root>\lib\mule to <GigaSpaces Root>\lib\mule: mule-core,
  mule-module-spring-config, mule-module-spring-extras. Other transports (if used) should be copied as well.
• Copy the following JAR files from <Mule Root>\lib\opt to <GigaSpaces Root>\lib\mule: commons-beanutils, commons-collections, commons-io, commons-lang, commons-pool, jug-2.0.0-asl, backport-util-concurrent. Other required JAR files can be copied as well (or they can be put in the Processing Unit lib directory).

Note, since version 7.0, the required mule jar files can also be placed within the processing unit lib directory, without "installing" mule into each GSC node installation.

Running/Deploying

Once the Processing Unit is packaged, it can be run using the different options that come with OpenSpaces:

• Standalone
• SLA driven container