Native MQ export binding

Use this page to view or modify the attributes of the selected native WebSphere® MQ 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 native WebSphere MQ 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 [native MQ].


Links marked (online) require access to the Internet.

Check for updates to this topic (online)

Configuration tab

The Configuration tab contains the following attributes:

Connection Factory JNDI Name

Choose the connection factory that you want your native WebSphere MQ 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 connection factory is used to obtain connections to WebSphere MQ in order to send response messages to the Send MQ Destination.

Property Value
Data type Text

Send MQ Destination JNDI Name

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

The send MQ destination is where the response message will be sent, if not superseded by the ReplyToQ and ReplyToQMgr MQMD header fields in the incoming message.

Property Value
Data type Text

Activation specification JNDI Name

Choose the activation specification for your native WebSphere MQ 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 export to WebSphere MQ Queue Manager and the destination from which messages are received.

Property Value
Data type Text

Receive MQ Destination JNDI Name

Identifies the receive destination for the native WebSphere MQ 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 native WebSphere MQ export binding. The callback destination is determined by the choice of response connection factory.

The callback MQ destination is where the response or incoming message should be placed.

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.