Command Line Utilities

All Message Queue utilities are accessible via a command line interface. Utility commands share common formats, syntax conventions, and options. These utilities allow you to perform various administrative tasks, as noted below, and therefore can require different administrative permissions:

• The Broker utility (imqbrokerd) starts up brokers and specifies their configuration properties, including connecting them together into a cluster. Permissions: User account that initially started the broker.

• The Command utility (imqcmd) controls brokers and their resources and manages physical destinations. Permissions: Message Queue admin user account.

• The Object Manager utility (imqobjmgr) manages provider-independent administered objects in an object store accessible via the Java Naming and Directory Interface (JNDI). Permissions: Object store (flat-file or LDAP server) access account.

• The Database Manager utility (imqdbmgr) creates and manages databases for persistent storage that conform to the Java Database Connectivity (JDBC) standard. Permissions: JDBC database manager account.

• The User Manager utility (imqusermgr) populates a file-based user repository for user authentication and authorization. Permissions: user account that initially started the broker.

• The Service Administrator utility ( imqsvcadmin) installs and manages a broker as a Windows service. Permissions: Administrator.

• The Key Tool utility (imqkeytool) generates self-signed certificates for Secure Socket Layer (SSL) authentication. Permissions: root user (Solaris and Linux platforms) or Administrator (Windows platform).

The executable files for the above command line utilities are in the /bin directory shown in Appendix A, Platform-Specific Locations of Message Queue Data.

See Chapter 15, Command Line Reference for detailed information on the use of these utilities.