Message listener class name. The listener class dispatches messages to Process Server.

To deploy processes created with Process Developer, use the listener class name as

com.activee.rt.mom.jms.transport.AeJmsBpelListener

.

If needed, you can create a custom listener class that extends the default listener class to include custom behavior. Specify the custom listener in this field.

Default is

com.activee.rt.mom.jms.transport.AeJmsBpelListener

.

Number of connections to keep open. When the server starts, the JMS manager creates instances of this class that serve as asynchronous consumers on the destination. Each asynchronous consumer has its own connection to the JMS server. The number of consumers and connections created is controlled by the listener count.

Default is

15

.

Specifies an identity for a JMS request. The identity is a role-based or group membership. If not specified, the request runs anonymously. Using this property is analogous to specifying an identity for a message-driven bean in

ejb-jar.xml

.

Use this option if you want the JMS listener to invoke processes that have been secured with the

Allowed Roles

restriction in the Process Deployment Descriptor (pdd). Another use case is using the aeRunAs header for Human Task (B4P) operations. This case allows you to specify a RunAs Identity with the abTrust security role.

If enabled for a supported platform, and if the required setup has been performed, indicates that a JMS read from the queue and the process engine must participate in the same transaction.

Select the

Rollback On Error

option if you want to decline messages that encounter an exception, or failed messages, and move to the next message. For example, the exception could be because of an authentication failure.

If you select this option, you must configure how the message server must handle failed messages. For example, you can configure the message server to redeliver failed messages for a specified number of times. Or, you can configure the server to move failed messages to a dead letter queue and take action later. For example, add the following policy entry to configure Apache ActiveMQ server to move failed messages to a dead letter queue:

<policyEntry queue=">">
    <deadLetterStrategy>
	<individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true" processNonPersistent="true"/>
   </deadLetterStrategy>
</policyEntry>

Here, if the original queue is

userIDs

, the dead letter queue that Apache ActiveMQ server creates is

DLQ.userIDs

.

The

Rollback on Error

option does not apply to messages that were delivered to target processes. A message is considered successfully processed if it invokes a target process, even if the process fails.

For new queues and listeners, the

Rollback on Error

option is selected by default.