Input port collection
Use this page to view the configuration properties of input ports..
An input port specifies the properties needed by receiver beans as session
beans. Receiver beans as message-driven beans do not need an input port, because
the properties needed are associated with the deployed message-driven bean
and the Message Listener service.
To view this administrative console page, click Resources > Extended
Messaging Providers > Input Port .
Configuration tab
- Name
- The name by which the input port is known for administrative purposes.
Data type |
String |
Units |
En_US ASCII characters |
- JNDI Name
- The JNDI name for the resource.
- Description
- A description of the input port, for administrative purposes.
- Category
- A string that can be used to classify or group the resource.
Data type |
String |
Range |
1 through 30 ASCII characters |
- JMS Connection Factory JNDI Name
- The JNDI name for the JMS connection factory to be used by the
input port; for example, jms/connFactory1.
- JMS Destination JNDI Name
- The JNDI name for the destination to be used by the input port;
for example, jms/destn1.
- JMS Acknowledgement Mode
- JMS acknowledgment mode to be used for acknowledging messages.
This property applies only to message-driven beans that use bean-managed
transaction demarcation (Transaction type is set to Bean).
Default |
Auto Acknowledge |
Range |
- Auto Acknowledge
- The session automatically acknowledges a message in either of the following
cases:
- When the session has successfully returned from a call to receive a message.
- When the session has called a message listener to process the message
and received a successful response from that listener.
- Dups OK Acknowledge
- The session acknowledges only the delivery of messages. This is likely
to result in the delivery of some duplicate messages if JMS fails, so it should
be used only by consumers that are tolerant of duplicate messages.
|
- Destination Type
- The type of the JMS resource.
Default |
Queue |
Range |
- Queue
- The receiver bean receives messages from a queue destination.
- Topic
- The receiver bean receives messages from a topic destination.
|
- Subscription durability
- [Topic destinations only.] Specifies whether a JMS topic subscription
is durable or non-durable.
Default |
Durable |
Range |
- Durable
- A subscriber registers a durable subscription with a unique identity that
is retained by JMS. Subsequent subscriber objects with the same identity resume
the subscription in the state it was left in by the earlier subscriber. If
there is no active subscriber for a durable subscription, JMS retains the
subscription's messages until they are received by the subscription or until
they expire.
- Nondurable
- Nondurable subscriptions last for the lifetime of their subscriber object.
This means that a client sees the messages published on a topic only while
its subscriber is active. If the subscriber is not active, the client is missing
messages published on its topic.
|
- Reply JMS Connection Factory JNDI Name
- JNDI name of the JMS Connection Factory to be used for replies.
- Reply JMS Destination JNDI Name
- JNDI name of the JMS Destination to be used for replies.

Adding a new input port
Configuring an input port

Administrative console buttons
Administrative console filter settings
Administrative console preference settings
Input port settings
Extended messaging provider settings
Searchable topic ID:
ueac_inputport
Last updated: Jun 21, 2007 8:07:48 PM CDT
WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/webui_pme/ui/ueac_inputport.html