TIBCO Cloud™ Integration - Hybrid Agent Requirements

Before using the Hybrid Agent, make sure you meet the following prerequisites:

• Ensure the on-premises machine or Cloud environment that runs the TIBCO Cloud Integration - Hybrid Agent meets the system requirements as described in System Requirements.
• You may need to whitelist IP addresses to allow traffic from TIBCO Cloud Integration. See Whitelisting Requirements for TIBCO Cloud™ Integration Apps for more information.
• To enable both remote app management and Hybrid Connectivity to on-premises resources, configure a dedicated agent for each one. These agents can run on the same machine.
  Note: You can run only one agent to manage remote apps. For Hybrid Connectivity, you can run more than one instance of an agent for Fault Tolerance, where one instances is always the primary.

Remote App Management

• A Hybrid Agent used to manage or monitor remote apps must be installed in a Kubernetes environment. The apps managed by the agent must be in the same Kubernetes namespace as the agent.
• The kubectl command line tool for Kubernetes must be installed when configuring a Hybrid Agent to manage remote apps.

Hybrid Connectivity

• The TIBCO Cloud Integration - Hybrid Agent should be co-located in the same data center network as the on-premises resources you intend to connect to from TIBCO Cloud Integration.
• To use the log streaming feature, install the socat utility on the machine running the TIBCO Cloud Integration - Hybrid Agent.
• Log streaming is not supported on Microsoft Windows.
• Agents used to set up a tunnel to on-premises applications are not limited to Kubernetes.

HTTP Proxy Configuration

If you are running the TIBCO Cloud Integration - Hybrid Agent behind an HTTP or HTTPS proxy, you must set the environment variable HTTP_PROXY or HTTPS_PROXY to the hostname or IP address of the proxy server before running the TIBCO Cloud Integration - Hybrid Agent.

For Linux and macOS:

export HTTP_PROXY=http://http_proxy:port/

or

export HTTPS_PROXY=https://http_proxy:port/

For Windows:

set HTTP_PROXY=http://http_proxy:port/

Or

set HTTPS_PROXY=https://http_proxy:port/