ibi MDM on Container Platforms
You can containerize ibi™ MDM (formerly TIBCO® MDM) and run it in a Docker or Kubernetes environment. To containerize ibi MDM, you must build and run the Docker images using the Dockerfiles bundled in TIB_mdm_10.0.0_container.zip.
The Dockerfiles are delivered as a ZIP file on the
TIBCO eDelivery website. Download the
TIB_mdm_10.0.0_container.zip file and extract its content to a separate directory named as docker. In the docker directory, locate the ready-to-use Dockerfile and other scripts required to build the images. You can build images using the Dockerfiles, and then run them as containers. For information about building images, see
Building and Running Docker Image for the ibi MDM All-in-one Container and Build Docker Image for ibi MDM Cluster Container.
To run an application, you require the application, all its dependencies, and configuration files. A container provides an OS environment to hold together all supporting components and tools that are required to run the application. This provides a consistent environment without the overhead of OS dependencies and other infrastructural requirements. For information about Docker concepts, such as, Dockerfile, Docker Image, and Container, see Docker documentation.
To save (persist) data and also to share data between containers, Docker volumes are used. Docker volumes are file systems mounted on Docker containers to persist or retain data generated by the running container.
The ibi MDM containers are available in the following modes:
Additionally, ibi MDM supports a high-level CRI-O container runtime that offers a lightweight alternative to Docker. CRI-O is an open-source implementation of Kubernetes’ container runtime interface (CRI). With the support of Open Container Initiative (OCI), you can now select different container runtimes (for example, CRI-O) instead of Docker, which conform to the specification.