TIBCO EBX® Container Edition image is Linux based and includes the following:
Application Server Apache Tomcat® 9.0
Java JDK 17
The image can be built on a POSIX native system or using a compatible layer:
Operating system : Linux, macOS, Windows (10 version 2004, Server 2022 or greater) using WSL2,
Processor type : Intel or AMD 64 bits,
Docker Engine installed and running,
Access to Internet .
To build an EBX® image, one needs to download file TIB_ebx_6.1.2_addon_6.1.X_container_edition.zip from TIBCO eDelivery.
To start installer on Linux or macOS :
Unzip the TIB_ebx_6.1.2_addon_6.1.X_container_edition.zip ,
Open a terminal in folder where file ebx-ce-installer.sh file is located,
Execute command ./ebx-ce-installer.sh .
To start installer on Windows :
Unzip the TIB_ebx_6.1.2_addon_6.1.X_container_edition.zip ,
Open a Windows PowerShell in folder where file ebx-ce-installer.bat file is located,
Execute command ebx-ce-installer.bat .
Follow instructions and select addons to be added to the image.
The installer will then build the image and print a summary similar to:
********************************************************************************************** The TIBCO EBX Container Edition image was successfully created with following names: ebx:latest ebx:6.1.2-dama-dint-dmdv-dpra-mame-tese-6.1.X This image includes the following addon(s): Digital Asset Manager (DAMA) Data Exchange (New) (DINT) Data Model and Data Visualization (DMDV) Insight (New) (DPRA) Match and Merge (MAME) Information Search (TESE) To run this image with the default configuration and an embedded database, use command: docker run -p 8080:8080 -d ebx:latest You can test EBX by visiting http://localhost:8080 in a browser. To run this image with other configurations, for example with an external database, see documentation. **********************************************************************************************
To start batch installer on Linux or macOS :
Unzip the TIB_ebx_6.1.2_addon_6.1.X_container_edition.zip ,
Open a terminal in folder where file ebx-ce-installer-batch.sh file is located,
Execute command ./ebx-ce-installer-batch.sh [OPTION]… [addon]…
Batch script to build image with optionally addon(s). -a add all addons -t <tag_file> create a file named tag_file including the image tag built --help display this help and exit [addon]... add specific addons (separate by a space) for sample: mame tese
To start batch installer on Windows :
Unzip the TIB_ebx_6.1.2_addon_6.1.X_container_edition.zip ,
Open a Windows PowerShell in folder where file ebx-ce-installer-batch.bat file is located,
Execute command ebx-ce-installer-batch.bat [OPTION]… [addon]…
The batch installer will then build the image and print a summary identical to the interactive installer.
The image can be run locally using command:
docker run -p 8080:8080 -d ebx:latest
In production , it is recommended to not use tag latest . The installer will always generate another tag depending on selected addons.
If previous sample, the tag is 6.1.2-dama-dint-dmdv-dpra-mame-tese-6.1.X because the following addons where selected:
Digital Asset Manager (DAMA),
Data Exchange (New) (DINT),
Data Model and Data Visualization (DMDV),
Insight (New) (DPRA),
Match and Merge (MAME),
Information Search (TESE).
The image can then be run using command:
docker run -p 8080:8080 -d ebx:6.1.2-dama-dint-dmdv-dpra-mame-tese-6.1.X
If no addons are selected, the tag is 6.1.2
The image can be run using command:
docker run -p 8080:8080 -d ebx:6.1.2
The steps to share an image depends on customer’s company infrastructure.
In following example, the image is pushed to a Docker private registry named myregistry :
docker tag ebx:6.1.2 myregistry:5000/ebx:6.1.2 docker push myregistry:5000/ebx:6.1.2
The installers are tested on Intel or AMD 64 bits systems. On these platforms the generated image’s architecture will be linux/amd64 .
The installers may succeed when running on a system using another processor. In that case the generated image architecture will be linux for that processor type.
For example, if the installer runs on a MacOS M1 workstation, the generated image’s architecture will be linux/arm64 .
Attention
Generating an image on a system that is not Intel or AMD is experimental and is not supported in production .