Mule provides SEDA models for message processing, but that may not be enough if the application demands a more robust queuing mechanism that requires persistence or clustering. An external queuing broker may need to be configured in such instances. This example shows how to configure the Mule JMS connector for interacting with OpenMQ.
Note from the editor: This is an embedded Spring configuration file in Mule, and requires that the user also define a Spring context in the Mule configuration. This configuration may vary slightly if Mule is running in stand-alone mode. Refer to the Mule 2.0 documentation for details (requires free log in).
Before modifying Mule config file, make sure you have configured OpenMQ properly. This partial listing shows how to set the Mule config file up once OpenMQ is executing: com.sun.jndi.fscontext.RefFSContextFactory file:///C:/pawan/openMQ/mq com.sun.jndi.fscontext.RefFSContextFactory 1.1 file:///C:/Temp I hope this post is informative & useful for the community.