WebSphere MQ messaging provider activation specification settings


 

+

Search Tips   |   Advanced Search

 

To set the configuration properties of the selected activation spec for use with the WebSphere MQ messaging provider.

  1. Go to...

    Resources | JMS | Activation specifications

  2. Set the Scope setting.

  3. Select the name of the activation spec

  4. Under General Properties there are four groups of properties:

    • Administration
    • Connection
    • Destination
    • Advanced

    There are two variations of the Connection group:

    CCDT Connection settings group

    A WebSphere MQ administrator can create a single Client Channel Definition Table (CCDT) of all the WebSphere MQ channels supported by queue managers in their enterprise.

    Client channel definition table URL A URL that specifies the 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.

    Explicitly-defined Connection settings group

    If the selected activation spec was not created using a CCDT, enter the following information to configure a connection:

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

    If we clear the check box for the "Use SSL to secure communication with Websphere MQ property", the following properties cannot be used:

    Make any required changes to the Administration, Connection, Destination, 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:

    1. Advanced properties.
    2. Broker properties.
    3. Custom properties.
    4. Client transport properties. This link does not appear for the CCDT-based variation.

    Under Related items, we can click JAAS - J2C authentication data to configure authentication information.

    We can also specify the localAddress property using WebSphere MQ administrative commands.

    When specifying WebSphere MQ properties, the following restrictions apply:

    • Names can have a maximum of 48 characters, with the exception of channels, which have a maximum of 20 characters.
    • The property values specified must match the values specified when configuring WebSphere MQ for JMS resources.

    A WebSphere MQ activation spec 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 (or other resources) at a different scope, change the scope on the WebSphere MQ activation spec collection panel, then click Apply, before clicking the link for the type of resource.

    Data type String

    Provider

    The JMS provider assigned when the activation specification is created.

    For all activation specifications created 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 activation spec is known for admin purposes within WAS.

    Data type String
    Range The name must be unique within the set of activation specifications defined to the cell.

    JNDI name

    The JNDI name used to bind the activation specification 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 activation spec for administrative purposes within WAS.

    Data type String

    Client channel definition table URL

    A URL that points to a WebSphere MQ CCDT.

    Data type String

    Queue manager

    If this activation spec 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 receive messages.

    Data type String
    Range If this activation spec 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 connection factory is based on a CCDT, the value must be a valid queue manager name.

    Transport

    The WebSphere MQ transport type for the connection.

    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:

    • Host name
    • Port
    • Server connection channel

    See:

    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

    This option determines whether the 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 activation specification, the application server manages SSL configuration. To set SSL configuration parameters...

    Security | SSL certificate and key management

    WebSphere MQ messaging provider activation specifications can only be configured with a single SSL cipher suite. If more than one cipher suite is configured, only the first 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 activation specification are used to select an appropriate SSL configuration.

    To provide the SSL configuration which will be matched to the activation specification, see: Dynamic outbound endpoint.

    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 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 an 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

    Destination JNDI name

    The JNDI name for the JMS destination from which messages are consumed for delivery to a message-driven bean (MDB) configured to use this activation specification.

    Data type String

    Message selector

    A message selector expression specifying which messages are to be delivered.

    Data type String

    Destination type

    The type of destination (queue or topic) from which to consume messages.

    Data type Drop-down list
    Range

    Queue

    The Destination JNDI name refers to a JMS destination that is a queue.

    Topic

    The Destination JNDI name refers to a JMS destination that is a topic.

    Durable subscription

    An option to specify whether a durable or nondurable subscription is used to deliver messages to an MDB subscribing to the topic.

    Data type Check box
    Default Cleared (nondurable)
    Range

    Cleared

    Nondurable.

    Selected

    Durable.

    Subscription name

    The name of a durable subscription. This is available only when the Durable subscription check box is selected.

    Data type String

    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 the 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 activation spec 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 activation spec 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.




Subtopics

WebSphere MQ messaging provider activation spec advanced properties
WebSphere MQ messaging provider activation spec broker properties
WebSphere MQ messaging provider activation spec client transport properties

 

Related tasks

Manage Java 2 Connector Architecture authentication data entries
Set the WebSphere MQ messaging provider with native libraries information
Secure messaging
Sizing the thread pools used by the WebSphere MQ messaging provider
Set an activation spec for the WebSphere MQ messaging provider

 

Related

Dynamic outbound endpoint SSL configuration settings
WebSphere MQ resource custom properties settings
WebSphere MQ library Web page
Mapping of admin console panel names to command names and WebSphere MQ names
Activation spec collection

 

Related information

JMS interfaces - explicit polling for messages