Use this task to view or change the configuration of an
existing JMS queue connection factory for use with WebSphere® MQ
as a messaging provider. This task contains an optional step for you
to create a new JMS queue connection factory.
About this task
With JMS 1.1, domain-independent (unified) connection
factories are preferred to domain-specific queue connection factory
and topic connection factory. To configure a unified connection factory,
see Configuring a unified connection factory for the WebSphere MQ messaging provider.
To
view or change the configuration of an existing queue connection factory
for use with the WebSphere MQ messaging provider, use the
administrative console to complete the following steps:
Procedure
- In the navigation pane, click .
- Select the WebSphere MQ
messaging provider for the queue connection factory that you want
to configure.
- Optional: Change the Scope setting
to the level at which the connection factory is visible to applications.
- In the contents pane, under Additional Properties, click Queue
connection factories to display a table of existing queue
connection factories, with a summary of their properties.
- To view or change the properties of an existing queue connection
factory, click its name in the list. Otherwise, to create a new connection
factory, complete the following steps:
- Click New in the content pane.
- 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 queue connection
factory for more details.
- Click Apply. This
defines the connection factory to WebSphere Application
Server, and enables you to view or change additional properties.
- Optional: Change properties for the queue connection factory,
according to your needs.
- 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.
- 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 . 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.
- Click OK.
- Save any changes to the master configuration.
- To have the changed configuration take effect, stop then
restart the application server.