So you’re using iON to run your Mule application and Maven to manage your development? Great! You’re now ready for the next stage: continuous deployment, which is the easiest way to push your application to iON during your development cycle.
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:
Cargo is a library providing a thin abstraction layer above containers life cycle and applications deployment. Think about integration testing Swiss army knife. It can be used from ant, maven or as a Java library to manipulate most available containers.
Starting today cargo has an open-source Mule implementation.
Mule Management Console 3 ships with both mule2 and mule3 agents. You can monitor all your mule instances from latest MMC and benefit from UI improvements and bug fixes even if you didn’t upgrade to mule3.
MMC 3.1 takes it to another level by introducing backward compatibility support for both agents. Safely upgrades your MMC console without touching mule instances! Everything you already configured will still work and UI will provide access to features depending on agent capacities.
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.
One of the key point of Mule ESB Management Console (MMC) is facilitating administration of your Mule instances.
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.
