Use this page to view or modify the attributes of the selected JMS export binding or to manage the state of endpoints .
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 JMS 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 by the system to connect to a bus to send the response message.
Property | Value |
---|---|
Data type | Text |
Choose the send destination for the JMS export 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 response message will be sent, if not superseded by the JMSReplyTo header field in the incoming message.
Property | Value |
---|---|
Data type | Text |
Default (if configured so that the send JMS destination is generated on the server at deployment time) | module_name/export_name_SEND_D |
Choose the failed event replay connection factory for the JMS export 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 by the system to create a connection to the JMS provider in order to replay failed events.
Property | Value |
---|---|
Data type | Text |
Choose the activation specification for the JMS 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 JMS export to the bus and destination on which request messages are received.
Property | Value |
---|---|
Data type | Text |
Identifies the receive JMS destination.
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.
Identifies the callback JMS destination.
The callback JMS destination is an SCA JMS System destination used to store correlation information. Do not read from or write to this destination.
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.