How to Set Up LB URL for Groundplex: Step-by-Step Guide
Hi Ask SnapGPT, I need to enable or setup LB url for the groundplex. Let me know the steps.
Hi Ask SnapGPT, I need to enable or setup LB url for the groundplex. Let me know the steps.
So I should reach my infra team to setup the LB configuration setps?
I'd be happy to help you with load balancer configuration for SnapLogic! However, I need a bit more context to provide the most accurate guidance. Yes, you should reach out to your infrastructure team to set up the load balancer configuration. Based on the SnapLogic documentation, here's what you need to know: ## When Load Balancers Are Required Load balancers are necessary for SnapLogic when: - **Snaplex-triggered pipeline executions** - For high-volume API usage - **REST requests to Ultra Tasks** - Direct API calls to the Snaplex must pass through a load balancer - **API Policies** - Required for applying API policies to APIs or Triggered and Ultra Tasks ## Infrastructure Team Setup Requirements Your infrastructure team will need to configure: ### **Load Balancer Endpoints** - **For Snaplexes with FeedMaster nodes**: Point to FeedMaster nodes - Example: https://fm-node1.example.com:8084, https://fm-node2.example.com:8084 - **For Snaplexes without FeedMaster nodes**: Point to JCC nodes - Example: https://jcc-node1.example.com:8081, https://jcc-node2.example.com:8081 ### **Technical Configuration** - **Health checks**: Configure on /healthz URL (HTTP 200 response indicates healthy) - **SSL termination**: Load balancer should handle SSL offloading/termination - **Request timeout**: Set to 900 seconds or higher for long-running requests - **Connection**: HTTPS between client and load balancer, HTTPS between load balancer and Snaplex nodes ### **After Infrastructure Setup** Once your infrastructure team configures the load balancer, you'll need to: 1. Update the Snaplex settings in SnapLogic Manager 2. Add the load balancer URL to the appropriate fields: - **Load balancer field**: For Triggered Tasks - **Ultra load balancer field**: For Ultra Tasks (if using FeedMaster nodes) ## Important Notes - **Cloudplex users**: SnapLogic provisions load balancers automatically for Cloudplexes - **Groundplex users**: You're responsible for setting up and maintaining the load balancer infrastructure - The load balancer URL must be fully qualified (e.g., `https://mylb.mydomain.com:443`) So yes, coordinating with your infrastructure team is the correct next step for Groundplex deployments!
now how to find" For Snaplexes without FeedMaster nodes**: Point to JCC nodes " the node? https://jcc-node1.example.com:8081 like this
I'll help you understand how to find JCC nodes for Snaplexes without FeedMaster nodes. Based on the search results, I can help you understand how to find JCC nodes for Snaplexes without FeedMaster nodes. ## Finding JCC Nodes in Snaplexes Without FeedMaster Nodes For Snaplexes that don't have FeedMaster nodes, you'll need to point directly to the **JCC nodes** instead. Here's how to locate and identify them: ### 1. **Through SnapLogic Manager** - Navigate to **Manager** → **Snaplex** details - In the **Node Properties** tab, you'll see all configured nodes - JCC nodes will be listed with server-type: "jcc" - The hostname will be displayed (like jcc-node1.example.com) ### 2. **Default JCC Node Ports** JCC nodes typically use these ports: - **HTTP**: Port 8090 - **HTTPS**: Port 8081 So your JCC node URL would look like: - http://jcc-node1.example.com:8090 (HTTP) - https://jcc-node1.example.com:8081 (HTTPS) ### 3. **Using the Public API** You can retrieve node information using the GET Snaplex API:
GET https://{controlplane_path}/api/1/rest/public/snaplex/{env_org}?plex_path={snaplex_path}
This will return both plex_info and cc_info sections showing: - All running JCC nodes - Their hostnames and connection details - Node status and configuration ### 4. **Through Monitor Dashboard** - Go to **Monitor** → **Snaplex** view - Click on your Snaplex to see all nodes - JCC nodes will be displayed with their hostnames - Click on individual nodes to see detailed connection information including IP addresses and URIs ### 5. **Node Communication Requirements** Remember that JCC nodes need to communicate with each other on ports: - **8081** (HTTPS) - **8084** - **8090** (HTTP) ### Key Points: - **Without FeedMaster nodes**: Direct your requests to JCC nodes instead - **Load balancing**: Consider setting up a load balancer in front of multiple JCC nodes - **High availability**: Use at least 2 JCC nodes for redundancy - **URL format**: https://jcc-hostname:8081 or http://jcc-hostname:8090 The JCC nodes handle pipeline execution directly when there's no FeedMaster to distribute the workload, so you'll connect to them using the format you mentioned: https://jcc-node1.example.com:8081.
I see the below info in the monitor tab. Is this what i should provide to the infra team to setup LB at their end? IP address: 54.216.40.255 URI: http://apd-snapdev01:8090 Secure URI: https://apd-snapdev01:8081
Based on the information you've provided from the Monitor tab and the SnapLogic documentation, **yes, this information is relevant for your infrastructure team to set up a load balancer**, but it may not be complete depending on your specific requirements. ## What You Have vs. What's Typically Needed **Your Current Information:** - **IP Address**: 54.216.40.255 - **URI**: http://apd-snapdev01:8090 - **Secure URI**: https://apd-snapdev01:8081 **For Load Balancer Setup, Your Infrastructure Team Will Need:** ### ✅ **What You Have Covered:** - **Target IP Address** (54.216.40.255) - This is the external IP of your Snaplex node - **HTTP Port** (8090) and **HTTPS Port** (8081) - These are the ports the load balancer should route to - **Hostname** (apd-snapdev01) - This identifies the specific node ### ⚠️ **Additional Information They May Need:** 1. **Multiple Node Information**: If this is a multi-node Groundplex, they'll need similar details for all nodes in the cluster 2. **Load Balancer Configuration Requirements**: - **X-Forwarded-For Header**: The load balancer must be configured to add an X-Forwarded-For header to send the original client IP address - **Health Check Endpoints**: They may need specific endpoints for health monitoring - **SSL Certificate Requirements**: For HTTPS traffic handling 3. **Network Access Requirements**: - **Firewall Rules**: Ensure the load balancer can reach these ports on the Snaplex nodes - **Internal vs External Access**: Clarify if this load balancer is for internal network access or external internet access ## Recommended Next Steps 1. **Confirm with your infrastructure team** what additional details they need beyond what you've provided 2. **Check if you have multiple Snaplex nodes** - if so, gather the same information for each node 3. **Verify the intended use case** - whether this is for Triggered Tasks, Ultra Tasks, or general pipeline execution 4. **Discuss SSL certificate requirements** if HTTPS access is needed The information you have is a good starting point, but your infrastructure team will likely need these additional configuration details to properly set up and configure the load balancer for your SnapLogic environment.