My Services WebSphere Training | JEE Build & Deploy | Automatic Linux Provisioning
A new feature of WebSphere 8 is that If you do not need to use WebSphere MQ (WMQ) 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. Procedure to disable MQ Administrative Console Using the administrative console, select the Disable WebSphere MQ check box on the required WebSphere MQ messaging provider panel. For more information, see JMS provider settings. Example using admin console On a stand-alone WAS 8 server you can only disable at a server scope. click the WebSphere MQ messaging provider and on the JMS providers/WebSphere MQ messaging provider screen check the Disable Websphere MQ check-box as shown in the image below. manageWMQ command Use the manageWMQ administrative command with the disableWMQ flag. For more information, see manageWMQ command. Note: In a single server environment, you can only disable WebSphere MQ at the server scope. When you have saved your changes and restarted the application server, all WebSphere MQ functionality is disabled on that server. In a network deployment environment, you can disable WebSphere MQ at all scopes in order to give fine grained configuration flexibility: - At the cell scope, all WebSphere MQ functionality is disabled on all application servers in the cell. - At the node scope, all WebSphere MQ functionality is disabled on all application servers that are part of that node. - At the cluster scope, all WebSphere MQ functionality is disabled on all application servers in that cluster. - At the server scope, all WebSphere MQ functionality is disabled in that particular application server. The value of the Disable WebSphere MQ check box at a higher scope takes precedence over the value at a lower scope. For example, if you do not select the check box at the server scope but do select it for a higher (for example, cell) scoped WebSphere MQ messaging provider, the value at the cell scope takes precedence and WebSphere MQ functionality is therefore disabled in all application servers in the cell, regardless of whether the check box is selected at the server scope. The changes take effect when you have saved them and restarted all affected processes in the cell. Example using wsadmin interactively: wsadmin>AdminTask.help('manageWMQ') 'WASX8006I: Detailed help for command: manageWMQ\n\nDescription: Provides the ability to manage the settings associated with the WMQ resource adapter installed at a particular scope.\n\n*Target object: The WMQ resource adapter to manage\n\nArguments:\n nativePath - Specifies the path to the WMQ messaging provider native libraries to be used if the WMQ resource adapter is to establish a bindings mode connection to the queue manager.\n query - Provides information about the WMQ messaging provider. This can be the WMQ resource adapter installed into WAS, or a WMQ resource adapter present on the filesystem of the node.\n enableInbound - Enables inbound JCA message delivery for the z/OS platform.\n disableWMQ - Disables all WebSphere MQ functionality on servers at the specified scope and lower. In a single server environment this disables WebSphere MQ functionality on the entire server.\n\nSteps:\n None\n\n' wsadmin>print AdminTask.help('manageWMQ') WASX8006I: Detailed help for command: manageWMQ Description: Provides the ability to manage the settings associated with the WMQ resource adapter installed at a particular scope. *Target object: The WMQ resource adapter to manage Arguments: nativePath - Specifies the path to the WMQ messaging provider native libraries to be used if the WMQ resource adapter is to establish a bindings mode connection to the queue manager. query - Provides information about the WMQ messaging provider. This can be the WMQ resource adapter installed into WAS, or a WMQ resource adapter present on the filesystem of the node. enableInbound - Enables inbound JCA message delivery for the z/OS platform. disableWMQ - Disables all WebSphere MQ functionality on servers at the specified scope and lower. In a single server environment this disables WebSphere MQ functionality on the entire server. Steps: None MQ Java Client To disable WebSphere MQ functionality in a WebSphere Application Server client process, specify the custom property com.ibm.ejs.jms.disableWMQSupport=true. Result of disabling WMQ functionality
Steve Robinson has been working in IT for over 15 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware consulting. Steve comes from both an administration and development background.
Before moving to JEE, Steve was an accomplished developer and consultant for both IBM Lotus Notes and Microsoft .NET Technologies.
Follow Steve as @stevencrobinson on twitter.
IBM WebSphere Application Server 8.0 Administration Guide
WebSphere Application Server 7.0 Administration Guide