Use this task to view or change the configuration of an
existing domain-independent connection factory for the IBM MQ messaging provider on a
WebSphere® Application Server node.
About this task
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. If you want 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 IBM MQ messaging
provider, use the administrative console to complete the following
steps.
Procedure
- In the navigation pane, click .
A list of existing unified connection factories, with
a summary of their properties, is displayed.
- Select the Scope corresponding to
the scope at which the connection factory is visible to applications.
- Click the name of the connection factory that you want
to view or change.
Configuration details for the
unified 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 connection
factory.
- Optional: Click Broker properties to
display or change the list of broker properties of your connection
factory.
- Optional: Click Custom properties to
display or change the list of custom properties of your connection
factory.
- Optional: Click Client transport
properties to display or change the list of client transport
properties of your 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 IBM MQ. This link does not appear
if you have chosen to use a client channel definition table (CCDT)
to establish a connection to IBM MQ.
- Optional: Click Connection pools to
display or change the connection pools detail of your connection factory.
- Optional: Click Session pools to
display or change the session pools detail of your 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 make the changed configuration take effect, stop then
restart the application server.