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!
We are evaluating using Nagios or a similar Big Brother Enterprise solution for displaying information about our many Enterprise Mule instances, applications and the status of our production and staging environments. The only sure thing is that we presented a budget for buying a couple of 55” monitors and were approved. Pure awesomeness!
This is complicated.
Scalability, Reliability, High Performance: Your business demands it, Mule’s High Availability solution delivers. See why five of the world’s top 10 banks trust Mule to run their business. Join Muley’s Pablo La Greca and Ramiro Rinaudo for a live demonstration of the core components in MuleSoft’s robust High Availability solution.
Mule Enterprise 3.2 introduced a powerful feature allowing to keep track of everything happening during the lifetime of your applications: Business Event Analyzer. This provides a place to monitor business transactions and events across multiple systems. Most businesses need access to information surrounding the following use case examples:
Distributed systems are great: they’re more versatile and resilient than monolithic ones. They also bring challenges of their own, one of them being the difficulty of building a holistic picture of the systems and interactions involved in the processing of a request or the execution of a business activity.
When an issue arises in production it can be quite daunting to reproduce it in a test environment. Ideally one debugs the live application. But logs don’t tell the whole story. And a severe issue may require the application be taken down. How can it be stopped and debugged at the same time? With Mule composite sources and Mule Management Console (MMC) end-point control you can eat your cake and have it,
Mule Management Console 3.1 ships with the brand new Flow Analyzer. Select your server, interesting flows, click start and enjoy seeing real-time messages passing through mule! Click on an debug event and you will see the payload before and after each message processor of your flow.
Out of the box MMC will convert the payload to a string representation using custom toString method if any or by reflectively inspecting its individual fields.
We recently released Mule 3.1 Community and Enterprise editions. In this post, I’d like to introduce Mule 3.1 Enterprise, the first Enterprise release of Mule 3.
Mule 3.1 Enterprise builds on all the great new features in Mule 3 and Mule 3.1 Community, adding a host of enterprise capabilities, including the Mule ESB Management Console (MMC), premium connectors, retry policies for self-healing connections,
On top of all the features we plan for next releases we are starting to think about Mule instance remote bootstrapping. The idea would be to facilitate installation/upgrade of whole mule instances on remote machines, including new ones.