Use this page to view or modify the attributes of the selected native WebSphere® MQ import binding or to manage the state of endpoints. The artifacts that your binding requires can be configured to be automatically created at deployment time, or you can administer the native WebSphere MQ import 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.
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 import 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 by the system to obtain connections to WebSphere MQ in order to send a request.
Property | Value |
---|---|
Data type | Text |
Choose the send destination for the native WebSphere MQ import 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 request, or outgoing message, will be sent.
Property | Value |
---|---|
Data type | Text |
Choose the activation specification for your native WebSphere MQ import binding. You can either type in 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 import to WebSphere MQ and the destination where incoming or response messages are received.
Property | Value |
---|---|
Data type | Text |
Identifies the receive destination for the native WebSphere MQ import binding.
The receive MQ destination is where the response or incoming message should be placed.
The destination reported 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 from which messages 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 point to a different destination, this field still reports the original value that was defined in IBM Integration Designer.
In all instances, the destination where incoming or request messages 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 import binding.
The callback MQ 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 |
Use the Runtime tab to manage the state of all receiving endpoints defined for the import. 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.