A JMS activation specification is associated with one or more message-driven beans and provides the configuration necessary for them to receive messages.
To view this pane in the console, click the following path:
.
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.
You create a JMS activation specification if you want to use a message-driven bean as a J2EE Connector Architecture (JCA) 1.5 resource that can communicate with the default messaging provider. JCA provides Java connectivity between application servers such as WebSphere Application Server, and enterprise information systems. It provides a standardized way of integrating JMS providers with J2EE application servers, and provides a framework for exchanging data with enterprise systems, where data is transferred in the form of messages.
For earlier versions of WebSphere Application Server, the interface between message-driven beans and their destinations is provided by the listener port. The listener port is a messaging component that can be manually started and stopped by the administrator. When it is stopped, the message-driven bean associated with it can no longer process messages. Furthermore, if a message-driven bean fails to process a message several times, the listener port is automatically stopped by the application server. You use listener ports with the MQ Client Link (the WebSphere Version 5 provider) and with WebSphere MQ as an external provider.
It is possible to share a single JMS activation specification with multiple message-driven beans. Doing this simplifies administration because it is only necessary to provide a single set of messaging configuration settings.
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.
Specifies the highest topological level at which application servers can use this resource object.
Required | No |
Data type | Text |
Specifies a JMS provider, which enables asynchronous messaging based on the Java Message Service (JMS). It provides J2EE connection factories to create connections for specific JMS queue or topic destinations. JMS provider administrative objects are used to manage JMS resources for the associated JMS provider.
Required | No |
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 | drop-down 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. The value is a string that is used to select a subset of the available messages. The syntax is based on a subset of the SQL 92 conditional expression syntax, as described in the JMS specification. Refer to the InfoCenter for more information.
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 | drop-down 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 | drop-down list |
The maximum number of messages received from the messaging engine in a single batch.
Required | No |
Data type | Integer |
Default | 1 |
Range | 1 through 2147483647 |
The maximum number of endpoints to which messages are delivered concurrently.
Required | No |
Data type | Integer |
Range | 1 through 2147483647 |
Whether a JMS topic subscription is durable or nondurable
Required | No |
Data type | drop-down 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 activation specification.
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 activation specification. This is a required field when using a durable topic subscription.
Required | No |
Data type | Text |
The name of a target that identifies a group of messaging engines. Specify the type of target using the Target type property.
Required | No |
Data type | Text |
The type of target named in the Target property.
Required | No |
Data type | drop-down list |
Range |
|
This property specifies the significance of the target group.
Required | No |
Data type | drop-down list |
Range |
|
The name of the inbound transport chain that the application should target when connecting to a messaging engine in a separate process to the application. If a messaging engine in another process is chosen, a connection can be made only if the messaging engine is in a server that runs the specified inbound transport chain. Refer to the InfoCenter for more information.
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 server_name panel. The following transport chains are provided, but you can define your own transport chains on that panel.
For more information about using this property with other connection factory properties for workload management of connections, see Administrative properties for JMS connections to a bus.
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 | drop-down list |
Default | Default |
Range |
|