Use this task to view or change the configuration of an
existing JMS queue connection factory for point-to-point messaging
with the WebSphere® MQ messaging provider.
About this task
This task applies to queue connection factories. With
JMS 1.1, domain-independent (unified) connection factories are preferred
to domain-specific queue connection factories and topic connection
factories. 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 .
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 that you
want to view or change.
Configuration details for
the queue connection factory are displayed.
- Under General Properties make any
required changes.
- 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 you created the connection factory, you chose to enter all
the information required to connect to WebSphere MQ. This link does not appear
if you 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 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.
- Click OK.
- Save your changes to the master configuration.
- To have the changed configuration take effect, stop then
restart the application server.