How to Configure TIBCO Enterprise Messaging Service 10.3 with FTL Stores in a Kubernetes Container Platform Environment

With current versions of TIBCO Enterprise Message Service (EMS 10.x), TIBCO FTL can be used as the backing stores for EMS.

FTL stores have a somewhat unique configuration and deployment model in comparison to other EMS storage types. When using FTL stores, the EMS server runs as a service within an FTL server – which is an umbrella process that launches and manages a number of messaging services that constitute a TIBCO FTL deployment. The integration of EMS with FTL in this manner reduces latency in communication between the EMS server and its FTL backend. Additionally, it also allows EMS to make use of FTL’s disaster recovery capabilities.

In terms of functionality, FTL stores are similar to file-based stores. When using FTL stores, all pending persistent message data and state information is maintained in the FTL server cluster. 

TIBCO FTL offers the ability to provide disaster recovery which ensures realm availability and protects persist data. With EMS 10.3, the disaster recovery mechanism is part of the EMS functionality, and can be triggered via tibemsadmin/tibftladmin.

Note: Though the deployment of EMS is in FTL, no previous knowledge of FTL is required. See the TIBCO Enterprise Message Service v10.3 documentation for additional details.

Additionally, Enterprise Message Service (EMS) now supports authentication of client connections via OAuth 2.0. 

EMS clients require an access token to connect to an EMS server configured with OAuth 2.0 authentication. Additionally, an EMS server itself may require an access token to connect to another EMS server or a TIBCO messaging product that is configured for OAuth 2.0 authentication. 

This document has been updated to provide details for using OAUTH 2.0 in EMS on Kubernetes Container platforms.

Note: The use of OAuth2 can only be used with EMS. FTL OAuth2 authentication is not supported in EMS configurations. 

This document will provide the steps necessary to build and test an EMS environment utilizing FTL as the backing store for both TCP and TLS configurations.

Other changes in this update include:

• The use of AlmaLinux9 as the container OS. RedHat 9, or a binary equivalent can still be used
• Both EMS and FTL now run as part of a non-root user account (tibuser)
• EMS hot fixes can be included in the Docker build
• One Docker build now supports standard,  OAuth2, and TLS configurations
• Helm charts are used for all deployments into the container platform environment

Configuring and running the TIBCO EMS utilizing FTL involves:

• Creating a Docker® image embedding FTL and EMS, and hosting it in a Docker registry
• Provisioning Persisted volume storage for cloud platforms
• Configuring and creating FTL/EMS containers based on the EMS Docker image to run in Kubernetes through pre-configured yaml configuration files via Helm charts.

ems_10.3_ftl_kubernetes.zip

How to Configure EMS 10.3 with FTL on Kubernetes.pdf