In this Page

Install a Snaplex on Linux

This article describes the procedures for installing an on-premise Snaplex on Linux OS. An on-premise Snaplex is also known as a Groundplex. This document uses the term Groundplex to distinguish this type of Snaplex (on-premise) from other types, such as a Clouplex or an eXtremeplex. Note that in command syntax and throughout the UI, the generic term Snaplex is used.

Groundplex installation covers the following tasks:

1. Setting up a Groundplex
2. Deploying FeedMaster
3. Importing a certificate to SnapLogic node.

For prerequisites, see Requirements for On-premises Snaplex. 

Setting up a Groundplex:

1. Log into SnapLogic Manager as an Org admin.
2. Navigate to the project where you want to create your Groundplex, then do one of the following:
   • Click the Snaplex tab, then click  to display the Snaplex popup.
     OR
   • Click to display the Assets drop-down list, then select Snaplex; the Snaplex popup appears.
     
     
     
3. Enter the required information on the Create Snaplex form. Once completed, the Downloads tab on the Snaplex popup is displayed.
4. Download the RPM/DEB and the configuration file onto a Linux machine. The Downloads panel has links to the installer and configuration files.

   • For CentOS (or Redhat) 6.3 or newer, run the following command
     sudo rpm -i <filename>.rpm

   • For Ubuntu 14.04 or newer, run the following command: 
     sudo dpkg -i <filename>.deb.

   • where <filename> is the name of the current installer file. 

5. After the software is 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 so that snapuser owns it by running the following commands:

   sudo chown snapuser:snapuser /opt/snaplogic/etc/myplex.slpropz
   sudo chmod 600 /opt/snaplogic/etc/myplex.slpropz

6. To start the Snaplex service, run:
   $ sudo /opt/snaplogic/bin/jcc.sh start
7. To verify the Snaplex has started, visit https://elastic.snaplogic.com/sl/dashboard.html#Health. The newly installed Snaplex node should show up in the list of nodes for the Snaplex.

Setting up a 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. For complete instructions, see Deploying a FeedMaster Node.

Import a Certificate to the SnapLogic JCC

While configuring accounts for various Snap Packs, you might encounter the following error message:

"Failed to validate account: Invalid credentials Cause: Could not send Message. (Reason: unable to find valid certification path to requested target; Resolution: Please provide valid credentials.)"

If this error occurs, update the cacert trust store in the SnapLogic JCCs to enable a successful SSL handshake to the endpoint.

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:

1. Get the certificate (.pem) file by using SSH.

2. Import the file by using the following command in the JCC node:

   This example is an excerpt from 1.8.0_45; the directory path may vary based on the Java installation directory.

3. Restart the JCC process to confirm the import.

4. Run the following command to list certificates from the cacerts file:

Automatically Start and Stop an On-premises Snaplex on Linux

You can use either the systemd or init.d utilty to start and stop the Snaplex. Procedures for both are included below. The procedures vary depending on which Linux distribution is installed on the Snaplex host.

Start/Stop the Snaplex by Using Systems

Red Hat-like distributions (Red Hat, Fedora Core, CentOS, and Suse)

To add the Snaplex as a Service:

1. Log in to the Snaplex host as a root or sudo user.

2. Create the startup service file as follows:

   touch /etc/systemd/system/snaplogic.service

3. Change the permissions on the file as follows:

   chmod 664 /etc/systemd/system/snaplogic.service

   This change provides read and write permissions for the owner and group, and read permission for others.
   
   

4. Open the file wiht a text editor. For example, the vim editor:

    vim /etc/systemd/system/snaplogic.service

5. Add the following text to the file:
6. Save and exit the file.

7. Enable the service as follows – the service will start automatically when the host reboots.

    systemctl enable snaplogic.service

8. Start the service as follows:

   systemctl start snaplogic.service

To delete the Snaplex as a service:

Disable the service as follows:

 systemctl disable snaplogic.service

Start/Stop the Snaplex by Using init.d

RedHat-like Distribution (Red Hat, Fedora Core, CentOS, Suse)

To add the Snaplex as a Service:

