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

Document Information


Part I Introduction to Message Queue Administration

1.  Administrative Tasks and Tools

2.  Quick-Start Tutorial

Part II Administrative Tasks

3.  Starting Brokers and Clients

4.  Configuring a Broker

5.  Managing a Broker

6.  Configuring and Managing Connection Services

7.  Managing Message Delivery

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

13.  Monitoring Broker Operations

14.  Analyzing and Tuning a Message Service

15.  Troubleshooting

Part III Reference

16.  Command Line Reference

Command Line Syntax

Broker Utility

Command Utility

General Command Utility Options

Broker Management

Connection Service Management

Connection Management

Physical Destination Management

Durable Subscription Management

Transaction Management

JMX Management

Object Manager Utility

Database Manager Utility

User Manager Utility

Bridge Manager Utility

Service Administrator Utility

Key Tool Utility

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

Part IV Appendixes

A.  Distribution-Specific Locations of Message Queue Data

B.  Stability of Message Queue Interfaces

C.  HTTP/HTTPS Support

D.  JMX Support

E.  Frequently Used Command Utility Commands


Database Manager Utility

The Database Manager utility (imqdbmgr) sets up the database schema for a JDBC-based data store. You can also use it to delete Message Queue database tables that have become corrupted, change the database, display information about the database, convert a standalone database for use in an enhanced broker cluster, or back up and restore a highly-available database. Table 16-13 lists the imqdbmgr subcommands.

Note - When using a cluster configuration file to simplify management of the properties for a cluster of brokers, make sure to run imqdbmgr with the -D option to specify the location of the cluster configuration file; for example:

imqdbmgr -Dimq.cluster.url=location-of-cluster-configuration-file ...

Table 16-13 Database Manager Subcommands

create all
Create new database and persistent data store schema

Used on embedded database systems. The broker property imq.persist.jdbc.vendorName.createdburl must be specified.

create tbl
Create persistent data store schema for existing database

Used on external database systems.

For brokers belonging to an enhanced broker cluster (imq.cluster.ha = true), the schema created is for the cluster’s shared data store, in accordance with the database vendor identified by the broker’s imq.persist.jdbc.dbVendor property. If imq.cluster.ha = false, the schema is for the individual broker’s standalone data store. Since the two types of data store can coexist in the same database, they are distinguished by appending a suffix to all table names:

  • C clusterID: Shared data store

  • S brokerID: Standalone data store

delete tbl
Delete Message Queue database tables from current data store
delete oldtbl
Delete Message Queue database tables from earlier-version data store

Used after the data store has been automatically migrated to the current version of Message Queue.

recreate tbl
Re-create persistent store schema

Deletes all existing Message Queue database tables from the current persistent store and then re-creates the schema.

Display information about the data store
upgrade hastore
Upgrade standalone data store to shared data store
Back up JDBC-based data store to backup files
Restore JDBC-based data store from backup files
remove bkr
Remove broker from shared data store

The broker must not be running.

remove jmsbridge
Remove JMS bridge from the shared data store

The broker hosting the JMS bridge must not be running.

reset lck
Reset data store lock

Resets the lock so that the database can be used by other processes.

Subcommands for a Cluster's Shared Configuration Change Table
create sharecc_tbl
Create the shared database table for the cluster configuration change record
delete sharecc_tbl
Delete the shared database table for the cluster configuration change record
recreate sharecc_tbl
Re-create the shared database table for the cluster configuration change record.

Deletes existing shared database table and then re-creates it.

backup sharecc_tbl -file filePath
Back up the shared database table for the cluster configuration change record to a backup file
restore sharecc_tbl -file filePath
Restore the shared database table for the cluster configuration change record from a backup file. The table must already exist.

Table 16-14 lists the options to the imqdbmgr command.

Table 16-14 Database Manager Options

-b instanceName
Instance name of broker
Set broker configuration property

See Persistence Properties for information about persistence-related broker configuration properties.

Caution: Be careful to check the spelling and formatting of properties set with this option. Incorrect values will be ignored without notification or warning.

-u userName
User name for authentication against the database
-passfile filePath
Location of password file

See Password Files for more information.

-n brokerID
(Used with the remove bkr subcommand) Broker identifier of broker to be removed from shared data store
-n bridgeName
(Used with the remove jmsbridge subcommand) Bridge name of the JMS bridge to be removed from shared data store
-dir dirPath
Backup directory for backing up or restoring JDBC-based data store
Display version information1
Display usage help1

1Any other options specified on the command line are ignored.