TIBCO Flogo® Connector for TIBCO Enterprise Message Service™
TIBCO Flogo® Connector for TIBCO Enterprise Message Service™ (EMS) provides activities and triggers to send and receive messages. You can connect to your EMS broker by using transport layer security (TLS).
Configure triggers that subscribe to messages published to a queue and topic.
Flogo® Connector for TIBCO EMS supports OpenTelemetry. For more information, see OpenTelemetry Collector.
Flogo Connector for TIBCO EMS does not support JNDI lookups for administered objects (such as destinations or connection factories) that are hosted on an LDAP server.
- Do not use the Linux/x86 option to build the app in Flogo® app as EMS works only on a 64-bit machine. Install the GNU Compiler Collection (GCC) compiler on the Windows machine. Generate a Windows executable EMS app from the
builder-windows-amd64.exetool on TIBCO Flogo® that may take more time than other platforms. For information about how to use EMS, see the EMS documentation. - When using Flogo® App Build Command Line Interface (CLI) to create app builds for deployment on TIBCO Control Plane, it is recommended to use a custom application image. For more information, see Deploying a Flogo App using Custom Application Image. The standard CLI build does not include all required dependencies. Providing a fully qualified custom image ensures all dependencies are packaged in the Docker image so the app runs correctly on TIBCO Control Plane.
-
Alpine Linux is not supported as a runtime environment for TIBCO EMS due to compatibility issues between musl libc (used by Alpine) and the glibc-dependent libraries required by TIBCO EMS. For Docker deployment, use a glibc-based base image such as Debian or Ubuntu for successful runtime.
Before designing, testing, or running a Flogo app with this connector in Visual Studio Code, ensure that you install the prerequisites required at design time. For more information, see Prerequisites for Connectors.