SwiftMQ Documentation

SwiftMQ Documentation

  • Client
  • CE
  • UR
  • HA
  • Javadocs
  • Release Notes

›Administration

SwiftMQ Client

  • Getting Started
  • JNDI Client
  • JMS Client
  • AMQP 1.0 Client
  • Filetransfer Client

SwiftMQ CE

  • Getting Started
  • Installation
  • Upgrade
  • Software Architecture
  • Administration

    • Preconfig
    • CLI Command Line Interface
    • JMX Administration
    • CLI Message Interface
    • routerconfig.xml Watch Dog
    • System Properties

    Swiftlets

    • AMQP Swiftlet
    • Authentication Swiftlet
    • Deploy Swiftlet
    • JMS Swiftlet
    • JNDI Swiftlet
    • Log Swiftlet
    • Management Swiftlet
    • MQTT Swiftlet
    • Network Swiftlet
    • Queue Manager Swiftlet
    • Routing Swiftlet
    • Scheduler Swiftlet
    • Store Swiftlet
    • Streams Swiftlet
    • Threadpool Swiftlet
    • Timer Swiftlet
    • Topic Manager Swiftlet
    • Trace Swiftlet
    • XA Resource Manager Swiftlet

    APIs

    • CLI Admin API

    How To

    • TLS Configuration
    • HTTP Tunneling Configuration
    • Upgrade SwiftMQ Router and Clients

    In Depth

    • Versioning
    • File Store

SwiftMQ UR

  • Getting Started
  • License
  • Installation
  • Upgrade
  • Administration

    • SwiftMQ Explorer

    Swiftlets

    • JDBC Authentication Swiftlet
    • FileCache Swiftlet
    • JMS Application Container Swiftlet
    • JMS XA Swiftlet
    • JDBC Store Swiftlet
    • AMQP Bridge Extension Swiftlet
    • JMS Bridge Extension Swiftlet
    • JavaMail Bridge Extension Swiftlet
    • Replicator Extension Swiftlet

SwiftMQ HA

  • Getting Started
  • License
  • Installation
  • Upgrade
  • HA Introduction
  • HA Deployment
  • Administration
  • JNDI/JMS under HA
  • Routing under HA
  • Advanced Configuration
  • HA Test Suite

JMX Administration

Enabling JMX

JMX support is disabled by default. To use it, it must be enabled in the Management Swiftlet.

MBeans

SwiftMQ wraps the router's management tree with MBeans. It creates one MBean per Entity. The object names of the MBeans are equal to the CLI context names. It is configurable whether these names are created in a grouped fashion or as flat names. It depends on the JMX administration tool whether it is able to form a hierarchy like in SwiftMQ Explorer or not. jConsole, the tool delivered with the JDK, is able and we will use it here as an example.

JMX Management with jConsole

Start the SwiftMQ Router with JMX enabled. Then start jConsole. If JDK 1.5 is in your path, a simple

      jconsole

should do it. jConsole discovers the running JVMs and displays a connect dialog for those which have JMX access enabled:

After connect switch to the MBeans tab:

Under the left tree you'll see the different JMX domains. Your SwiftMQ Router is under domain com.swiftmq. appended with the router name. Expand the SwiftMQ domain node and you will see the router's management tree just like in SwiftMQ Explorer:

You can now do everything just like in SwiftMQ Explorer. For example, to create a new queue, go to sys$queuemanager, queues and click on the right Operations tab. Then fill the parameters of the new operation and click the new button:

To view the message count of a queue, go to sys$queuemanager, usage, click the queue name and then at the Attributes tab. Click on "messagecount ` to display a chart:

There is one special MBean to expose router specific commands like halt, reboot, save. This MBean's object name is the router's name. Click on this node and then on the Operations tab to see these commands:

← CLI Command Line InterfaceCLI Message Interface →
  • Enabling JMX
  • MBeans
  • JMX Management with jConsole
Copyright © 2020 IIT Software GmbH