When you want to run a Docker command in a new container, you use the -e flag for setting environment variables. Below you will find a list of Docker compatible environment variables that users can set during BusinessWorks Container Edition container (BWCE) deployment:
| Variable | Default values | Description |
|---|
| BW_LOGLEVEL | ERROR | Used to set a log level for the TIBCO BusinessWorks™ Container Edition application. The default value is ERROR. Supported values are:
|
| BW_ENGINE_THREADCOUNT | 8 | Used to set engine thread count for the TIBCO BusinessWorks™ Container Edition application. |
| BW_ENGINE_STEPCOUNT | -1 | Used to set engine step count for the TIBCO BusinessWorks™ Container Edition application. |
| BW_APPLICATION_JOB_FLOWLIMIT | n/a | Used to set flow limit for TIBCO BusinessWorks™ Container Edition application. |
| APP_CONFIG_PROFILE | default | Name of the application profile that is to be used from a configuration management system such as ZUUL, Spring Cloud Config etc. |
| BW_PROFILE | n/a | Used to set the name of the BusinessWorks profile from the application. |
| BW_JAVA_OPTS | n/a | Used to set Java properties that are used at run time. The properties are specified using name-value pairs and are separated by spaces.
For example,
BW_JAVA_OPTS="-Dname=value -Dname=value" |
In the AWS Fargate compute engine for Amazon ECS you can set environment variables in the Container Definition as part of your Task Definition. Below example shows how to set the loglevel to "DEBUG".
Further reading:
- A quick howto on deploying BWCE applications to AWS Fargate can be found here.
- For more info on how to use other out-of-thebox logging capabilities of BWCE, check out this blog from Jurriaan Brandsma here.
