WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with the WebSphere MQ messaging provider > Configure JMS resources for the WebSphere MQ messaging providerConfigure a queue connection factory for the WebSphere MQ messaging provider
Overview
Configure queue connection factories for point-to-point messaging with a WebSphere MQ messaging provider.
With JMS 1.1, domain-independent connection factories are preferred to domain-specific queue and topic connection factories.
Procedure
- In the navigation pane, click Resources > JMS->Queue connection factories. A list of existing queue connection factories, with a summary of their properties, is displayed.
- Select the Scope setting corresponding to the scope at which the queue connection factory is visible to applications.
- Click the name of the queue connection factory to view or change.
- Under General Properties make any required changes.
For information about each of the available fields, see WebSphere MQ messaging provider queue connection factory settings.
- Click Apply to save the configuration.
- Optional: Click Advanced properties to display or change the list of advanced properties of your queue connection factory.
- Optional: Click Custom properties to display or change the list of custom properties of your queue connection factory.
- Optional: Click Client transport properties to display or change the list of client transport properties of your queue connection factory. This link is only appears if, when we created the connection factory, you chose to enter all the information required to connect to WebSphere MQ. This link does not appear if we have chosen to use a client channel definition table (CCDT) to establish a connection to WebSphere MQ.
- Optional: Click Connection pools to display or change the connection pools detail of your queue connection factory.
- Optional: Click Session pools to display or change the session pools detail of your queue connection factory.
There is a mechanism (session.sharing.scope custom property) to make JMS sessions unshareable. This means that whenever an application calls Session.close(), the JMS session is automatically released from any transaction associated with and returned to the session pool. This means that sessions can be cleaned up and removed from the session pool even if the servlet or asynchronous bean that created it is still running.
- Click OK.
- Save your changes to the master configuration.
- To have the changed configuration take effect, stop then restart the application server.
Related concepts:
Message processing in ASF mode and non-ASF mode
Related
Create a connection factory for the WebSphere MQ messaging provider
Configure a unified connection factory for the WebSphere MQ messaging provider
Configure custom properties for WebSphere MQ messaging provider JMS resources
Reference:
createWMQConnectionFactory command
deleteWMQConnectionFactory command
listWMQConnectionFactories command
modifyWMQConnectionFactory command
showWMQConnectionFactory command
WebSphere MQ messaging provider queue connection factory settings
WebSphere MQ messaging provider queue connection factory advanced properties
WebSphere MQ messaging provider connection factory client transport settings
Connection pool properties
Session pool settings