Message-driven bean assembly settings

Use this page to configure the assembly properties of message-driven beans

Use this page to configure the assembly properties of message-driven beans. For more information about the effect of JMS properties, such as message selectors and message acknowledgement, see the WebSphere MQ Using Java book, SC34-5456 or Sun's Java Message Service (JMS) specification documentation.

The following notebook pages are available:

General properties
Specify general assembly properties for the message bean.
Advanced properties
Specify advanced assembly properties for the message bean.
Bindings properties
Specify bindings assembly properties for the message bean.
EJB name
The logical name for the message bean (as an enterprise bean)

The logical name for the message bean (as an enterprise bean). This name must be unique within the EJB module. There is no relationship between this name and the JNDI name.

Data type String
Units Not applicable
Default Null
Range Up to 30 ASCII characters
Display name
A short name that is intended to be displayed by graphical user interfaces
Data type String
Units Not applicable
Default Null
Range Up to 30 ASCII characters
Description
A description of the message bean, for administrive use
Data type String
Units Not applicable
Default Null
Range Up to 30 ASCII characters
EJB class
The full package name of the message bean class

Specify the full package name of the message bean class, for example, com.ibm.ejs.doc.account.MessageBean. You can either type the class name or click Browse to locate an existing class file.

Data type String
Units Not applicable
Default Null
Range Up to 30 ASCII characters
Transaction type
Whether the message bean manages its own transactions or the container manages transactions on behalf of the bean

Whether the message bean manages its own transactions or the container manages transactions on behalf of the bean. All messages retrieved from a specific destination have the same transactional behavior. To enable the transactional behavior that you want, configure the JMS destination with the same transactional behavior as you configure for the message bean.

Data type Enum
Units Not applicable
Default Bean
Range
Bean
The message bean manages its own transactions
Container
The container manages transactions on behalf of the bean
Message selector
The JMS message selector to be used to determine which messages the message bean receives

The JMS message selector to be used to determine which messages the message bean receives; for example: 

JMSType='car' AND color='blue' AND weight>2500

The selector string can refer to fields in the JMS message header and fields in the message properties. Message selectors cannot reference message body values.

Data type String
Units Not applicable
Default Null
Range A String, up to 30 ASCII characters, whose syntax is based on a subset of the SQL92 conditional expression syntax.
Acknowledge mode
How the session acknowledges any messages it receives.

This property applies only to message-driven beans that uses bean-managed transaction demarcation (Transaction type is set to Bean).

Data type Enum
Units Not applicable
Default Auto Acknowledge
Range
Auto Acknowledge
The session automatically acknowledges a message when it has either successfully returned from a call to receive, or the message listener it has called to process the message successfully returns.
Dups OK Acknowledge
The session lazily acknowledges 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
Whether the message bean uses a queue or topic destination.
Data type Enum
Units Not applicable
Default Null
Range
Queue
The message bean uses a queue destination.
Topic
The message bean uses a topic destination.
Subscription durability
Whether a JMS topic subscription is durable or non-durable.
Data type Enum
Units Not applicable
Default Null
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
Non-durable 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.

A non-durable subscriber can only be used in the same transactional context (for example, a global transaction or an unspecified transaction context) that existed when the subscriber was created. For more information about this context restriction, see "The effect of transaction context on non-durable subscribers".

Listener port name
The name of the listener port for this message bean.

The name of the listener port for this message bean (as defined on the WebSphere administrative console).

Data type String
Units Not applicable
Default Null
Range Up to 30 ASCII characters

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.