Cloud FTL Subscriber

Cloud FTL Subscriber is a process starter activity that starts the process based on the receipt of a message over a transport. The transport details are pre-configured in TIBCO FTL Realm Server running in TIBCO Cloud Integration.

General

The General tab has the following fields.

Field Literal Value/Process Property/Module Property Description
Name No The name to be displayed as the label of the activity in the application.
Content Matcher Yes Specifies Cloud FTL Subscriber activity's interest in messages based on their content. The syntax for example is, {"My-Long":123}.

A content matcher selects a subset of messages from a message stream according to the fields and values in those messages.

Format No Defines the set of fields in the message that is sent by the FTL Publisher activity. The form of each FTL message (its field names and their value datatypes) is governed by a format. The supported formats are:
  • Custom: can be defined by using the Input Editor. The Input Editor is enabled only for the Custom format option.
  • Keyed Opaque: is a built-in format that contains a text key field and a binary (opaque) data field.
  • Opaque: is a built-in format that contains a binary (opaque) data field.
Format Name Yes The name of the format of the Cloud FTL Subscriber message. This field is visible only when the Custom format is selected.

Description

Provide a short description of the activity here.

Advanced

The Advanced tab has the following fields.

Field Literal Value/Process Property/Module Property Description
Sequence Key No This field can contain an XPath expression that specifies which processes should run in sequence. Process instances with sequencing keys that evaluate to the same value are executed sequentially as the process instance was created.
Custom Job Id No This field can contain an XPath expression that specifies a custom ID for the process instance.
FTL Queue Dispatcher Threads Yes Specifies the number of threads to use for dispatching events from the FTL event queue.
FTL Queue Size Yes Size of FTL event queue.
FTL Queue Overflow Policy Yes This field is enabled when the queue size is greater than zero. It is pre-set to Discard None.
Activity Worker Threads Yes Must be greater than zero. By default, the equivalent of half of the TIBCO Cloud Integration engine thread pool is created.

For example, if the engine thread pool is eight, then the Cloud FTL Subscriber activity creates four threads for processing the incoming FTL message.

Output Editor

The Output Editor tab defines the schema to use for incoming messages. This tab gets enabled only when you select the Custom format.

Output

The output for the activity depends on the Format you select in the General tab. If you select the Custom format, the output is a data element defined in the Output Editor tab.