ibi MDM Monitoring and Management Using JMX

The JMX technology allows you to monitor and manage ibi MDM, which is running in either local or remote Java Virtual Machine (JVM).

You can monitor and manage various objects of ibi MDM as they are created, installed, and implemented. JMX handles two types of monitoring:

• Status Monitoring: Collects the statistics to view the current status of a particular operation. For example, how many users are currently logged in to the UI or how many database connections are acquired or released, and so on.
• Performance Monitoring: Uses performance characteristics to monitor and improve ibi MDM’s performance. For example, how much time it takes to run a rulebase or workflow. If the time is too high and it is affecting the performance, you can re-configure the workflow.

You can monitor and manage the following features of ibi MDM:

• Cache - For details, see Cache Statistics and Cache Operations.
• Database - For details, see Database Statistics and Database Operations.
• Hot Deployment - For details, see Hot Deployment Statistics and Hot Deployment Operations.
• HTTP - For details, see HTTP Statistics and HTTP Operations.
• Messaging - For details, see Messaging Statistics and Messaging Operations.
• Patterns - For details, see Patterns Statistics and Patterns Operations.
• Rulebase - For details, see Rulebase Statistics and Rulebase Operations.
• Scheduler Jobs - For details, see Scheduler Jobs Operations.
• Server - For details, see Server Statistics and Server Operations.
• Spark - For details, see Spark Operations.
• UI Login - For details, see UI Login Statistics and UI Login Operations.
• Web Services - For details, see Web Service Statistics and Web Service Operations.
• Workflows - For details, see Workflow Statistics and Workflow Operations.

For information about JMX monitoring, see "Monitoring and Management Using JMX" in the Oracle documentation.

For information about Java JConsole, see Oracle documentation.