WebSphere MQ messaging provider topic connection factory settings


 

+

Search Tips   |   Advanced Search

 

To set the configuration properties of the selected topic connection factory for use with the WebSphere MQ messaging provider. These configuration properties control how connections are created to the associated JMS topic destination.

A WebSphere MQ topic connection factory is used to create JMS connections to topic destinations provided by WebSphere MQ for publish/subscribe messaging.

To view WebSphere MQ topic connection factory settings, use the admin console to complete the following steps:

  1. In the navigation pane, click...

    Resources | JMS | Topic connection factories

  2. Set the Scope

  3. Select the name of the topic connection factory that you want to work with.

Under General Properties there are three groups of properties:

There are two variations of the Connection group:

CCDT Connection settings group

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

Client channel definition table URL Location of the CCDT.
Queue manager The queue manager name that specifies the CCDT entry, or entries, to use.
SSL configuration The SSL configuration to use when SSL is used to secure network communications with the WebSphere MQ queue manager or queue-sharing group.

Make any required changes to the Administration, Connection, and Advanced groups of properties, and then click Apply to save the configuration before, in the content pane under Additional Properties, you click any of the following links:

Advanced properties advanced properties of the WebSphere MQ topic connection factory.
Broker properties broker properties of the WebSphere MQ topic connection factory.
Custom properties custom properties of the WebSphere MQ topic connection factory.
Client transport properties client transport properties of the WebSphere MQ topic connection factory.

This link is only present on the explicitly-specified variation of this panel, where you enter all information required to connect to WebSphere MQ. This link does not appear for the CCDT-based variation.

Connection pools connection pools detail of the WebSphere MQ topic connection factory
Session pools session pools detail of the WebSphere MQ topic connection factory.

Under Related items, we can click JAAS - J2C authentication data to configure authentication information for use with the connection factory.

We can specify the following additional properties using WebSphere MQ administrative commands:

See about these properties, refer to the createWMQConnectionFactory.

When specifying WebSphere MQ properties, the following restrictions apply:

A WebSphere MQ topic connection factory has the following properties.

Scope

The level to 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 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 at a different scope, change the scope on the WebSphere MQ topic connection factory collection panel, then click Apply, before clicking the link for the type of resource.

Data type String

Provider

The JMS provider assigned when the topic connection factory is created.

For all topic connection factories using this panel, the provider is the WebSphere MQ messaging provider.

The provider is displayed for information only.

Data type String

Name

The name by which this topic connection factory is known for admin purposes within WAS.

Data type String
Range The name must be unique within the set of JMS topic connection factories defined to the cell.

JNDI name

The JNDI name used to bind the topic connection factory into the JNDI 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

Description

A description of this topic connection factory for administrative purposes within WAS.

Data type String
Default Null

Client channel definition table URL

A URL that points to a WebSphere MQ CCDT.

Data type String

Queue manager

If this topic connection factory 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 WebSphere MQ resource to send or receive messages.

Data type String
Range If this topic connection factory is based on a CCDT, the value must be one of the following:

  • A valid queue manager name

  • A valid queue manager name with the last character an asterisk (*)

  • An asterisk (*)

  • Blank

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

Transport

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

client

Use a TCP/IP-based network connection to communicate with the WebSphere MQ queue manager

bindings then client

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

See about configuring a transport type of bindings then client or bindings, refer to Set the WebSphere MQ messaging provider with native libraries information and Sizing the thread pools used by the WebSphere MQ messaging provider.

Hostname

The host name, IPv4, or IPv6 address of the WebSphere MQ queue manager to connect to.

Data type String

Port

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).

Server connection channel

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.

Use SSL to secure communications with WebSphere MQ

Whether the SSL (SSL) protocol is used to secure network communications with the WebSphere MQ queue manager or queue sharing group.

When using a WebSphere MQ messaging provider topic connection factory in the appserver environment, the appserver manages SSL configuration. To change SSL configuration parameters, use the admin console to navigate to...

Security | SSL certificate and key management panel

When using a WebSphere MQ messaging provider topic connection factory in the client environment, the client takes SSL configuration information from the file...

ssl.client.props

A WebSphere MQ messaging provider topic connection factory can only be configured with a single SSL cipher suite in the SSL configuration. If we specify more than one cipher suite in the SSL configuration for a WebSphere MQ messaging provider topic connection factory, only the first one is used.

Data type Check box. If this check box is cleared, the following SSL properties are disabled:

Centrally managed

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 SSL configuration.

When you select this radio button, the host name and port attributes from the WebSphere MQ messaging provider topic connection factory are used to select an appropriate SSL configuration. To provide the SSL configuration which will be matched to the topic connection factory, see the Dynamic outbound endpoint SSL configuration settings topic listed under related reference.

Data type Radio button

Specific configuration

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

SSL configuration

The specific SSL configuration to use when SSL is to be used to secure network communications with the WebSphere MQ queue manager or queue sharing group.

Is disabled if the Centrally managed radio button is selected and the WebSphere MQ messaging provider resource has been explicitly defined.

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 a SSL configuration of none is selected, the default centrally managed WAS SSL configuration for the WebSphere MQ messaging provider is used.

Data type Drop-down list

Component-managed authentication alias

A user name and password to use when connecting to WebSphere MQ.

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.

Client identifier

The client identifier to specify when connecting to WebSphere MQ messaging provider.

Data type String

Allow cloned durable subscriptions

An option that determines whether multiple instances of a durable subscription can be accessed concurrently by different servers.

Data type Check box
Default Cleared
Range

Selected

Multiple instances of a durable subscription can be accessed concurrently by different servers.

Cleared

Multiple instances of a durable subscription cannot be accessed concurrently by different servers.

Provider version

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 functionality required by the client.

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

Data type String
Range 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

where n is a numeric value greater than or equal to zero.

For example 6.0.0.0.

Support distributed two-phase commit protocol

An option that specifies whether the connection factory supports XA coordination of messaging transactions. Enable this option if multiple resources, including this connection factory, are to be used in the same transaction.

If we 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 WAS.

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

Data type Check box
Default Selected
Range

Selected

The connection factory supports the use of distributed two-phase commit protocols for the coordination of transacted work.

Cleared

The connection factory does not support the use of distributed two-phase commit protocols for the coordination of transacted work.

Do not enable XA when the queue manager specified by the topic connection factory is the only resource in the transaction. Enable XA if transactions involve other resources, including other queues or topics.

Authentication alias for XA recovery

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.

Mapping-configuration alias

This field if 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, under Related items, click JAAS - J2C authentication data .

Data type Drop-down list
Default (none)
Range





Subtopics


WebSphere MQ messaging provider topic connection factory advanced properties

 

Related tasks

Manage Java 2 Connector Architecture authentication data entries
Secure messaging
Set a unified connection factory for the WebSphere MQ messaging provider
Set the WebSphere MQ messaging provider with native libraries information
Sizing the thread pools used by the WebSphere MQ messaging provider
Set a topic connection factory for the WebSphere MQ messaging provider

 

Related

Topic connection factory collection
ssl.client.props client configuration file
Dynamic outbound endpoint SSL configuration settings
Mapping of admin console panel names to command names and WebSphere MQ names
WebSphere MQ resource custom properties settings
WebSphere MQ library
WebSphere MQ messaging provider connection factory broker properties
WebSphere MQ messaging provider connection factory client transport settings
Connection pool settings
Session pool settings

 

Related information

JMS interfaces - explicit polling for messages