The Message Subscriber trigger listens for a published message from the TIBCO Cloud Messaging service.
Refer the limitations outlined in the Overview section before using this trigger.
Trigger Settings
The Trigger Settings tab has the following fields.
Field Description
Connection Name of the TIBCO Cloud Messaging connection.
Field Description 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.
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.
● 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.
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.
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.
TCMMessagePublisher
This activity sends a message to the TIBCO Cloud Messaging service.
Refer the limitations outlined in the Overview section before using this trigger.
Settings
The Settings tab has the following fields.
Field Description
Connection Name of the TIBCO Cloud Messaging connection that you want to use.
Input Settings
The fields that you select in this tab will be available in the input schema in the Input tab.
Field Description
Message Schema A JSON object that you want to send to TIBCO Cloud Messaging.
Input
Field Description
destination The destination for a message.
In addition to destination, the Input tab displays the elements of the schema that you entered in the Input Settings tab in a tree format. You can input the values for each element by hard coding the value or mapping the value to an element from the output schema of a previous activity in the flow. See the section on Mapper in the TIBCO Flogo® Enterprise documentation for details on how to map elements.
Loop
Refer to the section on "Using the Loop Feature in an Activity" in the TIBCO Flogo® Enterprise User's Guide for information on the Loop tab.
Retry on Error
This tab allows you to set the number of times the flow to should try to execute the activity if it encounters a retriable error (such as waiting for a server to start, intermittent connection failures, or connection timeout) during the activity execution.
Map the elements in the schema using the mapper or alternatively, enter values for the element by
manually typing the value in the mapper. See the section on "Using the Mapper" in TIBCO Flogo® Enterprise User's Guide for details on how to map elements.
Field Description
Count The number of times the flow should attempt to execute the activity.
Interval The time (in milliseconds) to wait in between each attempt to execute the activity.
TCMMessageAck
The TCMMessageAck activity notifies the TCM Message Subscriber trigger to acknowledge the message received. This activity must be used when Message Ack Mode is set to Explicit on the trigger configuration.
The TCMMessageAck activity can be used in the main flow or error handler flow. It cannot be used in a subflow.
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.
TIBCO, the TIBCO logo, the TIBCO O logo, and Flogo are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.
All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.
This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. Please see the readme.txt file for the availability of this software version on a specific operating system platform.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
This and other products of TIBCO Software Inc. may be covered by registered patents. Please refer to TIBCO's Virtual Patent Marking document (https://www.tibco.com/patents) for details.
Copyright © 2016-2020. TIBCO Software Inc. All Rights Reserved.