WebSphere MQ JMS export binding

Use this page to view or modify the attributes of the selected WebSphere® MQ JMS export binding or to manage the state of endpoints. The artifacts that your binding requires can be configured to be created on the server at deployment time, or you can administer the WebSphere MQ JMS export binding to use artifacts that you created on the server.

To view this administrative console page, click Applications > SCA Modules > module_name > Exports > export_name > Binding > binding_name [MQ JMS].

Parent topic: WebSphere MQ JMS bindings

Configuration tab

The Configuration tab contains the following attributes:

Response Connection Factory JNDI Name

Choose the response connection factory that you want your WebSphere MQ JMS export binding to use. You can either type the JNDI name of the connection factory, or you can use the Browse button to choose from a list of available connection factories.

The response connection factory is used by clients to create a connection to the WebSphere MQ JMS provider.

Property Value
Data type Text

Send MQ JMS Destination JNDI Name

Choose the send destination for the WebSphere MQ JMS export binding. You can either type the JNDI name of the send MQ JMS destination, or you can use the Browse button to choose from a list of available destinations.

The send MQ JMS destination is where the response message will be sent, if not superseded by the JMSReplyTo header field in the incoming message.

Property Value
Data type Text

Failed Event Replay Connection Factory JNDI Name

Choose the failed event replay connection factory for the WebSphere MQ JMS export binding. You can either type the JNDI name of the failed event replay connection factory, or you can use the Browse button to choose from a list of available connection factories.

The failed event replay connection factory is used to create a connection to the WebSphere MQ JMS provider in order to replay failed events.

Property Value
Data type Text

Activation specification JNDI Name

Choose the activation specification for your WebSphere MQ JMS export binding. You can either type the JNDI name of the activation specification, or you can use the Browse button to choose from a list of available activation specifications.

The activation specification is used to connect the JMS export to the bus and destination on which request messages are received.

Property Value
Data type Text

Connection Factory JNDI Name

Shows the connection factory for the WebSphere MQ JMS export binding. This field cannot be edited.

The connection factory is used by the SCA JMS runtime environment when the send destination is on a different Queue Manager than the receive destination. This field is read-only.

Property Value
Data type Text

Receive MQ JMS Destination JNDI Name

Identifies the receive destination for the WebSphere MQ JMS export binding.

The destination shown here is the destination that was defined when the application was developed. The defined destination is used by the system to create an activation specification when you deploy the application. The destination on which inbound requests will be received is the one referenced from inside the activation specification.

Note that if you create your own resources or modify the generated activation specification to use a different destination, this field still reports the original value that was defined in IBM Integration Designer.

In all instances, the destination where inbound requests are placed is the one found in the activation specification, not necessarily the one reported in this field.

Property Value
Data type Text

Callback JMS Destination JNDI Name

Identifies the callback destination for the WebSphere MQ JMS export binding. The callback destination is determined by the choice of response connection factory.

The callback JMS destination is an SCA JMS System destination used to store correlation information. Do not read from or write to this destination.

Property Value
Data type Text

Runtime tab

Use the Runtime tab to manage the state of all receiving endpoints defined for the export. You can pause and then resume active endpoints.

Note: The Runtime tab applies only to applications on Version 7 of the runtime environment.

The node, server, and status for each endpoint are listed in the Receiving Endpoints table. The value for the Status column can be Active, Paused, or Stopped.

To pause or resume the endpoint, perform the following task:
  1. Select the check box next to the endpoint.
  2. Click Pause or Resume to change the state of the endpoint.