JMS import binding

Use this page to view or modify the attributes of the selected JMS import binding or to manage the state of endpoints. The artifacts that your import binding requires can be configured to be created on the server at deployment time, or you can administer the JMS 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 [JMS].


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)

Configuration tab

The Configuration tab contains the following attributes:

Connection Factory JNDI Name

Choose the connection factory that you want your JMS 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 a service integration bus in order to send a request.

Property Value
Data type Text

Send JMS Destination JNDI Name

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

The send JMS destination is where the request, or outgoing message, will be sent.

Property Value
Data type Text

Failed Event Replay Connection Factory JNDI Name

Choose the failed event replay connection factory for the JMS import 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 JMS provider in order to replay failed events.

Property Value
Data type Text

Activation specification JNDI Name

Choose the activation specification for the JMS import 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 for receiving response messages to a request.

Property Value
Data type Text

Receive JMS Destination JNDI Name

Identifies the receive JMS destination JNDI name.

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 WebSphere® Integration Developer.

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.

Callback JMS Destination JNDI Name

Identifies the callback JMS destination JNDI name.

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

Runtime tab

Use the Runtime tab to manage the state of all receiving endpoints defined for the import. 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.