Configuration
The Configuration tab has the following fields.
Field |
Global Var? |
Description |
Name |
No |
The name to appear as the label for the activity in the process definition. |
Description |
No |
Short description of the activity. |
JMS Connection |
No |
The JMS connection. For more information about creating a JMS connection, see JMS Connection . |
Destination Topic |
Yes |
Name of the topic of the incoming message. The syntax of the topic name is specific to the JMS provider you are using. For more information about topic names, see your JMS provider documentation. Note: If you are using TIBCO Enterprise Message Service as your JMS provider, you can use the Browse button next to this field after specifying a valid connection in the JMS Connection field. The Browse button displays a list of configured destinations in the JMS server that are appropriate for this activity.
|
Message Type |
|
The type of the message. This can be one of the following:
|
Durable Subscription |
Yes |
Specifies a durable subscription. You must specify a name in the Subscription name field that is registered with the JMS application as the durable subscription name. |
Subscription Name |
Yes |
The subscription name registered with the JMS application for durable subscriptions. This field is only available when the Durable Subscription field is checked. Once a durable subscription is created, it can only be removed by accessing the administration tool of the JMS provider. For more information about managing durable subscriptions, see the documentation of your JMS provider. |
Suppress Local Messages |
Yes |
Specifies to not receive messages on the specified topic name when the message origin is the JMS application on the same connection as the process engine. If your process definition publishes and subscribes to messages with the same topic name, this option is useful if you want to specify whether to receive messages sent by the same JMS application that published the message. Checking this field prevents the process from receiving messages sent by the same connection. Unchecking this option specifies messages sent by the same connection should be received. |
Acknowledge Mode |
Yes |
This field is available when a JMS transport is selected. This field specifies the acknowledgement mode to be used for incoming messages. It can be one of the following:
|
Acknowledge Mode |
Yes |
|
Max Sessions (Read Only) |
No |
When the Acknowledge Mode field is set to "Client", "Transactional" or "Local Transactional", this read-only field appears to notify you that only one session can receive incoming topic messages until the message is confirmed. When a JMS topic message is received, the session is blocked until the message is acknowledged. Because all sessions subscribed to JMS topics receive the same messages, only one session can actively listen for new messages until each message is confirmed. |