Dockerfile for TIBCO BusinessEvents
TIBCO BusinessEvents provides the Dockerfiles for creating Docker image of the TIBCO BusinessEvents application and components.
Files Location | Dockerfile | Platform | Used for Creating the Docker Image of | Associated Script File |
---|---|---|---|---|
BE_HOME/cloud/docker/bin
(For the Docker image based on software installers) |
Dockerfile | Ubuntu | TIBCO BusinessEvents application | build_app_image.sh |
Dockerfile.rhel | Red Hat Enterprise Linux | TIBCO BusinessEvents application | build_app_image.sh | |
Dockerfile.win | Microsoft Windows | TIBCO BusinessEvents application | build_app_image.bat | |
Dockerfile-rms | Ubuntu | Rule Management Server (RMS) | build_rms_image.sh | |
Dockerfile-rms.win | Microsoft Windows | Rule Management Server (RMS) | build_rms_image.bat | |
Dockerfile-teagent | Ubuntu
Note: The same Dockerfile is used on both Linux and Windows platforms, and creates a Linux container. |
TIBCO BusinessEvents Enterprise Administrator Agent | build_teagent_image.sh
build_teagent_image.bat |
|
BE_HOME/cloud/docker/frominstall
(For the Docker image based on the existing TIBCO BusinessEvents installation) |
Dockerfile_fromtar | Ubuntu | TIBCO BusinessEvents application | build_app_image.sh |
Dockerfile_fromtar.win | Microsoft Windows | TIBCO BusinessEvents application | build_app_image.bat | |
Dockerfile-rms_fromtar | Ubuntu | Rule Management Server (RMS) | build_rms_image.sh | |
Dockerfile-rms_fromtar.win | Microsoft Windows | Rule Management Server (RMS) | build_rms_image.bat | |
Dockerfile-teagent_fromtar | Ubuntu | TIBCO BusinessEvents Enterprise Administrator Agent | build_teagent_image.sh |
To use any other platform, update the Dockerfile with the platform details. For more information about Dockerfile structure, see Docker Documentation.
The following sections identify key instructions to set up key configurations for the TIBCO BusinessEvents Docker images.
Environment Variables (ENV)
ENV key value
- CDD_FILE: Path of the TIBCO BusinessEvents application or RMS CDD file.
- EAR_FILE: Path of the TIBCO BusinessEvents application or RMS EAR file.
- PU: The name of the processing unit to run. The value is provided at the runtime by the user. The default value is default.
- AS_DISCOVER_URL: Discovery URL of TIBCO ActiveSpaces.
- ENGINE_NAME: TIBCO BusinessEvents engine name. The default value is be-engine.
- LOG_LEVEL: Logging level for BusinessEvents. The default value is na.
# BusinessEvents Environment Variables ENV CDD_FILE no-default ENV PU default ENV EAR_FILE no-default ENV ENGINE_NAME be-engine ENV LOG_LEVEL na ENV AS_DISCOVER_URL self
Data Volumes (VOLUME)
VOLUME /dir1, /dir2 ...
Volumes | Dockerfiles | Description |
---|---|---|
/mnt/tibco/be/logs | Dockerfile
Dockerfile-rms |
Directory where log files are stored. |
/mnt/tibco/be/data-store | Dockerfile
Dockerfile-rms |
Directory where shared nothing data is stored. |
/opt/tibco/be/${BE_SHORT_VERSION}/rms/config/security | Dockerfile-rms | Directory which holds the RMS application’s ACL (permission configuration) and user.pwd files. |
/opt/tibco/be/${BE_SHORT_VERSION}/examples/standard/WebStudio |
Dockerfile-rms | The repository directory for BusinessEvents WebStudio where all projects are stored. |
/opt/tibco/be/${BE_SHORT_VERSION}/rms/config/notify | Dockerfile-rms | Directory where email notification configuration files are stored. |
/opt/tibco/be/${BE_SHORT_VERSION}/rms/shared | Dockerfile-rms | Directory where RMS applications exported files are stored. |
/opt/tibco/be/${BE_SHORT_VERSION}/rms/locale | Dockerfile-rms | Directory where the user locale configuration is stored. |
/mnt/tibco/be/ | Dockerfile-teagent | Directory where TIBCO BusinessEvents is stored. |
/opt/tibco/be/${BE_SHORT_VERSION}/teagent/logs/ | Dockerfile-teagent | Directory where TIBCO BusinessEvents Enterprise Administrator Agent logs are stored. |
Here, BE_SHORT_VERSION stands for the TIBCO BusinessEvents software version in the short form. For example, for TIBCO BusinessEvents version 5.6.0, the BE_SHORT_VERSION is 5.6.
Ports (EXPOSE)
EXPOSE port1 port2 ...
These ports can be mapped during Docker run.