Enabling Execution History for TIBCO BusinessWorks™ Apps Running On-premises

Use the TIBCO Cloud™ Integration Execution History service to publish, store, and retrieve execution statistics generated by TIBCO BusinessWorks apps running on-premises. TIBCO Cloud™ Integration stores Execution History data generated by an on-premises app in a local database that you configure and displays it on the Execution History tab of the App Details page for a specific app.

Enabling Execution History must be done in a series of distinct steps as follows:

Configure a local database to store app execution data, as described in Configuring a Database for On-premises TIBCO BusinessWorks™ App Execution History.
Configure Fluentd to push app Execution History to the local database, as described in Pushing TIBCO BusinessWorks™ App Execution History to a Local Database.
Configure and start a Hybrid Agent to manage remote apps as described in Downloading, Configuring, and Running the Hybrid Agent. This agent handles displaying remote apps in the User Interface allowing you to access Apps Details and Execution History for those apps
Configure and start a Hybrid Agent for Hybrid Connectivity as described in Downloading, Configuring, and Running the Hybrid Agent. This agent handles the connection to the database for Execution History. Use the --spec argument when starting the agent to pass one or more connection specs, such as the port and IP address of the local database you configured in the first step. For example:
```
tibagent start agent --spec 3306:10.97.170.85:3306 <agentname>
```
Where 10.97.170.85 is the database host IP address.
Note: If you are using Oracle Database to store app execution data, provide the IP address and port of the local BWCE Mon in the --spec command.
Note: To use the Execution History service, you must download the latest Hybrid Agent from the TIBCO Cloud™ Integration User Interface. Using an Agent downloaded before the January 2022 release of TIBCO Cloud™ Integration generates a Connect file not found error when starting the Agent.
Note: A single Hybrid Agent configured without a custom access key can be used for multiple services, such as the Execution History, Flow tester, or DB services. If a Hybrid Agent is configured with your access key to establish a tunnel connection to your on-premises resources, you must configure a separate agent for each service.
Enable the Execution History service using the TIBCO Cloud™ Integration API, as described in Enabling the Execution History Service for an Organization with the API.
Configure a TIBCO BusinessWorks App, as described in Configuring a TIBCO BusinessWorks™ App for Execution History.
View the Execution History for an app, as described in Viewing Execution History for a TIBCO BusinessWorks™ App.

Enabling Execution History for TIBCO BusinessWorks™ Apps Running On-premises

Related Topics