JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server Message Queue 4.5 Technical Overview
search filter icon
search icon

Document Information


1.  Messaging Systems: An Introduction

2.  Client Programming Model

3.  The Message Queue Broker

Broker Services

Connection Services

Port Mapper Service

Thread Pool Management

Message Delivery Services

Physical Destinations

Managing Destinations

Configuring Physical Destinations

Managing Memory

Destination Message Limits

System-Wide Message Limits

System Memory Thresholds

Persistence Services

File-Based Persistence

JDBC-Based Persistence

Security Services

Authentication and Authorization

JAAS-Based Authentication


Bridge Services

JMS Bridge Service

STOMP Bridge Service

Monitoring Services

Metrics Generator


Metrics Message Producer

JMX MBeans

Java ES Monitoring Framework Support

Administration Tools

Built-in Administration Tools

JMX-Based Administration

Administration Tasks

Supporting a Development Environment

Supporting a Production Environment

Setup Operations

Maintenance Operations

4.  Broker Clusters

5.  Message Queue and Java EE

A.  Message Queue Implementation of Optional JMS Functionality

B.  Message Queue Features



Administration Tools

This section describes the tools you use to configure and manageMessage Queue broker services. The tools fall into two categories:

Built-in Administration Tools

The following illustration shows the administration tools provided by Message Queue for configuring and managing broker services.

Figure 3-4 Message Queue Administration Tools

image:Figure shows which tools the administrator uses to control which Message Queue Service components. Figure explained in text.

The administration tools include the following command line interfaces:

In addition to the command line utilities shown in Figure 3-4,Message Queue administration tools also include the GUI-based Administration Console. The Administration Console combines some of the capabilities of the Command utility (imqcmd) and the Object Manager utility (imqobjmgr). You can use it to do the following:

JMX-Based Administration

To serve customers who need a standard programmatic means to monitor and access the broker, Message Queue also supports the Java Management Extensions (JMX) architecture, which allows a Java application to manage broker resources programmatically.

The JMX specification defines an architecture for the instrumentation and programmatic management of distributed resources. This architecture is based on the notion of a managed bean, or MBean: a Java object, similar to a JavaBean, representing a resource to be managed. Message Queue MBeans are associated with individual resources such as connection services, connections, or destinations, or with whole categories of resources, such as the set of all destinations on a broker. There are separate configuration MBeans and monitor MBeans for setting a resource’s configuration properties and monitoring its runtime state.

Java applications access MBeans through remote method invocation (RMI) protocols. The MBeans are hosted by an MBean server in the broker, which functions as an MBean container. The MBean server is accessed by means of a RMI connector, which is used to obtain an MBean server connection, which, in turn, provides access to the individual MBeans.

The JMX specification defines an architecture that enables the programmatic management of any distributed resource. This architecture is defined by design patterns, APIs, and various services.

JMX-based administration provides dynamic, fine grained, programmatic access to the broker. You can use this kind of administration in a number of ways.

JMX is the Java standard for building management applications and is widely used for managing Java EE infrastructure. If your Message Queue client is a part of a larger Java EE deployment, JMX support allows you to use a standard programmatic management framework throughout your Java EE application. Message Queue is based on the JMX 1.2 specification, which is part of JDK 1.5.

To manage a Message Queue broker using the JMX architecture, see Oracle GlassFish Server Message Queue 4.5 Developer’s Guide for JMX Clients. For information on JMX infrastructure and configuring the broker's JMX support, see Appendix D, JMX Support, in Oracle GlassFish Server Message Queue 4.5 Administration Guide.