Enabling Execution History for Apps

Use the TIBCO Cloud™ Integration Execution History service to publish, store, and retrieve execution statistics generated by apps.

Execution History data generated by a app can be stored in an on-premises database or a database hosted on the cloud. TIBCO Cloud Integration displays the Execution History data on the Execution History tab of the App Details page for a specific app.

To enable Execution History for apps

  1. Configure the PostgreSQL database to store app execution data.
    Note: Only the PostgreSQL database is supported when storing execution history data.
  2. (For an on-premises database only) Configure and start the Hybrid Agent for Hybrid Connectivity as described in Downloading, Configuring, and Running the Hybrid Agent. Use the --spec command when you start the agent to pass one or more connection specs, such as the port and IP address of the on-premises database you configured in the first step. For example: 
    tibagent start agent --spec <port>:<IP address>:<port> <agentname>

    Where <IP address> is the IP address of the database host and <port> is where the userdb is listening for client connections.

    For example:

    tibagent start agent --spec 3306:10.97.170.85:3306 tibagent1
    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 May 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 hybrid connectivity to your on-premises resources, you must configure a separate agent for each service.
  3. 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.
  4. Configure a app for Execution History, as described in Configuring a Flogo App for Execution History.
  5. View the Execution History for an app, as described in Viewing Execution History for a Flogo App.