+

Search Tips   |   Advanced Search

Disable IBM MQ functionality in WAS

If we do not need to use IBM MQ functionality in an application server we can disable it using either the administrative console or an administrative command. We can also disable IBM MQ functionality in a client process by specifying a custom property.

When a WebSphere Application Server process or an application client process starts, and while this process is running, an amount of processing is performed to allow it to support IBM MQ-related functionality such as the IBM MQ messaging provider. By default this processing is performed regardless of whether any IBM MQ-related functionality is ever used. If we do not need to take advantage of any IBM MQ functionality, it is possible to disable all IBM MQ functionality in an application server or client process to give increased performance.

Disable IBM MQ functionality in a WAS process has the following effects:

Disable IBM MQ functionality in a WAS client process has the following effects:


Tasks


Example

Consider the following example: A network deployment configuration with two nodes: node1 and node2. Node1 has two servers on it, server1 and server2. Node2 has a single server on it, server3. Server3 and server1 are part of a cluster, cluster1. The IBM MQ messaging provider panel at cluster1 scope has the IBM MQ disabled check box selected and the changes saved. When cluster1 has been restarted, all IBM MQ functionality is disabled on server3 and server1.

It is worth noting that it is possible to have IBM MQ functionality disabled on all processes in a network deployment configuration without all scopes having IBM MQ functionality disabled. Using the scenario in the previous example, if all nodes in the topology (deployment manager node, node1 and node2) have IBM MQ functionality disabled, then all the processes in the topology also have IBM MQ functionality disabled.


What to do next

When the server starts, it is possible to detect whether IBM MQ functionality has been disabled on that server because messages with the following IDs are output:

  • IBM MQ messaging provider
  • Configure custom properties for the IBM MQ resource adapter
  • JMS provider settings
  • IBM MQ servers [Collection]
  • IBM MQ server [Settings]
  • IBM MQ client links [Collection]
  • Foreign bus connections [Collection]
  • IBM MQ links [Collection]