EMS Send Message Activity

Settings

On the Settings tab, configure the following settings:

Field	Required	Description
EMS Connection	Yes	Name of the connection.
Destination Type	Yes	The following options are available for destination type: Queue Topic
Destination	Yes	The destination to which a message is sent.
Delivery Delay	Yes	Delivery delay is the minimum length of time, in milliseconds, that must elapse after a message is sent before the EMS provider delivers the message to a consumer.

Input

The Input tab has the following fields:

Field	Required	Description
Message	Yes	The option available for the message format is string.
Destination	No	The destination to which a message is sent. This input item overrides the Destination field on the Settings tab.
Headers	No	correlationID: This ID is used to link a response message to its request message. This field usually has the request message ID, as its default value is empty in a reply 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: It signifies the messages are stored and forwarded. NONPERSISTENT: In this mode, messages are not stored and may be lost due to failures in transmission. reliable: This mode is only available when using TIBCO Enterprise Message Service™. For more information, see the TIBCO Enterprise Message Service documentation. The default value is PERSISTENT. expiration: It establishes 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. priority: This header defines message priority. 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.
messageProperties	No	Message properties allow you to add runtime properties to outgoing JMS messages, as specified in the Input tab. This optional parameter supports only one instance but can include multiple property elements. Each property element represents a single message property and contains the following elements: name: This field is required and specifies the name of the property with one instance. value: This field is required and specifies the value of the property with one instance. type: This optional field specifies the type of the property. If not provided or invalid, it defaults to a string. The following data types are supported in the type field: string boolean short integer long float double

Output

The following is the output of the activity.

Output Item	Datatype	Description
MessageID	string	The unique identifier of the message.

Loop

If you want this activity to iterate multiple times within the flow, enter an expression that evaluates the iteration details. Select a type of iteration from the Type menu. The default type is None, which means the activity does not iterate. For more information, see the Using the Loop Feature in an Activity section in the Flogo® app documentation.