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 Queue

Yes

Name of the queue of the incoming message.

The syntax of the queue name is specific to the JMS provider you are using. For more information about queue 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.

Acknowledge Mode

Yes

The acknowledge mode for the incoming messages. It can be one of the following:

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

  • Client : the message gets acknowledged at a later point by using the Confirm activity. If the message is not confirmed before the process instance ends, the message is redelivered. Ensure that your process definition confirms the message when using this acknowledge mode.

  • 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, is 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, there is a change in the behavior of this feature. Now only the messages that are not confirmed, would be 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, is 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.

  • TIBCO EMS No Acknowledge: the message is not acknowledged when it is received.

  • 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.