Before You Begin

You can containerize a TIBCO BusinessEvents application by using OCI compatible container build tools docker or buildah. You can also run the containerized TIBCO BusinessEvents application on various cloud environments, but not limited to:

• Kubernetes cluster on a cloud platform of your choice
• Multihost clustering on Amazon EC2 using Weave Net and Docker
• Cloud Foundry based VMware Tanzu Application Service

Concepts

Before you begin, you must be familiar with the following concepts and services:

• Docker concepts if you want to build BE container image using Docker
• Buildah concepts if you want to build BE container image using buildah
• Podman concepts if you want to run BE container image using Podman on a Linux machine
• Kubernetes concepts if you want to deploy BE container image using kubernetes.
• Administration knowledge of the cloud platform and the service that you want to use:
  • Amazon Web Services (AWS)
  • Microsoft Azure and Azure Kubernetes Service (AKS)
  • Red Hat OpenShift Container Platform
  • Google Cloud Platform (GCP) and Pivotal Container Service (PKS)
  • Oracle Cloud Infrastructure (OCI)
• Cloud Foundry based VMware Tanzu Application Service for VMs concepts (TAS for VMs) if you want to run BE container image on TAS

Preparing for TIBCO BusinessEvents Containerization

Ensure that you have the following infrastructure in place:

• TIBCO BusinessEvents installation and a TIBCO BusinessEvents project that you want to deploy and run on the cloud. For installation instructions, see the TIBCO BusinessEvents Installation Guide at TIBCO BusinessEvents Documentation.

• Clone or download the cloud folder from the TIBCO BusinessEvents GitHub repository to your system. You can download the cloud folder to any location on your system. The cloud folder contains utilities to deploy and monitor your TIBCO BusinessEvents applications on different cloud platforms.

  Note: When building image from local installation, it is assumed that the cloud folder from GitHub is downloaded at BE_HOME and merged with the existing BE_HOME/cloud folder.

• When building image using installers, Copy the necessary installer ZIP files to a directory where the build scripts can reference from (i.e. /home/tibco/installers). You will need the following software installers:

  • TIBCO BusinessEvents
  • TIBCO BusinessEvents add-ons (Optional)
  • TIBCO ActiveSpaces (Optional)
  • TIBCO FTL (Optional)
  • TIBCO OIHR (Optional)

  Note: You do not need to unzip the installers.

  For more details, see the Optional Software Requirements section in TIBCO BusinessEvents Installation Guide at TIBCO BusinessEvents Documentation
  

  Note (macOS only):
  On the macOS platform, you can build only Linux containers. To build a Container image on macOS, you must store the TIBCO BusinessEvents Linux installer ZIP file (TIB_businessevents-enterprise_<version>_linux26gl25_x86_64.zip) on your computer instead of the macOS installer ZIP file. Similarly, if your application uses TIBCO BusinessEvents add-ons (OR) TIBCO ActiveSpaces (OR) TIBCO FTL (OR) TIBCO OIHR, download respective Linux installers on your computer.

• When building image from local installation, build script looks for FTL_HOME, ACTIVESPACES_HOME, AS_HOME & HAWK_HOME in the be-engine.tra, If they are defined with valid paths, respective artifacts are copied into the image. If you want to include/exclude any of them in the docker image make sure the path is updated/emptied properly for the respective field. In case of rms image, scripts will check for home path from be-rms.tra.

• (Optional) For monitoring TIBCO BusinessEvents applications, install TIBCO Enterprise Administrator with the latest hotfix. For installation instructions, see TIBCO Enterprise Administrator documentation.

• If you are running the application in a Kubernetes cluster on a cloud platform, ensure that you have an active account on that cloud platform.