Disabling WebSphere MQ

A new feature available to WebSphere 8 is the ability to disable the internal WebSphere MQ messaging provider. Disabling WMQ, when it is not required, improves WAS performance. In the previous section, we demonstrated how an application deployed in WebSphere can use JNDI to communicate with a WMQ queue which exists on an external WMQ queue manager. If your applications have no need for WMQ, then you can disable the loading of WebSphere MQ. Disabling WMQ improves server startup time and saves on JVM memory utilization. There are three ways in which WMQ can be disabled.

• Through the Administrative console

  • In a standalone install, WMQ can be disabled at server scope. For WebSphere ND, WMQ can be disabled at different scopes; for example, Cell, Node, cluster, and Server scope.

• The manageWMQ wsadmin command

  • Use the manageWMQ administrative command with the disableWMQ flag. This command is useful for scripted Jython configurations.

• MQ Java client

  • By using com.ibm.ejs.jms.disableWMQSupport...