Mule management console Architecture
Download as PPTX, PDF0 likes578 views
The Mule Management Console (MMC) provides centralized management and monitoring of Mule ESB deployments through a web-based interface. MMC communicates with Mule instances through agents that collect data and apply configuration changes, and stores transaction and environment data in databases. It allows monitoring of applications and transactions across development, testing, and production environments from a single interface.
Mule management console Architecture
- 1. Mule Management Console - architecture Shanky Gupta
- 2. Overview • Mule Management Console (MMC) centralizes management and monitoring functions for all your on-premise Mule ESB Enterprise deployments, whether they are running as standalone instances, as a cluster, or embedded in application servers. • After software developer teams create Mule applications using Anypoint Studio or another IDE, they typically pass the Mule application to another team who deploys the application in a simulated environment for more rigorous testing. Afterwards, the application is run in production with strict requirements to be constantly available, performing at a certain rate, and continually working as expected. Moreover, additional Mule instances and applications may be introduced into the infrastructure, increasing the level of complexity inherent to managing and monitoring all systems.
- 3. Overview …continued • This is where MMC comes in. MMC is an enterprise management and monitoring tool designed specifically for Mule ESB instances. MMC provides a comprehensive set of functionality for managing and monitoring running Mule instances, Mule clusters, applications within Mule instances, and the flows within those applications. It also provides ways of looking at specific transactions through pre-defined business events, as well as transactions in flight. • MMC provides a centralized, convenient, and intuitive web-based interface to monitor, manage, and administer the run-time aspects of Mule ESB. With MMC, you can save time and reduce errors by quickly identifying, diagnosing, and appropriately addressing problems across development, testing, UAT and production environments, all within a single interface.
- 4. Architecture
- 5. 1. Mule ESB Instance(s) The Mule ESB instances monitored by MMC. These can be standalone or embedded instances, or clusters.
- 6. 2. MMC Agent • The MMC agent contained in the Mule instance, which is responsible for: • facilitating data transfer between the Mule instance and the MMC • applying changes (i.e. thread pools, and configuration file changes) to the Mule applications
- 7. 3. The console – MMC web application The MMC instance, the Web-based interface that interacts with Mule through • the MMC agent • JMX functionality exposed by Mule. (For more information on JMX management, see the JMX Management page) The MMC instance is a Web application packaged as a WAR file that executes from within your Web servlet container (i.e. Tomcat, JBoss, etc.).
- 8. 4. Business events – transaction data • The transactional database, that stores business event transactional data collected by the MMC agent within the Mule instance. This database by default is an H2 database, but you can configure MMC to use other relational databases.
- 9. 5. Environment data • The environment database, that stores state information about the various Mule instances and applications managed by MMC, including alerts, deployments, configurations, etc. The database is by default Apache Jackrabbit, but you can configure MMC to use other relational databases.
- 10. 6. MMC Rest API • MMC’s REST interface, which exposes MMC functionality through a REST API. MMC users can invoke this API to programmatically Mule instances paired with MMC.