Use this panel to view or change the configuration properties of the selected activation specification for use with the WebSphere® MQ messaging provider. These configuration properties control how connections are created to associated queues and topics.
Under Related Items, you can click JAAS - J2C authentication data to configure authentication information for use with the activation specification.
You can also specify the -localAddress property by using the createWMQActivationSpec WebSphere MQ administrative command.
If WebSphere MQ functionality has been disabled at a scope that affects this WebSphere MQ messaging provider resource, then an informational message indicating that WebSphere MQ has been disabled appears. In a single server environment this informational message is only displayed when the server is restarted after WebSphere MQ functionality has been disabled. For more information see Disabling WebSphere MQ functionality in WebSphere Application Server.
A WebSphere MQ activation specification has the following properties.
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 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 activation specification collection panel, then click Apply, before clicking the link for the type of resource.
Information | Value |
---|---|
Data type | String |
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.
Information | Value |
---|---|
Data type | String |
The name by which this activation specification is known for administrative purposes within WebSphere Application Server.
Information | Value |
---|---|
Data type | String |
Range | The name must be unique within the set of activation specifications defined to the cell. |
The JNDI name that is 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.
Information | Value |
---|---|
Data type | String |
A description of this activation specification for administrative purposes within WebSphere Application Server.
Information | Value |
---|---|
Data type | String |
Default | Null |
The information required to configure a connection depends on whether the selected activation specification 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 WebSphere MQ Using Java section of the WebSphere MQ information center.
A URL that specifies the location of a WebSphere MQ CCDT.
Information | Value |
---|---|
Data type | String |
If the specified activation specification 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 receive messages.
Information | Value |
---|---|
Data type | String |
Range | If this activation
specification is not
based on a CCDT, the value must be a valid queue manager name. If
this activation specification 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.
Information | Value |
---|---|
Data type | Drop-down list |
Default | Bindings, then client |
Range |
|
If this radio button is selected, this means that the connection to the WebSphere MQ queue manager is made using the information supplied by the host name and port properties.
Selecting this option enables the host name and port properties, and disables the connection name list property. To enter connection name list information, click Enter host and port information in the form of a connection name list.
This radio button is only available if the scope property specifies a cell, or if the scope property specifies a node or server and that node or server is running WebSphere Application Server Version 8.0 or later.
Information | Value |
---|---|
Data type | Radio button |
The host name, IPv4, or IPv6 address of the WebSphere MQ queue manager to connect to.
Information | Value |
---|---|
Data type | String |
The port number on which WebSphere MQ is listening.
Information | Value |
---|---|
Data type | Integer |
Default | 1414 |
Range | The value must be in the range 1 to 65536 (inclusive). |
If this radio button is selected, this means that the connection to the WebSphere MQ queue manager is made using the information supplied by the connection name list property.
Connection name lists can be used to connect to a single queue manager or to a multi-instance queue manager. For more information on using a multi-instance queue manager, see the WebSphere MQ information centre. Selecting this option enables the connection name list property and disables the host name and port properties. To enter separate host and port information, click Enter host and port information in the form of separate host and port values.
This radio button is only available if the scope property specifies a cell, or if the scope property specifies a node or server and that node or server is running WebSphere Application Server Version 8.0 or later.
Information | Value |
---|---|
Data type | Radio button |
The connection name list specifying the host name and port details to use when you want the activation specification to connect to a multi-instance queue manager.
This property must only be used to allow connection to a multi-instance queue manager. It must not be used to allow connections to non-multi-instance queue managers as that can result in transaction integrity issues.
Information | Value |
---|---|
Data type | String |
Default | Unset |
Range | This
field must be set to a string in the following form: host[(port)][,host(port)] The port information is optional, and if not specified, defaults to 1414. host must be a valid TCP/IP host name or IPv4 or IPv6 address. port must be an integer value in the range 1 to 65536 (inclusive). For example: localhost(1234),remotehost1(1234),remotehost2 |
When the connection name list property is specified, the host name or port properties are automatically set to the host name and port number of the first entry in the connection name list. So if you specified localhost(1234),remotehost1(1234),remotehost2, the host name would be set to localhost and port would be set to 1234.
This property is only available if the scope property specifies a cell, or if the scope property specifies a node or server and that node or server is running WebSphere Application Server Version 8.0 or later.
[29/09/10 12:15:27:468 BST] 00000018 J2CUtilityCla W J2CA0008W: Class com.ibm.mq.connector.inbound.ActivationSpecImpl used by resource cells/L3A3316Node01Cell/resources.xml#J2CResourceAdapter_1284547647859 did not contain method setConnectionNameList. Processing continued.In this case the information in the host name and port properties are used to connect to a queue manager.
The WebSphere MQ server connection channel name used when connecting to WebSphere MQ.
Information | Value |
---|---|
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 activation specification 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.
You can only use one cipher suite in the SSL configuration for a WebSphere MQ messaging provider activation specification . If you specify more than one cipher suite, only the first one is used.
Information | Value |
---|---|
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 activation specification are used to select an appropriate SSL configuration. If host and port information has been supplied to the activation specification by a connection name list this means that the host name and port information of the first element in the list are used to select an appropriate SSL configuration. To provide the SSL configuration which will be matched to the activation specification, see the Dynamic outbound endpoint SSL configuration settings topic listed under related reference.
Information | Value |
---|---|
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.
Information | Value |
---|---|
Data type | Radio button |
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.
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.
Information | Value |
---|---|
Data type | Drop-down list |
The JNDI name for the JMS destination from which messages are consumed for delivery to a message-driven bean (MDB) that is configured to use this activation specification.
Information | Value |
---|---|
Data type | String |
A message selector expression specifying which messages are to be delivered.
Information | Value |
---|---|
Data type | String |
The type of destination (queue or topic) from which to consume messages.
Information | Value |
---|---|
Data type | Drop-down list |
Range |
|
An option to specify whether a durable or nondurable subscription is used to deliver messages to an MDB subscribing to the topic.
Information | Value |
---|---|
Data type | Check box |
Default | Cleared (nondurable) |
Range |
|
The name of a durable subscription. This is available only when the Durable subscription check box is selected.
Information | Value |
---|---|
Data type | String |
The client identifier to specify when connecting to the WebSphere MQ messaging provider.
Information | Value |
---|---|
Data type | String |
An option that determines whether multiple instances of a durable subscription can be accessed concurrently by different servers.
Information | Value |
---|---|
Data type | Check box |
Default | Cleared |
Range |
|
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.
Information | Value |
---|---|
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. |
The user name and password to use when connecting to WebSphere MQ.
Information | Value |
---|---|
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. |