FTL Publisher

FTL Publisher is a synchronous activity that publishes (sends) a message over a transport that is abstracted through a TIBCO FTL application endpoint. The transport details are not configured in the FTL Publisher activity, instead it is configured in TIBCO FTL Realm Server.

General

The General tab has the following fields.

Field Literal Value/Module Property Description
Name No The name to be displayed as label of the activity in the application.
FTL Realm Server Connection Yes The shared resource containing information for connecting to TIBCO FTL Realm Server. See FTL Realm Server Connection for more details.
Endpoint Yes TIBCO FTL application endpoint which is an abstraction for the underlying transports on which the FTL Publisher activity sends messages. The endpoint can have more than one transport.

Click the Browse button to locate the endpoints defined on the TIBCO FTL Realm Server.

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.
  • Predefined: is already defined in the TIBCO FTL Realm Server for the FTL application. The Predefined format requires a format name and this can be obtained from the TIBCO FTL Realm Server using the Browse button.
Format Name Yes The name of the Predefined or Custom format.

This field is displayed when the Custom or Predefined format is selected.

In addition, selecting the Predefined format enables the Browse button. Click the Browse button to obtain the predefined formats from the TIBCO FTL Realm Server.

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
Retry Duration Yes This field specifies the retry duration for reconnecting to a persistent server.

The value is in seconds.

When the persistent server does not get accessed (because of network failure or quorum unavailability), retrying to connect to the server can be configured with this field. The value of this property determines the retry behavior. The supported values are:
  • 0: No retry. This call raises an exception. This is the default behavior.
  • 1: Synchronously retry the interaction until it succeeds. This call returns only upon success.
  • n (Any positive double value): Retry the interaction for n seconds. Return upon success or raise an exception after timeout.

Input Editor

The Input Editor gets enabled only when Custom format is chosen in the General tab. The schema must match the schema of the input for the activity shown on the Input tab.

Input Item Datatype Description
MessageType complex The message type used in the application.

From the Schemas folder, drag the Message : MessageType element on to the process editor.

Note: Input Schema does not support anyType element.

Input

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

Fault

The Fault tab lists the possible exceptions thrown by this activity.

Fault Thrown when...
FTLPublisherActivityFault FTL Publisher fails to publish a message due to a runtime error.
FTLCreateMessageFault The FTL message could not be created.
FTLSendMessageFault The FTL message could not be published.