Skip Navigation Links | |
Exit Print View | |
Oracle GlassFish Server Message Queue 4.5 Administration Guide |
Part I Introduction to Message Queue Administration
1. Administrative Tasks and Tools
3. Starting Brokers and Clients
6. Configuring and Managing Connection Services
8. Configuring Persistence Services
9. Configuring and Managing Security Services
10. Configuring and Managing Broker Clusters
11. Managing Administered Objects
12. Configuring and Managing Bridge Services
Configuring and Managing JMS Bridge Services
Pooled, Shared, and Dedicated Connections
Transactional Message Transfer
JMS Bridges in High Availability (HA) Broker Clusters
Message Transformation During Message Delivery
Dead Message Queue (DMQ) Processing
Message Processing Sequence Across a Link in a JMS Bridge
Specifying the Broker Properties for a JMS Bridge
Creating the XML Configuration File for a JMS Bridge
Starting and Stopping JMS Bridges
To Configure a JMS Bridge to Start at Broker Startup
To Start a JMS Bridge Manually
Starting and Stopping Links in a JMS Bridge
Configuring and Managing STOMP Bridge Services
Starting and Stopping the STOMP Bridge
To Stop the STOMP Bridge Manually
To Start the STOMP Bridge Manually
Message Processing Sequence Across the STOMP Bridge
Message Transformation During Message Processing
STOMP Protocol Features and the STOMP Bridge
13. Monitoring Broker Operations
14. Analyzing and Tuning a Message Service
17. Broker Properties Reference
18. Physical Destination Property Reference
19. Administered Object Attribute Reference
20. JMS Resource Adapter Property Reference
21. Metrics Information Reference
22. JES Monitoring Framework Reference
A. Distribution-Specific Locations of Message Queue Data
B. Stability of Message Queue Interfaces
The Message Queue Bridge Service Manager is an application that runs in same JVM as a broker to manage the bridges configured for the broker. Two administrative components control operation of the Bridge Service Manager:
Bridge-related broker properties
The Bridge Manager utility (imqbridgermgr)
The following sections introduce these two components.
The operation of the Bridge Service Manager is in part controlled by several broker properties. These broker properties, all of which begin with imq.bridge, are listed in tables under Bridge Properties. Some of the properties apply to all bridges configured for the broker, while others apply only to a specific bridge. The properties that apply to a specific bridge all begin with imq.bridge.bridgeName, where bridgeName is:
The same as the type of the bridge for bridge services that support only one bridge instance per broker, such as the STOMP bridge service
A name you specify for a bridge instance for bridge services that support multiple bridge instances per broker, such as the JMS bridge service
Of all the bridge-related broker properties, the two most important are imq.bridge.enabled and imq.bridge.activelist:
The imq.bridge.enabled property controls whether the Bridge Service Manager is enabled on the broker.
The imq.bridge.activelist property contains a comma-separated list bridges (by name) to be loaded when the broker starts.
Alternatively, you can specify the password using the -passfile option when you use the imqbrokerd command to start the broker hosting the bridge service manager.
The Bridge Manager utility (imqbridgemgr) is the interface to the bridge management functions of the Bridge Service Manager. It provides commands to:
Stop and start bridges
Pause and resume bridges
List configured bridges
Manage type-dependent subcomponents of bridges, such as the links within a JMS bridge service
The imqbridgemgr utility uses the same command line syntax as the other Message Queue utilities:
imqbridgemgr subcommand commandArgument [ options ]
For example, the following command lists all bridges of type JMS on the broker localhost:7373:
imqbridgemgr list bridge -t jms -b localhost:7373
For the complete set of subcommands, command arguments, and options supported by the imqbridgemgr utility, see Bridge Manager Utility.
Each bridge managed by the Bridge Service Manager for a broker has its own log file stored in the IMQ_VARHOME/instances/broker-name/bridges/bridge-name/ directory.
The JMS and STOMP bridge services use the Java logging facility, which can be configured by the Java logging configuration file. The logging level for a bridge can be controlled by setting the imq.bridge.bridge-name.level property in the Java logging configuration file. Then, the Java system property java.util.logging.config.file can be set to the Java logging configuration file when the broker is started; as in:
imqbrokerd -Djava.util.logging.config.file=config-file