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


User Manager Utility

The User Manager utility (imqusermgr) is used for populating or editing a flat-file user repository. The utility must be run on the same host where the broker is installed; if a broker-specific user repository does not yet exist, you must first start up the corresponding broker instance in order to create it. You will also need the appropriate permissions to write to the repository: on the Solaris or Linux platforms, this means you must be either the root user or the user who originally created the broker instance.

Table 16-15 lists the subcommands available with the imqusermgr command. In all cases, the -i option specifies the instance name of the broker to whose user repository the command applies; if not specified, the default name imqbroker is assumed.

Table 16-15 User Manager Subcommands

add [-i instanceName]
  • -u userName -p password

  • [-g group]

Add user and password to repository

The optional -g option specifies a group to which to assign this user:

  • admin

  • user

  • anonymous

delete [-i instanceName]
  • -u userName

Delete user from repository
update [-i instanceName]
  • -u userName -p password

update [-i instanceName]

  • -u userName -a activeStatus

update [-i instanceName]

  • -u userName -p password

  • -a activeStatus

Set user’s password or active status (or both)

The -a option takes a boolean value specifying whether to make the user active (true) or inactive (false). An inactive status means that the user entry remains in the user repository, but the user will not be authenticated, even if using the correct password.

Default value: true.

list [-i instanceName]
  • [-u userName]

Display user information

If no user name is specified, all users in the repository are listed.

In addition, the options listed in Table 16-16 can be applied to any subcommand of the imqusermgr command.

Table 16-16 General User Manager Options

Specify a broker property value when starting imqusermgr.
Perform action without user confirmation
Silent mode (no output displayed)
Display version information1
Display usage help1

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