Summary: The Mule Processing Unit allows you to run Mule within a Processing Unit, thus leveraging all of the Processing Unit and SLA-driven container capabilities.
OverviewOpenSpaces 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. ConfigurationIn 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. PackagingPackaging of the Processing Unit should follow the Processing Unit structure. There are two forms of packaging for Mule enabled processing unit. The first is to simply drop all the required mule jar files (and the required dependencies, except for Spring) in the processing unit "lib" directory and deploy. The other option is to "install" mule into GigaSpaces installation, and put the mule jar files and its dependencies under {{<GigaSpaces Root>\lib\mule}}. For example, here is a basic enablement of Mule into a GigaSpaces installation:
Running/DeployingOnce the Processing Unit is packaged, it can be run using the different options that come with OpenSpaces: |
![]() |
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence |