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.
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. Packaging for Mule exampleIn the Mule ESB example, the following jars are required and should be placed under <GigaSpaces Root>\lib\platform\mule backport-util-concurrent-3.1-osgi.jar commons-beanutils-1.7.0-osgi.jar commons-collections-3.2-osgi.jar commons-io-1.3.1-osgi.jar commons-lang-2.4-osgi.jar commons-pool-1.4.jar jug-2.0.0-osgi-asl.jar mule-core-2.2.1.jar mule-module-client-2.2.1.jar mule-module-spring-config-2.2.1.jar mule-module-spring-extras-2.2.1.jar mule-transport-quartz-2.2.1.jar quartz-all-1.6.0-osgi.jar 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 |