1. Login to the Linux machine as root.

2. Change directories as follows:

   cd /etc/init.d/

3. Create a softlink to the jcc.sh file as follows: 

   ln -s /opt/snaplogic/bin/jcc.sh snaplex

   


4. Add the softlink to chkconfig management as follows:

   chkconfig --add snaplex

   It is recommended to reboot the machine to verify whether the Snaplex service is restarting automatically on machine reboot. One issue which has been seen to cause the restart to fail is that the symlink resolution can fail when the machine is starting up. In that case, the Snaplex startup script can be changed to be a file instead of a symlink. To do that, run the following as root user:

   rm /etc/init.d/snaplex
   cp /opt/snaplogic/bin/jcc.sh /etc/init.d/snaplex
   echo "export SL_ROOT=/opt/snaplogic" >> /etc/sysconfig/jcc

To delete the Snaplex as a service:

Remove the service from chkconfig management as follows:

chkconfig --del snaplex

Debian-like Distribution (Debian, Ubuntu)

To add the Snaplex as a Service:

1. Log in to the Linux machine as root.

2. Change directories as follows:

   cd /etc/init.d/

3. Create a soft-link to the jcc.sh file as follows: 

   ln -s /opt/snaplogic/bin/jcc.sh snaplex

4. Install the service using update-rc.d. For example: 

   sudo update-rc.d snaplex defaults 98 02

   It is recommended to reboot the machine to verify whether the Snaplex service is restarting automatically on machine reboot. One issue which has been seen to cause the restart to fail is that the symlink resolution can fail when the machine is starting up. In that case, the Snaplex startup script can be changed to be a file instead of a symlink. To do that, run the following as root user:

   rm /etc/init.d/snaplex
   cp /opt/snaplogic/bin/jcc.sh /etc/init.d/snaplex
   echo "export SL_ROOT=/opt/snaplogic" >> /etc/sysconfig/jcc

   On a Debian system, the /etc/sysconfig directory would need to be created if not already present.

To delete the Snaplex as a Service:

Remove the service from update-rc.d management as follows:

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.

snapuser soft nproc 8192
snapuser hard nproc 65536
snapuser soft nofile 8192
snapuser hard nofile 65536

Configuring Java 11 on Linux

To switch existing nodes to OpenJDK Java 11:

1. Stop the existing JCC node by running the following command:
   $ sudo /opt/snaplogic/bin/jcc.sh stop
   
   
2. Download the new Snaplex installer and install the Groundplex, running the RPM, DEB, or Docker installers as appropriate.
   • For RPM systems, run the following command:
     $ rpm -U snaplogic-snaplex.rpm
   • For DEB systems, run  the following command:
     $ dpkg -i snaplogic-snaplex.deb
   • For Docker, stop the existing container and start a new container using the latest image.
     
     
3. Add the following entry to the /etc/sysconfig/jcc directory. You must create this directory and file if neither are present. 
   export SL_JAVA_HOME=/opt/snaplogic/pkgs/jdk-11.0.1/


4. Start the JCC node by running the following command:
   $ sudo /opt/snaplogic/bin/jcc.sh start.

Changing the installation folder

If you want to use the/myopt/myroot instead of the /opt/snaplogicas the installation folder and myuser instead of snapuser, do the following steps:

1. Run the following commands after installing the RPM/DEB package:
   1. sudo mv /opt/snaplogic /myopt/myroot
   2. sudo chown -R myuser /myopt/myroot
2. Add the following entities in the /etc/sysconfig/jcc file. If this file does not exist, create it.
   1. export SL_USER=myuser
   2. export SL_ROOT=/myopt/myroot
3. Restart the service with the following command: 
   sudo /myopt/myroot/bin/jcc.sh restart
4. To make a service using init.d, make the /etc/init.d/snaplex file a symlink to the /myopt/myroot/bin/jcc.sh file.

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"

jcc.jvm_options = -Dhttp.keepAlive=False -Dcom.ning.http.client.AsyncHttpClientConfig.allowPoolingConnection=false -Dcom.ning.http.client.AsyncHttpClientConfig.allowSslConnectionPool=false