TIBCO Cloud™ Integration - Hybrid Agent And App Life Cycle

TIBCO Cloud™ Integration tracks updates sent from Hybrid Agents to determine if they are healthy and still running. Likewise, Hybrid Agents track managed remote apps. Remote apps and agents are displayed in TIBCO Cloud Integration based on this life cycle.

The health of a Hybrid Agent is based on a regular heartbeat sent to TIBCO Cloud Integration. The heartbeat is received from metrics sent by each participating Hybrid Agent. A Hybrid Agent is considered unhealthy after TIBCO Cloud Integration misses three consecutive heartbeats. The heartbeat interval is 1 minute.

The following describes the life-cycle management between TIBCO Cloud™ Integration, TIBCO Cloud Integration - Hybrid Agent, and TIBCO BusinessWorks and TIBCO Flogo® apps:

• TIBCO Cloud Integration polls Hybrid Agents every 10 seconds to discover remote apps.
• A Hybrid Agent has two possible statuses:
  • Running - the agent is healthy.
  • Heartbeat failed - a heartbeat has not been received from this agent for 3 minutes.
• A remote app has two possible statuses:
  • Running - at least one instance of the app is healthy.
  • Stopped - all app instances have been manually stopped.

Other special cases: 

• If an app is deleted from the Kubernetes cluster, it is also removed from the Apps List page.
• If you delete an agent from the Kubernetes cluster, it remains on the Agents page. You must delete it from the User Interface.
• If you delete an agent using the Web User Interface, the agent and any apps managed by that agent no longer display.
• If you delete an agent using the Web User Interface and you have taken a backup of the deleted agent's configuration, the agent cannot be started again using the backup agent configuration. All resources associated with that agent are deleted.