Skip to content

Containerize TIBCO BusinessEvents

Jump to bottom
nthota edited this page Apr 26, 2021 · 10 revisions

Using the scripts provided at the TIBCO BusinessEvents GitHub repository, you can containerize TIBCO BusinessEvents application by using docker or buildah tool.

A TIBCO BusinessEvents application comprises a common TIBCO BusinessEvents runtime and project (application) specific TIBCO BusinessEvents code running inside the TIBCO BusinessEvents runtime. Thus to containerize a TIBCO BusinessEvents application, TIBCO BusinessEvents software archive and application archive are included in the Container image.

Scripts with BusinessEvents

TIBCO BusinessEvents provides the build_image script for building images of TIBCO BusinessEvents application and its components at BE_HOME\cloud\docker. Use the --image-type as below for the respective images:

  • app - To build the Container image for your TIBCO BusinessEvents application.
  • s2ibuilder - To build the S2i Container image for your TIBCO BusinessEvents application.
  • rms - To build the Container image for RMS.
  • teagent - To build the Container image for TIBCO BusinessEvents Enterprise Administrator Agent.

build_image script uses the platform-specific Dockerfiles bundled with TIBCO BusinessEvents at BE_HOME\cloud\docker\dockerfiles. For details about Dockerfiles provided with TIBCO BusinessEvents, see Dockerfiles for TIBCO BusinessEvents.

Usage: build_image.sh

 [-i/--image-type]    :    Type of the image to build ("app"|"rms"|"teagent"|"s2ibuilder") [required]
                           Note: For s2ibuilder image usage refer to be-tools wiki.

 [-a/--app-location]  :    Path to BE application where cdd, ear & optional supporting jars are present
                           Note: Required if --image-type is "app"
                                 Optional if --image-type is "rms"
                                 Ignored  if --image-type is "teagent" or "s2ibuilder"

 [-s/--source]        :    Path to BE_HOME or TIBCO installers (BusinessEvents, Activespaces or FTL) are present (default "../../")

 [-t/--tag]           :    Name and optionally a tag in the 'name:tag' format [optional]

 [-d/--docker-file]   :    Dockerfile to be used for generating image [optional]

 [--gv-provider]      :    Name of GV provider to be included in the image ("consul"|"http"|"custom") [optional]
                           To add more than one GV use comma separated format ex: "consul,http" 
                           Note: This flag is ignored if --image-type is "teagent"

 [--disable-tests]    :    Disables docker unit tests on created image (applicable only for "app" and "s2ibuilder" image types) [optional]

 [-b/--build-tool]    :    Build tool to be used ("docker"|"buildah") (default is "docker")
                           Note: s2ibuilder image and docker unit tests not supported for buildah.

 [-h/--help]          :    Print the usage of script [optional]

 NOTE : supply long options with '='

Note for the Windows platform:

  • Use build_image.bat script and enclose all arguments in double quotes (")
  • Flags disable-tests and build-tool not applicable in windows environment.
  • If you are building from a Windows machine behind a firewall, you may see error like - "Unable to connect to the remote server". In such case you need to configure your firewall to allow all traffic on the nat virtual adapter which is only used by containers

Containerizing TIBCO BusinessEvents Application and Components

To Containerize TIBCO BusinessEvents components, see the following topics:

Clone this wiki locally