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

The administration tools include the following command line interfaces:

• Broker utility (imqbrokerd). Used to start a broker. You can use options to the imqbrokerd command to specify whether brokers should be connected in a broker cluster and to specify additional startup configuration information.

• Command utility (imqcmd). Used after starting a broker to manage broker resources, such as connection services, connections, durable subscriptions, transactions, physical destinations, and so forth.

• Object Manager utility (imqobjmgr). Used to create, list, update, and delete administered objects in a JNDI object store.

• User Manager utility (imqusermgr). Used to populate a file-based user repository for user authentication and authorization.

• Database Manager utility (imqdbmgr). Used to create and manage a JDBC-based persistent data store. (The built-in file store requires no external management.)

• Key Tool utility (imqkeytool). Used to generate self-signed broker certificates needed for SSL authentication.

• Service Administrator utility (imqsvcadmin). Used to install, query, and remove a broker as a Windows service.

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:

• Manage a broker, its connection services, and other resources.

• Create, update, and delete physical destinations.

• Connect to a JNDI object store, add administered objects to the store, and manage them.