Tag: deployment

When building Mule architectures a company will often need to run several instances of Mule ESB: Some on QA, some on staging, and on production, perhaps some instances running locally and some others in another continent. Managing Clusters of Mule Servers, keeping track of what application is running where, and knowing what is the health of those instances at a glance, or even being warned when something wrong happens… That is Mule Enterprise Console job!

So you can use the UI to manage all your geographically distributed instances, but what about automation?

Yes UI is good, but…

Mule 3 had a ton of new improvements.  We’ve talked a lot about flows, cloud connectors and the like and offered webinars on each. Mule 3 also offers a new model to support the of multiple applications and hot of those applications.

Are you looking to learn about how best to deploy Mule and Mule applications?  Should you deploy Mule standalone?  Should you deploy it on an application server? What are the pros and cons of each approach?

Andrew Perepelytsya on Monday, May 24, 2010

Mule 3. Rebooted.

9

Mule 3 Milestone 3 (3.0.0-M3) is ready to hit the streets, and today we’d like to talk about a fundamental transformation that it has undergone. Mind you, it’s not the only one :)

The State of Alaska uses Tcat Server for of its Apache Tomcat servers, and to automate the process for key Tomcat applications.