Mule integrates with jBPM, allowing you to send/receive messages to/from a running process. A message from Mule can start or advance a process, the message can be used as a process variable, and a process can send messages to any endpoint in your Mule config.
In a recent post by Loraine Lawson on ITBusinessEdge, an informal survey was cited that referenced a majority of mid-market CIOs who “said they had no current business need for SOA.” I was a little surprised by the headline since MuleSoft continues to see tremendous adoption of our open source Mule ESB and subscriptions of our enterprise version among companies I would describe as mid-market. So, I decided to read further and try to learn more.
With the release of Mule ESB 2.2.4 Enterprise Edition, there are several new and interesting capabilities that have been enhanced in Mule. Reading through the release notes, you might miss them, so I decided to highlight them here on the blog.
Mule has had support for WS-Security via CXF for some time now, but Mule 2.2.4 Enterprise goes a bit further still with the inclusion of the Mule SAML Module and a new WS-Security example. In this article, I will step through the WS-Security example so that you can see the different possibilities available for incorporating WS-Security into your Mule application.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.