Configuring a TIBCO BusinessWorks™ App for Execution History

When you enable the Execution History Service for an organization, it publishes, stores, and retrieves execution statistics generated by remote TIBCO BusinessWorks apps. Those remote apps must be configured to leverage the Execution History Service and to allow the Hybrid Agent to discover them. Use the following app configuration example, to configure your own TIBCO BusinessWorks Apps for Execution History.

Note: To use this feature, TIBCO BusinessWorks™ Container Edition 2.7.0 or later is required.

This app configuration example assumes the following:

You are running an app in TIBCO BusinessWorks™ Container Edition 2.7.0 or later in Docker. See Creating the TIBCO BusinessWorks™ Container Edition Base Docker Image for Linux Containers in the TIBCO BusinessWorks™ Container Edition documentation.
Your app is named timerapp.
You have configured Fluentd as specified in Pushing TIBCO BusinessWorks™ App Execution History to a Local Database.
You have a TIBCO Cloud™ Integration - Hybrid Agent configured to manage remote apps. See Downloading, Configuring, and Running the Hybrid Agent for more information.
You have a second TIBCO Cloud™ Integration - Hybrid Agent configured for Hybrid Connectivity to establish a tunnel to on-premises resources. See Downloading, Configuring, and Running the Hybrid Agent for more information.

To configure the app:

Download the TIBCO BusinessWorks™ Container Edition runtime zip file, such as bwce-runtime-2.7.0.zip, and copy it to <BWCE_HOME>/bwce/2.7/docker/resources/bwce-runtime.
Run the following command from <BWCE_HOME>/bwce/2.7/docker:
```
docker build -t bwce270hybrid .
```
Edit the Dockerfile for the app. See Creating the TIBCO BusinessWorks™ Container Edition Base Docker Image for Linux Containers in the TIBCO BusinessWorks™ Container Edition documentation.
Create an app image using the bwce270hybrid base image:
```
docker build -t bwcetimerapp .
```
Run the app image, and pass the environment variables for your Hybrid Agent and Fluentd sidecar. See Pushing TIBCO BusinessWorks™ App Execution History to a Local Database for more information on Fluentd. Use the sampleBWApplicationAutoRegd.yaml file in the Samples folder generated when you ran the connect manage command to configure your Hybrid Agent. See the configure manage section of the Hybrid Agent Command Reference page for information on the sample files.
Environment variables:
- TCI_HYBRID_FLUENTD_HOST=<Fluentd sidecar host>
- TCI_HYBRID_FLUENTD_PORT=<Fluentd sidecar port>
- ENABLE_EXECUTION_HISTORY_SERVICE=true
Once your app discovered by the Hybrid Agent, execution statistics display on the TIBCO Cloud™ Integration App Details page in the Execution History tab. See Viewing Execution History for a TIBCO BusinessWorks™ App.

Configuring a TIBCO BusinessWorks™ App for Execution History

Related Topics