Use this panel to view or change the configuration properties of the selected queue connection factory for use with the WebSphere® MQ messaging provider. These configuration properties control how connections are created to associated JMS queue destinations.
A WebSphere MQ queue connection factory is used to create JMS connections to queues provided by WebSphere MQ for point-to-point messaging.
Make any required changes to the Administration, Connection, Advanced, and Security settings groups of properties, and then click Apply to save the configuration before, in the content pane under Additional Properties, you select any of the following links:
Under Related Items, you can click JAAS - J2C authentication data to configure authentication information for use with the queue connection factory.
A WebSphere MQ queue connection factory has the following properties.
The level at which this resource definition is visible to applications.
Resources such as messaging providers, namespace bindings, or shared libraries can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates that are defined at more general scopes.
The scope displayed is for information only, and cannot be changed on this panel. If you want to browse or change this resource (or other resources) at a different scope, change the scope on the WebSphere MQ queue connection factory collection panel, then click Apply, before clicking the link for the type of resource.
Data type | String |
The JMS provider assigned when the queue connection factory is created.
For all queue connection factories created using this panel, the provider is the WebSphere MQ messaging provider.
The provider is displayed for information only.
Data type | String |
The name by which this queue connection factory is known for administrative purposes within WebSphere Application Server.
Data type | String |
Range | The name must be unique within the set of queue connection factories defined to the cell. |
The JNDI name that is used to bind the queue connection factory into the namespace.
As a convention, use the fully qualified JNDI name; for example, in the form jms/Name, where Name is the logical name of the resource.
Data type | String |
A description of this queue connection factory for administrative purposes within WebSphere Application Server.
Data type | String |
Default | Null |
The information required to configure a connection depends on whether the selected queue connection factory was created using a Client Channel Definition Table (CCDT).
For more information about setting the SSL properties for WebSphere MQ, see SSL properties in the Using Java section of the WebSphere MQ information center.
A URL that specifies the location of a WebSphere MQ CCDT.
Data type | String |
If the specified queue connection factory is based on a CCDT, this property is used to select an entry in the CCDT. Otherwise, this property specifies the name of the queue manager or queue-sharing group to connect to. A connection is established to the specified WebSphere MQ resource to send or receive messages.
Data type | String |
Range | If this queue connection factory is not
based on a CCDT, the value must be a valid queue manager name. If
this queue connection factory is based on a CCDT, the value must be
one of the following:
If
the specified connection factory is based on a CCDT, and the CCDT
can select from more than one queue manager, you might not be able
to recover global transactions. Therefore, for connection factories
that specify a CCDT, you have two alternatives:
|
The WebSphere MQ transport type for the connection. The transport type is used to determine the exact mechanisms used to connect to WebSphere MQ.
Data type | Drop-down list |
Default | Bindings, then client |
Range |
The information about sizing the thread pools used by the WebSphere MQ messaging provider is not relevant for Fix Pack 5 or later since the WMQCommonServices thread pool is no longer used. |
The host name, IPv4, or IPv6 address of the WebSphere MQ queue manager to connect to.
Data type | String |
The port number on which WebSphere MQ is listening.
Data type | Integer |
Default | 1414 |
Range | The value must be in the range 1 to 65536 (inclusive). |
The WebSphere MQ server connection channel name used when connecting to WebSphere MQ.
Data type | String |
Default | SYSTEM.DEF.SVRCONN |
Range | The value must be a server connection channel defined to the WebSphere MQ queue manager that is being connected to. |
This option determines whether the SSL (Secure Sockets Layer) protocol is used to secure network communications with the WebSphere MQ queue manager or queue-sharing group.
When using a WebSphere MQ messaging provider queue connection factory in the application server environment, the application server manages SSL configuration. To change SSL configuration parameters, use the administrative console to navigate to the
panel.When using a WebSphere MQ messaging provider queue connection factory in the client environment, the client takes SSL configuration information from the ssl.client.props file. Use of this file is detailed in the related reference information for this topic.
You can only use one cipher suite in the SSL configuration for a WebSphere MQ messaging provider queue connection factory. If you specify more than one cipher suite, only the first one is used.
Data type | Check box. If this check box is cleared, the following SSL
properties are disabled:
|
When the SSL protocol is used to communicate with WebSphere MQ, select this radio button to specify that the SSL configuration is taken from the centrally managed WebSphere Application Server SSL configuration.
When you select this radio button, the host name and port attributes from the WebSphere MQ messaging provider queue connection factory are used to select an appropriate SSL configuration. To provide the SSL configuration that will be matched to the queue connection factory, see the Dynamic outbound endpoint SSL configuration settings topic listed under related reference.
Data type | Radio button |
Select this radio button when you want to specify a particular SSL configuration for use when SSL is to be used to secure network communications with the WebSphere MQ queue manager or queue-sharing group.
Data type | Radio button |
The SSL configuration to use when SSL is to be used to secure network communications with the WebSphere queue manager or queue-sharing group.
This property is disabled if the Centrally managed radio button is selected and the WebSphere MQ messaging provider resource has been explicitly defined.
This property is always enabled if the WebSphere MQ messaging provider resource is based on a CCDT.
If this WebSphere MQ messaging provider resource is based on a CCDT, this parameter is only used if the relevant entries in the CCDT have been configured to use SSL.
Additionally, if an SSL configuration of none is selected, the default centrally managed WebSphere Application Server SSL configuration for the WebSphere MQ messaging provider is used.
Data type | Drop-down list |
The client identifier to specify when connecting to the WebSphere MQ messaging provider.
Data type | String |
The WebSphere MQ messaging provider version. This is used to determine whether to connect to a particular version of a queue manager. It is also used to determine the type of functions required by the client.
For Fix Pack 5 or later, if this connection factory is used to connect to a queue manager or queue-sharing group on a WebSphere MQ for z/OS Version 7 system, enter the value 6.0.0.0 in the Provider version property.
For Fix Pack 7 or later, the restriction on the provider version is lifted.
Data type | String |
Range | The value entered must either be the empty string or be in
one of the following formats:
For example 6.0.0.0. |
An option that specifies whether the queue connection factory supports XA coordination of messaging transactions. Enable this option if multiple resources, including this queue connection factory, are to be used in the same transaction.
If you clear this property, you disable support for distributed two-phase commit protocol. The JMS session can still be enlisted in a transaction, but it uses the resource manager local transaction calls session.commit and session.rollback, instead of XA calls. This can lead to an improvement in performance. However, only a single resource can be enlisted in a transaction in WebSphere Application Server.
Last participant support enables you to enlist one non-XA resource with other XA-capable resources.
Data type | Check box |
Default | Selected |
Range |
|
Keep this option selected if transactions involve other resources, including other queues or topics. Clear this option only when you are certain that the queue manager that is the target for this queue connection factory is the only resource in the transaction.
The user name and password to use when connecting to WebSphere MQ during XA recovery.
Data type | Drop-down list |
Default | (none) |
Range | All authentication aliases defined to the cell and the value "(none)", which specifies that no credentials are passed to WebSphere MQ during XA recovery. |
This field is used only in the absence of a login configuration on the component resource reference.
When the resource authority value is "container", the preferred way to define the authentication strategy is by specifying a login configuration and associated properties on the component resource reference.
If the DefaultPrincipalMapping login configuration is specified, the associated property will be a JAAS - J2C authentication data entry alias. To configure authentication information for use with the queue connection factory, under Related Items, click JAAS - J2C authentication data .
Data type | Drop-down list |
Default | (none) |
Range |
|
The authentication alias which specifies the user name and password to use when connecting to the WebSphere MQ messaging provider.
Data type | Drop-down list |
Default | (none) |
Range | All authentication aliases defined to the cell and the value "(none)", which specifies that no credentials are passed to WebSphere MQ. |