...
Point the cursor and click the target Snaplex to open the Update Snaplex dialog.
Click the Node Properties tab.
In the HTTP Port or HTTPS Port field, specify the custom port value.
...
Updating this option changes the default setting in the global.properties
file:
...
Info |
---|
Learn more about specific field settings on the Node Proxies tab in Updating a Snaplex. |
By default, a proxy routes all outbound HTTP and HTTPS requests. To restrict the proxy for requests routing outside your firewall, you need to change the proxy settings. First, you need to configure the Non-proxy Hosts field to restrict the endpoints that the proxy uses. Second, you need to disable the proxy to enable communication among the nodes in a Snaplex. If you cannot do the latter task, it can result in neighbor connectivity check failures for your Snaplex.
In the following example, the field restricts HTTP requests from routing to the local host or host in the http://example.com domain.
Key:
jcc.http.nonProxyHosts
Value:
localhost|127.*|[::1]|MYHOSTNAME|*.example.com
...
In some scenarios, your network operations team might configure a reverse proxy instead of a traditional proxy. In that case, all requests to the proxy are directly sent to the SnapLogic Control Plane. For example, if https://myproxy.test.com/ is the proxy server, a request will return the status from the SnapLogic Control Plane.
...
To enable the Snaplex to work with the reverse proxy, add the following two key-value pairs to the Global properties Properties of your Snaplex:
Global property | Key |
|
Value |
| |
Key |
| |
Value | control-plane-name |
Where control-plane-name is one of the following:
...
You can run the following cURL commands to test communication with the Snaplex. In each command, you specify the Control Plane name in the URL.
Name | Control Plane |
---|---|
elastic | Production - default |
emea | Production - EMEA region |
uat | Testing - default |
To verify if outbound requests are permitted from the Snaplex node:
...