MessageSubscriber Trigger

The Message Subscriber trigger listens for a published message from the TIBCO Cloud Messaging service.

Trigger Settings

Important: Refer the limitations outlined in the Overview section before using this trigger.

The Trigger Settings tab has the following fields.

Field Description
Connection Name of the TIBCO Cloud Messaging connection.
Durable Subscriber By default, this field is set to False. Setting this field to True, changes the subscriber to a durable subscriber. As a durable subscriber, if the app goes down, any incoming messages during the period when the app was down will be preserved and delivered once the app comes back up again.
Note: A trigger marked as a durable subscriber should have been running at least once in order for it to receive pending messages that were sent while the app was down.
When this field is set to True, the following fields appear:
  • Durable Name: Enter a name for the subscription. This is a required field.
  • Durable Type: The following durable types are supported:
    • Shared- For multiple instances of an app, the messages received will be distributed among the app instances in a round-robin manner.
    • Standard-For every unique instance of an app, all the apps will receive all the messages. The messages will not be distributed.
      Note:
      • In a single app, the same connection can not be used for two or more TCMMessageReceiver triggers and two or more handlers in a single trigger for Standard durable type. To configure Standard durable type for two more triggers or handlers create different connections.
      • In container deployment, if an app is scaled to more that one instance only the last instance receives all messages.
  • Message Ack Mode: The following acknowledgment types are supported:
    • Auto- In this mode, messages are auto acknowledged as soon as they are received from the TCM. In case of failure in business logic the messages are not redelivered.

      Use this mode if message redelivery is not preferred.

    • Explicit- In this mode, the message received by the MessageSubscriber Trigger must be explicitly acknowledged within the flow using TCMMessageAck activity. Any unacknowledged messages will be re-delivered to the new durable subscriber configured with the same durable name.
Destination Name of the message destination. If this field is left blank then it will receive all messages, otherwise only the messages with the specific destination set.
Content Matcher To specify the attributes that match the incoming message click Add row. For each attribute specify its name, type, and value.
Important: You cannot have two subscribers with the same durable name but different destinations running concurrently. You must stop the subscriber that was already running before your start the second subscriber. This is also true for blue-green deployments supported by PaaS platforms, such as TIBCO Cloud Integration. So, do not update the destination name in blue-green deployments.

Output Settings

The fields selected in this tab will be available in the output schema in the Map to flow Inputs tab.

Field Description
Message Schema An example JSON object that you want to receive from TIBCO Cloud Messaging service.

Map to flow Inputs

This tab displays the schema specified in the Output Settings tab in a tree structure format. The output of an activity is displayed for informational purposes only and cannot be modified or altered.

The properties that are displayed in the Output tab schema correspond to the output of this activity and can be used as input by subsequent activities in the flow.

Related concepts
Related reference