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
.Links marked (online) require access to the Internet. Each link launches a search for the topic in the online information center. When search results are listed, select the topic that corresponds best to your configuration.
Check for updates to this topic (online)
The Configuration tab contains the following attributes:
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 |
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 |
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 |
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 WebSphere Integration Developer.
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 |
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 |
Use the Runtime tab to manage the state of all receiving endpoints defined for the export. You can pause and then resume active endpoints.
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.