The Lamaxu docker image comes bundled with a free one(1) queue manager license.
Container Repository
https://hub.docker.com/r/queuemetrix/lamaxu
Docker command
The command below will pull the latest docker image. Please use a specific version TAG for older images.
docker pull queuemetrix/lamaxu
LAMAXU JMX enables the monitoring of IBM MQ resources using standard Java JMX technology by instrumenting WMQ objects like queue managers, queue/subscriber and channel statuses etc, in the Java programming language. WMQ objects are exposed as MBeans in order to implement access to the objects’ instrumentation.
The JMX technology integrates with existing monitoring/management solutions and emerging technologies. The JMX APIs are open interfaces that any management system vendor can implement. JMX solutions can use look-up and discovery services and protocols such as Jini network technology and the Service Location Protocol (SLP).
The JMX architecture is divided into three levels:
To manage resources using the JMX technology, you must first instrument the resources in the Java programming language. You use Java objects known as MBeans to implement the access to the resources’ instrumentation. MBeans must follow the design patterns and interfaces defined in the JMX specification. Doing so ensures that all MBeans provide managed resource instrumentation in a standardized way. In addition to standard MBeans, the JMX specification also defines a special type of MBean called an MXBean. An MXBean is an MBean that references only a pre-defined set of data types. Other types of MBean exist, but this trail will concentrate on standard MBeans and MXBeans.
Once a resource has been instrumented by MBeans, it can be managed through a JMX agent. MBeans do not require knowledge of the JMX agent with which they will operate.
MBeans are designed to be flexible, simple, and easy to implement. Developers of applications, systems, and networks can make their products manageable in a standard way without having to understand or invest in complex management systems. Existing resources can be made manageable with minimum effort.
In addition, the instrumentation level of the JMX specification provides a notification mechanism. This mechanism enables MBeans to generate and propagate notification events to components of the other levels.
A JMX technology-based agent (JMX agent) is a standard management agent that directly controls resources and makes them available to remote management applications. JMX agents are usually located on the same machine as the resources they control, but this arrangement is not a requirement.
When you implement a JMX agent, you do not need to know the semantics or functions of the resources that it will manage. In fact, a JMX agent does not even need to know which resources it will serve because any resource instrumented in compliance with the JMX specification can use any JMX agent that offers the services that the resource requires. Similarly, the JMX agent does not need to know the functions of the management applications that will access it.
The core component of the LAMAXU JMX agent is the MBean server, a managed object server in which MBeans are registered. The LAMAXU JMX agent also includes a set of services to manage MBeans, and at least one communications adapter or connector to allow access by a management application.
JMX technology instrumentation can be accessed in many different ways, either through existing management protocols such as the Simple Network Management Protocol (SNMP) or through proprietary protocols. The MBean server relies on protocol adapters and connectors to make a JMX agent accessible from management applications outside the agent’s Java Virtual Machine (Java VM).
Each adapter provides a view through a specific protocol of all MBeans that are registered in the MBean server. For example, an HTML adapter could display an MBean in a browser.
Connectors provide a manager-side interface that handles the communication between manager and JMX agent. Each connector provides the same remote management interface through a different protocol. When a remote management application uses this interface, it can connect to a JMX agent transparently through the network, regardless of the protocol. The JMX technology provides a standard solution for exporting JMX technology instrumentation to remote applications based on Java Remote Method Invocation (Java RMI).
Queuemetrix Lamaxu extends the monitoring capability of solarwinds SAM by enabling the monitoring of IBM MQ message flows and metrics.
LAMAXU interfaces natively with solarwinds ® using standard Java JMX MBeans, making IBM MQ appear just like a Java Application Server.
Queuemetrix Gatekeeper is an Open Source LDAP security authentication plugin for IBM MQ that provides a secure way for MQ TCP clients to connect to MQ. It uses a client authentication exit module to extend the functionality of MQ to provide a method for JMS and other types of client connections to be authenticated using standard LDAP Simple bind authentication.
The Exit allows Queuemetrix Lamaxu to use AD username/password authentication on MQ versions prior to version 8.
The module itself is called a ‘security channel exit’ and is named libMQGatekeeper. The module is deployed to an MQ server and is used to protect client MQ connections by providing username and password authentication against an enterprises single sign-on (SSO) such as LDAPS or Microsoft’s Active Directory. Authenticated users can also be restricted to those that are members of specific AD/LDAP groups.
Client passwords are protected during channel authentication by using standard MQ one way SSL/TLS encryption.
The module provides a number of key security features such as,
Recent Comments