TIBCO Fulfillment Catalog as a Container on Kubernetes

TIBCO Fulfillment Catalog can be deployed as a container application. To containerize the application, you must build and run the Docker images using the bundled Dockerfile. The deployment architecture and the detailed instructions in this guide are written in context to Google Kubernetes as it has been used to create and orchestrate docker containers for the components of TIBCO Fulfillment Catalog. Hereafter, Google Kubernetes is referred to as Kubernetes. Deployment uses Kubernetes concepts such as, deployment, pod, kubctl, kubernetes master, and service. For more details, see Kubernetes documentation.

Building Docker Images

Preparation for the deployment starts with building Docker images using the Docker files. Download the Docker .zip file from the same link where TIBCO Fulfillment Catalog product package was downloaded and extract it to a separate directory. The directory contains a subdirectory with the ready-to-use Dockerfile and other scripts required to build the images. The subdirectories and their purpose is as follows:
  • fcbase: This directory contains Dockerfile and Readme used to build the base image. This base image is then used to build other images such as fc_single_container, fc_multi_container, and fc_ignite_base. You must build the fcbase image before building other images.
  • fc_base_ignite: This directory contains the Dockerfile and Readme used to build the docker image. This is the base image used to build the ignite image. This image must be built before the fc-ignite image.
  • fcdb: This directory contains Dockerfile, Readme, helper scripts, and a sample deployment json. This image is PostgreSQL database for TIBCO Fulfillment Catalog.
  • fc_ignite: This directory contains Dockerfile, Readme, and other helper scripts used to build an ignite cache.
  • fc_single_container: This directory contains Dockerfile, Readme, and other helper scripts used to build a single host, single pod image. This container also contains components such as PostgreSQL (database), activemq (messaging server), and ActiveSpaces.
  • fc_multi_container: This directory contains Dockerfile, Readme, helper scripts, and a sample deployment json used to build a TIBCO Fulfillment Catalog server image. This image is for an independent TIBCO Fulfillment Catalog application that can be used with a separate Oracle or PostgreSQL database, depending on how the image is built.
  • fc_opd: This is the docker image for the TIBCO Fulfillment Catalog-Offer and Price Designer. This directory contains Dockerfile, Readme, and other helper scripts used to build an offer and pricing designer.

Detailed instructions on how to use the Docker file and build the image are provided in the respective Docker file and the Readme. After creating the Docker files you must push them in the Docker registry so that they can be accessed by Kubernetes deployment.

Note: You must select the Docker files based on the type of deployment and combination of database and messaging software being used.
The following topologies are available for deployment:
  • Single Pod Deployment:The components of TIBCO Fulfillment Catalog server run in a single container inside a single pod. For example, TIBCO Fulfillment Catalog app server, PostgreSQL database, TIBCO ActiveSpace, and Apache ActiveMQ messaging.
  • Multi-Pod Deployment:The components of TIBCO Fulfillment Catalog run in separate containers in separate pods allowing a cluster kind of deployment to achieve high-availability and scalability at different levels. Multiple pods are involved, which continue working when one of the pod instances crashes.