Configuring 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 use with the WebSphere® MQ messaging provider on a WebSphere Application Server Version 6 node. This task contains an optional step for you to create a new domain-independent connection factory.

About this task

With JMS 1.1, domain-independent (unified) connection factories are preferred to domain-specific queue connection factories and topic connection factories. If you want to view or change the configuration of a queue 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 administrative console to complete the following steps:

Procedure

  1. In the navigation pane, click Resources > JMS ->JMS providers.
  2. Select the WebSphere MQ messaging provider that you want to support the destination.
  3. Optional: Change the Scope setting to the level at which the connection factory is visible to applications.
  4. In the contents pane, under Additional Properties, click Connection factories to display a table of existing unified connection factories, with a summary of their properties.
  5. To view or change the properties of an existing unified connection factory, click its name in the list. Otherwise, to create a new connection factory, complete the following steps:
    1. Click New in the content pane.
    2. Specify the following required properties.
      Name
      The name by which this connection factory is known for administrative purposes within IBM® WebSphere Application Server.
      JNDI name
      The JNDI name that is used to bind the connection factory into the namespace.
      CCSID
      The coded character set identifier for use with the WebSphere MQ queue manager; for example: 850. See the properties for the unified JMS connection factory for more details.
    3. Click Apply. This defines the JMS connection factory to WebSphere Application Server, and enables you to view or change additional properties.
  6. Optional: Change properties for the unified JMS connection factory, according to your needs.
  7. Optional: Change connection pool properties and session pool properties, according to your needs.

    APAR PK59605 provides 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.

  8. Configure a non-default SSL repertoire. To do this, specify a custom property on the connection factory with name ssl.repertoire and a value of the name of the repertoire alias to be used. A list of available repertoire aliases can be found by navigating to Security > SSL certificate and key management > SSL configurations. For WebSphere MQ the only settings in the SSL configuration that are used are:
    • Location of the Trust store and its password
    • Location of the Key store and its password
    Information about supported SSL cipher suites is ignored by the WebSphere MQ client.
  9. Click OK.
  10. Save any changes to the master configuration.
  11. To have the changed configuration take effect, stop then restart the application server.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 4:28:44 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-mp&topic=tmj_adm630
File name: tmj_adm630.html