If you do not need to use WebSphere® MQ functionality in an application server you can disable it by using either the administrative console or an administrative command. You can also disable WebSphere MQ functionality in a client process by specifying a custom property.
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 WebSphere MQ messaging provider panel at cluster1 scope has the WebSphere MQ disabled check box selected and the changes saved. When cluster1 has been restarted, all WebSphere MQ functionality is disabled on server3 and server1.
It is worth noting that it is possible to have WebSphere MQ functionality disabled on all processes in a network deployment configuration without all scopes having WebSphere MQ functionality disabled. Using the scenario in the previous example, if all nodes in the topology (deployment manager node, node1 and node2) have WebSphere MQ functionality disabled, then all the processes in the topology also have WebSphere MQ functionality disabled.
In this information ...Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) |