Enterprise Message Server (EMS) version 10.3 can run with a variety of persistent storage options.
This document will outline running EMS with persisted file storage in Kubernetes environments.
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 document only covers EMS utilizing a shared file system for storage.
Running TIBCO Enterprise Message Service on different Kubernetes Container Platforms with
persisted file storage involves:
● Creating a Docker® image embedding EMS and hosting it in a Docker registry
● Preparing a shared folder on NFS for on premise storage configurations, if required
● Provisioning Persisted volume storage for cloud platforms, if required
● Configuring and creating EMS containers based on the EMS Docker image to run in
Kubernetes
● EMS is now deployed in Kubernetes via Helm
How_to_Configure_EMS_10.3_on_Kubernetes_files.pdf ems_10.3_files_kubernetes.zip
-
2
-
1
Recommended Comments
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now