Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the WebSphere MQ messaging provider


Disable WebSphere MQ functionality in WAS

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

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

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

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


Procedure


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 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 (dmgr node, node1 and node2) have WebSphere MQ functionality disabled, then all the processes in the topology also have WebSphere MQ functionality disabled.


What to do next

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


Manage messaging with the WebSphere MQ messaging provider
Configure custom properties for the WebSphere MQ resource adapter


Related


JMS provider settings
WebSphere MQ servers [Collection]
WebSphere MQ server [Settings]
WebSphere MQ client links [Collection]
Foreign bus connections [Collection]
WebSphere MQ links [Collection]
SIBMQLinkSenderChannel_CollectionForm
SIBMQLinkReceiverChannel_CollectionForm

+

Search Tips   |   Advanced Search