First Look at JMX MBean Support in iWay Service Manager 9.2

[Artem]

Java Management Extensions (JMX) is a technology that provides tools for managing and monitoring applications, system objects, devices, and service-oriented networks. iWay Service Manager exposes custom MBeans which gives users access to crucial metrics such as listener status, worker counts, and execution metrics, enabling enhanced monitoring and management of the system's performance. By leveraging JMX, administrators can gain real-time insights and execute management operations seamlessly, ensuring optimal functionality and responsiveness of the software.

You can access JMX locally, connecting directly within the same Java Virtual Machine (JVM) using an in-process connection. This method ensures efficient and secure interactions with the MBeans. For remote access, set up a connector server to expose the MBean server over network protocols like RMI or JMXMP. This allows you to manage the application from different machines. Make sure to configure security features such as authentication and encryption to protect communications during remote access. By following these steps, you can effectively use JMX to manage and monitor your iSM applications in various environments.

Please refer to this Oracle guide for further details on how to setup remote JMX access.

The picture below shows a local connection to an iSM instance using Java VisualVM. On the MBeans tab you can browse for iSM listener components by looking under com.ibi.edaqm package. Here you can see we have a single File listener "simple_inlet.1_listener.1". The Attributes tab displays a table with various attributes that can be used to monitor the listener.

 

Exposed listener attributes are summarized below.

state	Returns the server state [inactive, begin, retry, config, active, stopping, stopped, waiting, license]
stateMessage	Returns error message if available when state is "config" or "retry"
uptime	How long the listener has been running in seconds
countWorkers	Total number of workers
countFreeWorkers	Count of workers currently waiting for work
countCompleted	Number of successfully processed messages
countFailed	Number of failed messages
countInProcess	Number of messages currently in-process
countPending	Number of pending messages
countRetries	Number of retries
countTimedOut	Number of timed out messages
statsCount	Total number of messages with collected statistics
statsMinExecTimeCPU	Minimum execution time in seconds (system mode)
statsMaxExecTimeCPU	Maximum execution time in seconds (system mode)
statsAvgExecTimeCPU	Average execution time in seconds (system mode)
statsVarianceCPU	Variance in seconds (system mode)
statsErlangCPU	Erlang distribution (system mode)
statsMsgRateCPU	Rate of processing messages per second (system mode)
statsStdDevCPU	Standard deviation in seconds (system mode)
statsMinExecTimeUser	Minimum execution time in seconds (user mode)
statsMaxExecTimeUser	Maximum execution time in seconds (user mode)
statsAvgExecTimeUser	Average execution time in seconds (user mode)
statsVarianceUser	Variance in seconds (user mode)
statsErlangUser	Erlang distribution (user mode)
statsMsgRateUser	Rate of processing messages per second (user mode)
statsStdDevUser	Standard deviation in seconds (user mode)
statsMinExecTimeWall	Minimum execution time in seconds (wall clock)
statsMaxExecTimeWall	Maximum execution time in seconds (wall clock)
statsAvgExecTimeWall	Average execution time in seconds (wall clock)
statsVarianceWall	Variance in seconds (wall clock)
statsErlangWall	Erlang distribution (wall clock)
statsMsgRateWall	Rate of processing messages per second (wall clock)
statsStdDevWall	Standard deviation in seconds (wall clock)

 

Looking under the Metadata tab of VisualVM, you can see a table describing the MBean and its attributes.

 

JDBC Providers are also exposed as MBeans.

Edited July 3 by Artem