...

This purpose differs from that of an HTTP proxy, which might be required for outbound requests from the Snaplex to the Control Plane or other endpoints. (Typically, the HTTP proxy is required when Groundplex nodes are on client servers with a restricted network configuration.)

...

• For Triggered Tasks, you only need to configure the Load balancer field.

• If a load balancer points to a FeedMaster node, then you only need to configure the Ultra load balancer field.

• If the load balancer points to worker nodes, then you should only configure the Load balancer field in the Snaplex Settings tab.

• The full URL of the load balancer needs to be configured in the Snaplex properties.
  For example, “https“https://mylb.mydomain.com:443”443”.

Use Cases where a Load Balancer is Not Required

...

On a Cloudplex, a load balancer is provisioned by SnapLogic, typically only when the Ultra subscription feature is enabled. The Cloudplex load balancer has a snaplogic.io domain endpoint that points to the FeedMaster nodes. You can use a load balancer for both Ultra and Snaplex-triggered Pipeline runsPipelines.

As an Org admin, you must update the Snaplex settings with the load balancer URL after the load balancer is provisioned.

...

• For a Snaplex with FeedMaster nodes, the load balancer should point to these FeedMaster nodes:

  • https://fm-node1.example.com:8084

  • https://fm-node2.example.com:8084

A FeedMaster node can process Triggered and Ultra Tasks, but a JCC node can only process Triggered Tasks. You can use the FeedMaster node as the load balancer endpoint for a Triggered Task. For an Ultra Task, you need to update the load balancer field value in the Snaplex Settings dialog.

• If your Snaplex does not contain FeedMaster nodes, the load balancer can point to these JCC nodes:

  • https://jcc-node1.example.com:8081

  • https://jcc-node2.example.com:8081.

For Triggered Tasks and Always-On Ultra Tasks, you need to update the Load balancer field value in the Snaplex settings.

...