New install for WebSphere MQ v7.1 and/or v7.5 creates two Windows service entries

Technote (troubleshooting)


Problem(Abstract)

After installing WebSphere MQ (WMQ) v7.1 or v7.5, you notice there are two Windows services for WMQ.

Cause

When you install WMQ v7.1 or v7.5, it will create two entries in the Windows services.

  • IBM MQSeries
  • IBM WebSphere MQ(Installation Name)

The service for IBM MQSeries should be set to Manual start (default). The service for IBM WebSphere MQ(Installation Name) should be set to autostart (default).

The IBM MQSeries service is created for legacy purposes. This service is only used if WMQ v7.0.1.x is also installed. If you only have WMQ v7.1 or v7.5, you should never have to use the IBM MQSeries service.

However, if you are running WMQ Broker or other software which is dependent on the "IBM MQSeries", you will need to enable the service even if you are not running WMQ v7.0.x.

The service that you get for the primary installation only is called the old name 'IBM MQSeries' and is expected only ever to run under LocalSystem. It's only purpose in life is to start the real (MQ_<INSTALLATION_NAME>) service. Hence ending "IBM MQSeries" service will cause the associated primary installation's service to end. If broker is dependent on "IBM MQSeries" services.

Ending "IBM MQSeries" service will end both broker and queue manager. The "IBM MQSeries"
service is only there to support applications that depend on it, but if they depend on it, they expect it to operate like the original "IBM MQSeries" service would have.

Related information

A Japanese translation is available

Product Alias/Synonym

WMQ MQ

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere MQ
Configuration

Software version:

7.1, 7.5

Operating system(s):

Windows

Software edition:

All Editions

Reference #:

1615234

Modified date:

2014-11-10

Translate my page

Machine Translation

Content navigation