Table of Contents |
---|
...
- As an org admin, log into Manager.
- Under Project Spaces on the left, locate the project where you want to create your Groundplex (or the global "shared" project), then select the Snaplexes tab on the right.
- Click the Create button and complete the Create dialog (later known as the Update Snaplex dialog). Once completed, the dialog reopens to the Downloads panel.
- Download the RPM/DEB and the configuration file onto a Linux machine. The Downloads panel has links to the installer and config files.
For CentOS (or Redhat) 6.3 or newer, do sudo rpm -i <filename>.rpm.
For Ubuntu 14.04 or newer, dosudo dpkg -i <filename>.deb
.
where <filename> is the name of the current installer file.After the software has been installed, place the downloaded configuration file in the "/opt/snaplogic/etc" directory and make sure the file name ends with .slpropz. Change the slpropz file to be owned by snapuser user, by running:
Code Block sudo chown snapuser:snapuser /opt/snaplogic/etc/myplex.slpropz sudo chmod 600 /opt/snaplogic/etc/myplex.slpropz
To start the on-premises service, type: sudo /opt/snaplogic/bin/jcc.sh start
To verify the Snaplex has started, visit https://elastic.snaplogic.com/sl/dashboard.html#Health. The newly install node should show up in the list of nodes for the Snaplex.
...
Info | ||
---|---|---|
For Snaplex downloads prior to Fall 2016 (4.7):
The RPM installation needs to be performed as the root user. The service startup needs to be done as the root user, the JCC process itself runs as the user snapuser. This allows enhanced security by allowing the keys stored in /etc/snaplogic to be protected from access by regular users. If enhanced encryption is not being used, it is possible to enable the service startup to be done directly as snapuser. To do that, perform steps 1 to 4 as above, then do:
The service start and stop can then be done as snapuser without needing root access.
|
FeedMaster
You can designate a Groundplex as a FeedMaster by setting the Snaplex node types on the Node Properties panel in the Update Snaplex dialog.
...
Find the trust store at /opt/snaplogic/pkgs/java version/lib/security/cacerts
, and confirm that every node in the Groundplex has the certificate imported. Perform the following task (for Linux) to generate and import a self-signed certificate on all the nodes in the Snaplex.
To import a certificate to the SnapLogic JCC:
- Get the certificate (.pem) file by using SSH.
Import the file by using the following command in the JCC node:
Paste code macro /opt/snaplogic/pkgs/jre1.8.0_45/bin/keytool -import -file <path_to_pem_file_from_step_1> -alias <alias_name_optional> -keystore /opt/snaplogic/pkgs/jre1.8.0_45/lib/security/cacerts -vEnter keystore password: changeit
Note This example is an excerpt from 1.8.0_45; the directory path may vary based on the Java installation directory.
- Restart the JCC process to confirm the import.
Run the following command to list certificates from the cacerts file:
Paste code macro /opt/snaplogic/pkgs/jre1.8.0_45/bin/keytool -list --keystore /opt/snaplogic/pkgs/jre1.8.0_45/lib/security/cacerts -v+
...
Code Block |
---|
update-rc.d -f snaplex remove |
System Limits
Some Linux installations have system ulimit settings set to low values. This can cause errors when running higher pipeline load on the node. The error usually seen is "java.lang.OutOfMemoryError: unable to create new native thread". To fix this, system limits for the Snapuser user need to be increased. The below can be added in the /etc/security/limits.conf to increase the file and process limits.
Note |
---|
The JCC process needs to be restarted after the limits are updated. |
...
Code Block |
---|
snapuser soft nproc 8192 snapuser hard nproc 65536 snapuser soft nofile 8192 snapuser hard nofile 65536 |
Groundplex on Azure
When running a Linux Groundplex on Azure, the default TCP keep alive settings on Azure have been seen to cause connectivity issues between the Groundplex and the SnapLogic control plane. The workaround is to disable keep alive in the JCC configuration. Add the following in global.properties
and restart the JCC using "/opt/snaplogic/bin/jcc.sh restart
"
Code Block |
---|
jcc.jvm_options = -Dhttp.keepAlive=False -Dcom.ning.http.client.AsyncHttpClientConfig.allowPoolingConnection=false -Dcom.ning.http.client.AsyncHttpClientConfig.allowSslConnectionPool=false |
Note |
---|
If you are unable to create an SLDB file using international language characters (such as æ, Æ, Ø) in the file name, update the 'jcc.use_lease_urls' property in the Snaplex's Global Properties to False. This workaround works for all UTF-8 characters, and hence supports all global languages. |