Container Management
The Docker containers that contain TIBCO BPM Enterprise are managed by a Container Orchestration System -- Kubernetes.
Some of the ways in which Kubernetes is used to manage TIBCO BPM Enterprise containers includes the following:
- Adding and removing pods from Kubernetes nodes. Replica Sets of pods across nodes can be created to scale TIBCO BPM Enterprise.
- Deploying Docker containers, containing TIBCO BPM Enterprise, to pods. As TIBCO BPM Enterprise only has a single container type, each pod will contain only a single container and the associated resources (database shared resources, IP address, and so on) required by TIBCO BPM Enterprise.
- Start up and shut down of Docker containers containing TIBCO BPM Enterprise.
- Basic health monitoring. This is accomplished using Kubernetes cAdvisor, which monitors container metrics, as well as application metrics.
- Configuration injection. TIBCO BPM Enterprise configuration is injected into the container on startup. Some of this configuration is written to the database to ensure consistency across all containers.
The following illustrates how TIBCO BPM Enterprise is deployed in Kubernetes.
Pods are created and deployed in Kubernetes nodes. Each pod contains a single TIBCO BPM Enterprise container. Additional pods can be added to a node to scale the system. The system can also be scaled by creating a replica set across multiple Kubernetes nodes.
There is a single TIBCO BPM Enterprise service per node, which exposes the product REST API.
For additional information, see TIBCO BPM Enterprise Administration.