A JMS activation specification is associated with one or more message-driven beans and provides the configuration necessary for them to receive messages.
In the administrative console page, to view this page click .
A JMS activation specification is used to provide configuration information when a JMS endpoint (message-driven bean application) is deployed and activated against the default messaging provider.
All properties apart from Name, JNDI name, Destination JNDI name, and Authentication alias are overridden by appropriately named activation-configuration properties in the deployment descriptor of an associated EJB 2.1 message-driven bean. For an EJB 2.0 message-driven bean, the Destination type, Subscription durability, Acknowledge mode and Message selector are overridden by the corresponding elements in the deployment descriptor. For either type of bean the Destination JNDI name can be overridden by a value specified in the message-driven beans bindings.
Configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
The level to which this resource definition is visible; for example, the cell, node, cluster, or server level.
The scope displayed is for information only, and cannot be changed on this panel. If you want to browse or change this resource (or other resources) at a different scope, change the scope on the messaging provider settings panel, then click Apply, before clicking the link for the type of resource.
Required | Yes |
Data type | Text |
The name by which this resource is known for administrative purposes.
Required | Yes |
Data type | Text |
The JNDI name for the resource.
Required | Yes |
Data type | Text |
Whether the message-driven bean uses a queue or topic destination.
Required | Yes |
Data type | Selection list |
Default | Queue |
Range |
|
JNDI Name of destination
Select the type of destination on the Destination type property.
Required | Yes |
Data type | Text |
The JMS message selector used to determine which messages the message-driven bean receives.
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.
A null value (an empty string) indicates that there is no message selector for the message consumer.
Required | No |
Data type | Text |
Default | Null |
The name of the bus to connect to.
Required | No |
Data type | Custom |
How the session acknowledges any messages it receives.
Required | No |
Data type | Selection list |
Default | Auto-acknowledge |
Range |
|
The name of a J2C authentication alias used for component-managed authentication of connections to the service integration bus.
A J2C authentication alias specifies the user ID and password that is used to authenticate the creation of a new connection to the JMS provider.
Required | No |
Data type | Selection list |
The maximum number of messages received from the messaging engine in a single batch.
Required | No |
Data type | Text |
Default | 1 |
The maximum number of endpoints to which messages are delivered concurrently.
Required | No |
Data type | Text |
Default | 10 |
Whether a JMS topic subscription is durable or nondurable
Required | No |
Data type | Selection list |
Default | Durable |
Range |
|
The subscription name needed for durable topic subscriptions. Required field when using a durable topic subscription.
This subscription name must be unique within a given client identifier.
Required | No |
Data type | Text |
The JMS client identifier needed for durable topic subscriptions on all connections created using this activationSpec.
Required | No |
Data type | Text |
The name of the messaging engine used to store messages delivered to durable subscriptions for objects created from this JMS activationSpec. Required field when using a durable topic subscription.
Required | No |
Data type | Text |
The name of the protocol that resolves to a group of messaging engines.
If the selected messaging engine is in the same server as the application, a direct in-process connection is made and this transport chain property is ignored.
The transport chains represent network protocol stacks operating within a server. The name you specify must be one of the transport chains available in the server that hosts the messaging engine, as listed on the panel. The following transport chains are provided, but you can define your own transport chains on that panel.
Required | No |
Data type | Text |
Default | Null |
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
You can override this property for individual JMS destinations by setting the Read ahead property on the JMS destination.
Required | No |
Data type | Selection list |
Default | Default |
Range |
|