Use this page to view or modify the attributes of the selected native WebSphere MQ Import binding. 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 Applications > SCA Modules > [Content pane] module_name > [Module components] Imports > import_name > Binding > binding_name [native MQ].
Choose the connection factory that you want your native WebSphere MQ Import binding to use. You must 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 must 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 listener port for your native WebSphere MQ Import binding. You can type in the name of the port, or you can use the Browse button to see a list of available ports.
The listener port is used to connect the import to WebSphere MQ and the destination where incoming or request messages are placed.
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 which was defined when the application was developed. The defined destination is used by the system to create a listener port when you deploy the application. The destination from which messages will be received is the one referenced from inside the listener port.
Note that if you create your own resources or modify the generated listener port to point to a different destination this field still reports the original value that was defined in WebSphere Integration Developer.
In all instances the destination where incoming or request messages are placed is the one found in the listener port, not necessarily the one reported in this field.
Property | Value |
---|---|
Data type | Text |