...
8090 for the JCC node
8091 for the FeedMaster node
...
HTTP/HTTPS Port Customization
You can customize the HTTP port configuration used by the JCC node. On .
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 by setting the port number to the following value:
...
HTTP Port:
jcc.jetty_port
...
=
...
8090
HTTPS Port
...
You can customize the HTTPS port configuration used by the JCC node. On the Node Properties tab in the Update Snaplex dialog, you can specify a value in the HTTPS Port field.
...
:
...
jcc.cc_secure_port
...
=
...
8888
...
Feedmaster Broker Port Customization
You can If you Snaplex has a Feedmaster node, you can also customize the FeedMaster Feedmaster node port configuration used by the JCC node. The default is 8089. On the Node Properties tab in
Point the cursor and click the target Snaplex to open the Update Snaplex dialog
...
.
Click the Node Properties tab.
Under Global properties, click
to open the key-value fieldset. Specify the custom port value.
Key:
jcc.broker_service_uri
...
Value:
ssl://0.0.0.0:8089?transport.enabledProtocols=TLSv1,TLSv1.1,TLSv1.2&transport.enabledCipherSuites=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA
| Info |
|---|
The port used should be unique and cannot be the same as the ports used for the HTTP and HTTPS services. |
HTTP Connection Pooling
Outbound HTTP connections created to the SnapLogic cloud or to any other HTTP endpoints are placed in a connection pool by default. You can configure the properties for the pool in etc/global.properties by adding them to the Update Snaplex dialog, Node Properties tab, Global properties table.
To increase the maximum number of connections that can be created at a time (default is 100):
...
| language | java |
|---|
Key:
jcc.http_client_max_connections
...
Value:
300
To set the TCP connection timeout for an outbound connection (in seconds, the default is 60, zero is an infinite timeout):
...
| language | java |
|---|
Key:
jcc.http_client_tcp_connection_timeout
...
Value:
120
To set the inactivity timeout for a socket connection (in seconds, default is 3600, zero is an infinite timeout).
...
Key:
jcc.http_client_socket_timeout
...
Value:
300
| Info |
|---|
The http_client_socket_timeout must be set to a value higher than the maximum child Pipeline execution time. |
HTTP Proxy Configuration
In the typical HTTP Proxy configuration, the proxy forwards requests to any endpoint. You can use the same HTTP proxy for connecting with the SnapLogic Control Plane and also for connecting to other REST endpoints, such as Salesforce. Forward HTTP proxy type is the most flexible method for integrating multiple endpoints.
...
| 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.
...
nonProxyHostsValue:
localhost|127.*|[::1]|MYHOSTNAME|*.example.com
The proxy settings are configured per the standard JRE settings. These are displayed in the Node Proxies tab of your Snaplex in SnapLogic Manager:
| Paste code macro |
|---|
jcc.http.proxyHost = myproxy.example.com jcc.http.proxyPort = 3128 jcc.http.nonProxyHosts = localhost|127.*|[::1]|MYHOSTNAME|*.example.com jcc.https.proxyHost = myproxy.example.com jcc.https.proxyPort = 3128 jcc.https.nonProxyHosts = localhost|127.*|[::1]|MYHOSTNAME|*.example.com jcc.http.proxyUser=proxyuser jcc.http.proxyPassword=proxypass |
...
In some scenarios, your network operations team might have configured 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.
For example:
...
| language | html |
|---|
curl https://myproxy.test.com/status
To enable the Snaplex to work with the reverse proxy, add the following information to two key-value pairs to the Global properties of your Snaplex properties:
...
Global property | Key |
|
...
Value |
|
...
Key |
|
...
Value | control-plane-name |
Where control-plane-name is one of the following:
elastic
uat
emea
| Info |
|---|
Setting up a reverse proxy is unusual. In most cases, a forward proxy should be used. |
Troubleshooting Snaplex Communication
This article covers some basic troubleshooting tips 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
...
:
...
curl
...
https://
...
control-plane-name.snaplogic.com/status
A response with the status OK indicates successful completion.
If this request hangs or fails, then a proxy is required. Request the HTTP proxy information from your network operations team.
To check access through a proxy
...
:
...
curl
...
-x myproxy.mydomain.com:3128
...
https://
...
control-plane-name.snaplogic.com/status
If this request fails with a 407 (Proxy Authentication Required), then you need to specify the authentication information in the proxy.
To check the proxy authentication, run the following command:
...
curl
...
-x myproxy.mydomain.com:3128
...
--proxy-user
...
"proxyuser:proxypasswd"
...
https://
...
control-plane-name.snaplogic.com/status
The -v option can be added to curl to get detailed messages.
Control Plane Name
| Info |
|---|
For Windows-based Groundplexes, download the TLS (SSL) enabled |
...
...
to verify your configuration. |