Requirements for different agent transport protocols for a third-party load-balancing solution:
Agents connecting via HTTP/HTTPs Protocol transport
- The load balancer must ensure that agent HTTP requests are balanced to the Cloud Proxy instance based on the HTTP JSESSIONID session cookie. The Cloud Proxy instance keeps a WebSocket channel to APM Gateway associated with the HTTP session of the agent.
Agents connecting via WebSocket protocol transport
- Agent WebSocket transport creates a stable TCP socket connection. The third-party solution must support the WebSocket protocol.
Agents connecting via Isengard protocol
- The Isengard protocol is transferred directly through a TCP socket connection. A network load balancer or similar technique can be used to ensure failover to an available Cloud Proxy instance.
The proxy target URL and Token are preconfigured when the Download Cloud Proxy feature is executed in the GUI.
The agent token that is used to authenticate communication between Cloud Proxy and Cloud Gateway. You can generate the token from Team Center