+

Search Tips   |   Advanced Search

Configure a unified connection factory for the WebSphere MQ messaging provider

Use this task to view or change the configuration of an existing domain-independent connection factory for the WebSphere MQ messaging provider on a WAS node.

This task applies to unified connection factories. With JMS 1.1, domain-independent (unified) connection factories are preferred to domain-specific queue connection factories and topic connection factories. To view or change a queue connection factory or topic connection factory, see the related tasks.

To view or change the configuration of an existing connection factory for use with the WebSphere MQ messaging provider, use the console to complete the following steps.

  1. In the navigation pane, click Resources > JMS->Connection factories. A list of existing unified connection factories, with a summary of their properties, is displayed.

  2. Select the Scope corresponding to the scope at which the connection factory is visible to applications.

  3. Click the name of the connection factory to view or change. Configuration details for the unified connection factory are displayed.

  4. Under General Properties make any required changes.

    For information about each of the available fields, see WebSphere MQ messaging provider connection factory settings.

  5. Click Apply to save the configuration.

  6. Optional: Click Advanced properties to display or change the list of advanced properties of the connection factory.

  7. Optional: Click Broker properties to display or change the list of broker properties of the connection factory.

  8. Optional: Click Custom properties to display or change the list of custom properties of the connection factory.

  9. Optional: Click Client transport properties to display or change the list of client transport properties of the connection factory. This link is only appears if, when creating 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.

  10. Optional: Click Connection pools to display or change the connection pools detail of the connection factory.

  11. Optional: Click Session pools to display or change the session pools detail of the 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 that is 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.

  12. Click OK.

  13. Save the changes to the master configuration.

  14. To make the changed configuration take effect, stop then restart the application server.


Related concepts

  • Message processing in ASF mode and non-ASF mode


    Related tasks

  • Create a connection factory for the WebSphere MQ messaging provider
  • Configure a queue connection factory for the WebSphere MQ messaging provider
  • Configure a topic connection factory for the WebSphere MQ messaging provider
  • Configure custom properties for WebSphere MQ messaging provider JMS resources

  • createWMQConnectionFactory command
  • deleteWMQConnectionFactory command
  • listWMQConnectionFactories command
  • modifyWMQConnectionFactory command
  • showWMQConnectionFactory command
  • WebSphere MQ messaging provider connection factory settings
  • WebSphere MQ messaging provider connection factory advanced properties
  • WebSphere MQ messaging provider connection factory broker properties
  • WebSphere MQ messaging provider connection factory client transport settings
  • Connection pool properties
  • Session pool settings