As an integration framework and broker, Mule ESB is the platform of choice for implementing and deploying enterprise integration solutions and related services. In this series of posts, I’m going to look at situations beyond the traditional integration scenarios where using Mule ESB has enabled the implementation of effective and elegant solutions.
The Mule ESB team is happy to report that we published the next milestone on our journey to a final Mule 3 release. The focus of Milestone 3 was mostly on internal architecture changes. Some highlights:
MuleMessageAdapter has been dropped, replaced with MuleMessageFactory (read more in this post)
Lifecycle improvements and fixes, although that may affect only users coding against Mule APIs,
Are you looking for a JMS messaging solution that can be deployed and supported with Mule ESB, or as a standalone messaging platform? Are you looking for better performance, stability, management and scalability than ActiveMQ but without the complexity or cost of WebSphere MQ or TIBCO EMS?
On Wednesday May 26, Ken Yagen, VP of Engineering, and Mateo Almenta Reca, Sr. Product Manager, will host a webinar about Mule MQ,
Just as we’re always driving Mule ESB to make it easier to use, we’re also always taking user feedback and revving the Mule Community website to make it easier to find what you need, when you need it. The Mule Community website has a new look, so check it out!
We built MMC based on significant feedback from our customers, and we put the product through two early access pre-releases to incorporate feedback from real users. I must say that I’m pretty pleased with the end result —
Last week, we did a webinar with Terracotta on scaling and managing your web applications running on Tomcat. During the webinar, I did a short demo that showed a Terracotta profile, which makes it super easy to setup the environment required for web applications that use HTTP session clustering using Terracotta.
I previously blogged about how to create a server profile and apply it to servers here. In this case,
Most of our customers are using Tcat to build APIs. Anypoint Platform combines Tcat’s ease of use with built-in management and support. Whatever you’re building and deploying on Tcat, Anypoint Platform gives you agility, reusability, and transparency. Give Anypoint Platform a try for 30 days and see what you think.
Once in a while I get questions about whether Apache Tomcat implements a way to include other files in server.xml, Tomcat’s main configuration file. The answer is that there is a way to do it, and that Tomcat didn’t have to implement a new feature for it to work. The way to do it is: XML entity includes.
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.