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:

  • Simple — A message with no body portion.

  • Bytes — A stream of bytes.

  • Map — A set of name/value pairs. The names are strings, and the values are simple data types (Java primitives), an array of bytes (use the Binary datatype to map this data), or a string. Each item can be accessed sequentially or by its name.

  • Object — A serializable Java object.

  • Object Ref — An object reference to a Java object.

  • Stream — A stream of Java primitives, strings, or arrays of bytes. Each value must be read sequentially.

  • Text — The message is a java.lang.String.

  • XML Text — The message is XML text.

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:

  • Auto : the message is automatically acknowledged when it is received.

  • Client: the message is acknowledged when the process implementing the operation ends successfully.

  • Dups OK : the message is acknowledged automatically when it is received. JMS provides this mode for lazy acknowledgement, but ActiveMatrix BusinessWorks acknowledges messages upon receipt.

  • TIBCO EMS Explicit : (only available for TIBCO Enterprise Message Service) a message which is not acknowledged using the Confirm activity before the process instance ends, are redelivered instead of all messages in the session. The session is not blocked and one session handles all incoming messages for each process instance.

    Note: In the ActiveMatrix BusinessWorks 5.10 release, a change occurs in the behavior of this feature. Now only the messages that are not confirmed, are redelivered.
  • TIBCO EMS Explicit Dups OK : (only available for TIBCO Enterprise Message Service) a message which is not acknowledged using the Confirm activity before the process instance ends, are redelivered instead of all messages in the session. The session is not blocked and one session handles all the incoming messages for each process instance. The messages however, would be lazily acknowledged.

Acknowledge Mode

Yes

  • Dups OK — the message is acknowledged automatically when it is received. JMS provides this mode for lazy acknowledgement, but ActiveMatrix BusinessWorks acknowledges messages upon receipt.

  • Transactional — this mode is used when a transaction that can process JMS messages is included in the process definition. The message is acknowledged when the transaction commits. For more information about creating transactions that JMS activities can participate in, see TIBCO ActiveMatrix BusinessWorks™ Process Design.

  • Local Transactional — this mode is used when a transaction involves only JMS messages. For more information about creating transactions that JMS activities can participate in, see TIBCO ActiveMatrix BusinessWorks™ Process Design.

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.