EMS Receive Message Trigger

The EMS Receive Message trigger receives a message from a topic or queue. Each message triggers a new flow. The message gets acknowledged as soon as the EMS Acknowledge activity is encountered in the flow.

Trigger Settings

On the Settings tab, configure the following settings:

Field Required Description
EMS Connection Yes Name of the connection.
Destination Type No The following options are available for the destination type:
  • Queue
  • Topic
Destination   Name of the destination.
Acknowledge Mode  

Auto: The message is acknowledged automatically when it is received.

Explicit Client: The message is acknowledged at a later point by using the Acknowledge activity. If the message is not confirmed before the flow instance ends, the message is redelivered and a new flow instance is created to handle the new incoming message. Ensure that your process confirms the message when using the acknowledge mode.

Explicit Client Dups OK: (Only available for TIBCO Enterprise Message Service) A message that is not acknowledged using the Acknowledge activity before the flow 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 are lazily acknowledged.

Output

The Output tab has the following fields:

Field Required Description
Message Yes The message format is string.
Headers 

destination: The EMS destination from where the flow starter receives the message.

replyTo: The EMS destination where the reply message is sent. The default value is empty.

deliveryMode: The delivery mode of the message. It can be one of the following:

  • PERSISTENT: signifies the messages are stored and forwarded.

  • NONPERSISTENT: messages are not stored and may be lost due to failures in transmission.

  • reliable: this mode is only available when using the TIBCO Enterprise Message Service. For more information, see the TIBCO Enterprise Message Service documentation.

The default value is PERSISTENT.

messageID: The unique ID of the message.

timestamp: The time a message is handed off to an EMS provider to be sent. The time is expressed as the amount of time, in milliseconds, since midnight, January 1, 1970, UTC.

expiration: The expiration time of the message. The time is expressed as the amount of time, in milliseconds since midnight, January 1, 1970, UTC. If set to 0, the message does not expire. The default value is 0.

redelivered: Typically, this item is set when the EMS provider has delivered the message at least once before.

priority: The priority of the message. Priority is a value from 0 to 10. Higher numbers signify a higher priority (that is, 8 is a higher priority than 7). The default value is 4.

correlationID: This ID is used to link a response message with its related request message. This is usually the message ID of a request message when this field is found in a reply message. The default value is empty.