What you can do with the WebSphere MQ Services snap-in

All the functions offered by the WebSphere MQ Services snap-in can be used to administer local or remote WebSphere MQ for Windows servers, except for the Alert monitor function, which records and notifies you of problems in your WebSphere MQ system. This function can be used on your local system only. See "Using the WebSphere MQ alert monitor application" for more information.

With the WebSphere MQ Services snap-in, you can:

• Start or stop a queue manager (on your local machine or on remote Windows systems).
• Start or stop the command servers, channel initiators, trigger monitors, and listeners.
• Create and delete command servers, channel initiators, trigger monitors, and listeners.
• Set any of the services to start up automatically during system startup.
• Set specific services to start up automatically when a queue manager is started.
• Modify some of the properties of queue managers. (Others are modified using WebSphere MQ Explorer.) This is the equivalent of the mqs.ini and qm.ini files used on WebSphere MQ for UNIX systems.
• Change the default queue manager.
• Manage secure sockets layer (SSL) certificates, associating certificates with queue managers and configuring and setting up certificate stores.
• Modify the parameters for any service, such as the TCP port number for a listener, or a channel initiator queue name.
• Modify the behavior of WebSphere MQ if a particular service fails. You could, for example, try to start the service a certain number of times.
• Start or stop the service trace.

The WebSphere MQ Services snap-in presents information in a style consistent with that of the Microsoft Management Console (MMC) and the other snap-in applications that the MMC supports.

You can also configure and control WebSphere MQ services using the amqmdain command. This command is described in amqmdain (WebSphere MQ services control).