WebSphere MQ messaging provider queue connection factory settings


 

+

Search Tips   |   Advanced Search

 

Overview

A WebSphere MQ queue connection factory (QCF) creates JMS connections to queues provided by WebSphere MQ for point-to-point messaging. To set the QCF configuration properties...

Resources | JMS | Queue connection factories | Scope | Queue Connection Factory

QCF properties include...

Using the MQ administrative command, createWMQConnectionFactory, we can set additional properties...

Names can have a maximum of 48 characters, with the exception of channels, which have a maximum of 20 characters.


Connection properties

Group Description
CCDT connection A WebSphere MQ administrator can create a single Client Channel Definition Table (CCDT) of all the MQ channels supported by queue managers in their enterprise. Additional MQ configuration information can be associated with the entries in a CCDT. If the connection factory was created using a CCDT, only the following information is required to configure a connection:

CCDT URL Location of the CCDT.
Queue manager CCDT entry, or entries, to use.
SSL configuration Secure network communications with the MQ queue manager or queue-sharing group.

Explicitly-defined connection If the connection factory was not created using a CCDT, to configure a connection...

  • Queue manager
  • Transport
  • Host name
  • Port
  • Server connection channel

If we clear the check box for...

Use SSL to secure communication with Websphere MQ

...the following properties cannot be used...


WebSphere MQ Queue Connection Factory properties

Scope 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 defined at more general scopes. The scope displayed is for information only, and cannot be changed on this panel. To browse or change this resource (or other resources) at a different scope, change the scope on the MQ QCF collection panel, then click Apply, before clicking the link for the type of resource.
Provider The JMS provider assigned when the QCF is created. For all QCFs created using this panel, the provider is the MQ messaging provider. The provider is displayed for information only.
Name Unique name by which this QCF is known for admin purposes within WAS.
JNDI name Used to bind the QCF into the namespace. For example...

jms/ResourceName
Description A description of this QCF for administrative purposes within WAS.
Client channel definition table URL A URL that points to an MQ CCDT.
Queue manager If this QCF is based on a CCDT, this property is used to select an entry in the CCDT. Otherwise, it is the name of the queue manager or queue-sharing group to connect to. A connection is established to this MQ resource to send or receive messages.

The value must be one of the following:

  • Valid queue manager name
  • Valid queue manager name with the last character an asterisk
  • Asterisk
  • Blank

If this connection factory is not based on a CCDT, the value must be a valid queue manager name.

Transport The MQ transport type for the connection...

client Use a TCP/IP-based network connection to communicate with the MQ queue manager.
bindings then client Default. Attempt a bindings mode connection to the queue manager. If this is not possible, revert to the client transport.
bindings Establish a cross-memory connection to a queue manager running on the same node. The following Client Transport Mode properties are disabled:

  • Hostname
  • Port
  • Server connection channel

Hostname The host name, IPv4, or IPv6 address of the MQ queue manager to connect to.
Port Port number on which MQ is listening. Default is 1414. Range is 1 to 65536 (inclusive).
Server connection channel The MQ server connection channel name used when connecting to MQ.

Default: SYSTEM.DEF.SVRCONN

The value must be a server connection channel defined to the MQ queue manager that is being connected to.

Use SSL to secure communications with WebSphere MQ Secure network communications to the MQ queue manager or queue-sharing group.

When using an MQ messaging provider QCF in the appserver environment, the appserver manages SSL configuration. To set...

Security | SSL certificate and key management

MQ QCFs in the client environment get SSL configuration information from ssl.client.props.

If more than one cipher suite is specified, only the first one is used.

If check box is cleared, the following SSL properties are disabled:

Centrally managed Host name and port attributes from the MQ messaging provider QCF are used to select a centrally managed SSL configuration.
Specific configuration Specify a particular SSL configuration for securing network communications with the MQ queue manager or queue-sharing group.
SSL configuration From the drop-down list, select the SSL configuration to use. Disabled if "Centrally managed" radio button is selected and the MQ messaging provider resource has been explicitly defined. Enabled if the MQ messaging provider resource is based on a CCDT and the relevant entries in the CCDT have been configured to use SSL. If none is selected, the default "Centrally managed" WAS SSL configuration for the MQ messaging provider is used.
Component-managed authentication alias User name and password to use when connecting to the MQ messaging provider. Range is all authentication aliases defined to the cell. The value "(none)" specifies that no credentials are passed to MQ.
Client identifier Client identifier to specify when connecting to MQ messaging provider.
Provider version MQ messaging provider version.

Used to determine whether to connect to a particular version of a queue manager and type of functionality required by the client.

If this QCF factory is used to connect to a queue manager or queue-sharing group on an MQ for z/OS system, enter the value 6.0.0.0 in the Provider version property, regardless of the version of MQ for z/OS to which it connects.

The value entered must be either the empty string or be must be in one of the following formats:

  • n.n.n.n
  • n.n.n
  • n.n
  • n

For example: 6.0.0.0

Support distributed two-phase commit protocol Specify whether the connection factory supports XA coordination of messaging transactions. Enable if multiple resources, including this connection factory, are to be used in the same transaction.

If cleared, support for distributed two-phase commit protocol is disabled. The JMS session can still be enlisted in a transaction, but it uses the resource manager local transaction calls...

  • session.commit
  • session.rollback

...instead of XA calls, which can lead to an improvement in performance. However, only a single resource can be enlisted in a transaction in WAS.

Last participant support enables you to enlist one non-XA resource with other XA-capable resources.

Default: Selected

Keep selected if transactions involve other resources, including other queues or topics. Clear only when certain the queue manager connected to this QCF is the only resource in the transaction.

Authentication alias for XA recovery User name and password to use when connecting to MQ during XA recovery. Range is all authentication aliases defined to the cell. The value "(none)" specifies that no credentials are passed to MQ during XA recovery.
Mapping-configuration alias 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 connection factory...

Related items | JAAS - J2C authentication data

Range...

Container-managed authentication alias The authentication alias which specifies the user name and password to use when connecting to the MQ messaging provider. Range is all authentication aliases defined to the cell and the value. The value "(none)" specifies that no credentials are passed to MQ.




Subtopics

MQ messaging provider QCF advanced properties

 

Related tasks

 

Related

Manage Java 2 Connector Architecture authentication data entries
Secure messaging
Set the MQ messaging provider with native libraries information
Sizing the thread pools used by the MQ messaging provider
Set a QCF for the MQ messaging provider
Queue connection factory collection
WebSphere MQ messaging provider
ssl.client.props client configuration file
Dynamic outbound endpoint SSL configuration settings
MQ resource custom properties settings
Map of admin console panel names to command names and MQ names
MQ messaging provider connection factory client transport settings
Connection pool settings
Session pool settings
JMS interfaces - explicit polling for messages
MQ library
MQ library Web page