Overview

TIBCO Flogo® Connector for Apache Pulsar provides out-of-the-box activities and triggers to send and receive messages. You can connect to your Apache Pulsar broker by using transport layer security (TLS), JSON Web Token (JWT), or Open Authorization (OAuth2). Flogo® Connector for Apache Pulsar supports 2.6.x, 2.7.x, 2.8.x, 2.9.x, 2.10.x, and 3.0.x versions of Apache Pulsar.

Configure triggers that subscribe to messages published to a topic, including Exclusive, Shared, Failover, or KeyShared subscription types. Use activities to send messages to a topic by mapping string or JSON content, with optional compression.

Flogo Connector for Apache Pulsar supports OpenTelemetry. For more information, see the Tracing Apps by Using OpenTelemetry Collector topic of TIBCO Flogo® Enterprise documentation.

Flogo Connector for Apache Pulsar supports Flow Limit. For more information, see the Environment Variables topic of TIBCO Flogo® Enterprise documentation.

Flogo Connector for Apache Pulsar is popularly used for the following purposes:

  • To subscribe to messages produced by edge computing devices and perform transformation or analysis on them.
  • To publish messages on any broker and topic in your network based on the state of the flow. You can send the results of the flow to a topic.

Note: Do not use the Linux/x86 option to build the app in Flogo® app as Apache Pulsar works only on a 64-bit machine. Install the GNU compiler collection (GCC) compiler on the Windows machine. Generate a Windows executable pulsar app from the builder-windows-amd64.exe tool on Flogo® Enterprise that may take more time than other platforms. For information about how to use Apache Pulsar, see the Apache Pulsar documentation.