Pushing TIBCO BusinessWorks™ App Execution History to a Local Database

When you enable the Execution History Service for an organization, the data generated by apps configured for that service must be sent to a local database to make it available for display later. You can configure Fluentd to run as a sidecar container with an on-premises TIBCO BusinessWorks App to push the app execution data to your database.

The Fluentd configuration varies based on the database you chose. For the list of supported databases see, Configuring a Database for On-premises TIBCO BusinessWorks™ App Execution History. The following Fluentd configuration files for each database are available for download from our GitHub repository at: https://github.com/TIBCOSoftware/bw-tooling/tree/master/fluentd.

Note: If you are using Oracle Database with enhanced limits, see Using Oracle Database with Increased Column Limits.

fluentd.conf- Contains the database details. Edit the fluentd.conf content at /etc/fluent/fluent.conf with the details for the selected database.
Dockerfile - Required to create the Fluentd Docker Image based on the fluentd.conf configuration file.
Example:
```
docker build -t fluent:mysql .
```
Once you have the Fluentd Docker Image created, you can start the Fluentd container.
Example:
```
docker run --rm -p 24224:24224 -e FLUENTD_CONF=fluentd.conf --name fluent_mysql fluent:mysql
```

Pushing TIBCO BusinessWorks™ App Execution History to a Local Database

Related Topics