In this Article

Install a Snaplex on Linux

This article describes the procedures for installing an on-premise Snaplex in a Linux environment. 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 Cloudplex or an eXtremeplex. However, in command syntax and references to the UI, the generic term Snaplex is used.

...

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 appears. The Downloads tab has links to the installer and configuration files.
4. Download the RPM/DEB and the configuration file onto a Linux machine. 

   • 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:

   Code Block
   $ 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

A FeedMaster is a type of node that you use when running tasks based on Ultra Pipelines. 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.

Importing a Certificate to SnapLogic JCC nodes

To generate and import a self-signed certificate on all the JCC nodes in the Snaplex:

...

Automatically Start and Stop a Groundplex on Linux

You can use either the systemd or init.d utility 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.

Starting and Stopping the Groundplex by Using the Linux Systems Call

Use this procedure for Red Hat-like Linux distributions such as Red Hat, Fedora CoreOS, CentOS, and SuSE.

...

1. Log into the Groundplex host as a root or sudo user.

2. Create the startup service file:

   Code Block
   touch /etc/systemd/system/snaplogic.service

   
   

3. Change the permissions on the file:

   Code Block
   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 with a text editor. For example, the using a vim editor:

   Code Block
   vim /etc/systemd/system/snaplogic.service

   
   

5. Add the following text to the file:

   Paste code macro
   [Unit] Description=SnapLogic JVM After=network.target [Service] Type=forking ExecStart=/opt/snaplogic/bin/jcc.sh start ExecReload=/opt/snaplogic/bin/jcc.sh restart ExecStop=/opt/snaplogic/bin/jcc.sh stop [Install] WantedBy=default.target

   
   

6. Save and exit the file.
   
   

7. Enable the service by running the following command:

   Code Block
   systemctl enable snaplogic.service

   The service will start automatically when the host reboots.
   
   

8. Start the service:

   Code Block
   systemctl start snaplogic.service

   
   

9. To stop the Snaplex as a service, run the following command:
   

   Code Block
   systemctl disable snaplogic.service

   
   

Starting and Stopping the Groundplex by Using the init.d Utility

Use this procedure for Red Hat-like Linux distributions such as Red Hat, Fedora CoreOS, CentOS, and SuSE.

...

chkconfig --del snaplex

Debian-like Distribution (Debian and Ubuntu)

To add the Snaplex as a Service:

1. Log in to the Linux machine as root.

2. Change directories:

   Code Block
   cd /etc/init.d/

   
   

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

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

   
   

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

   Code Block
   sudo update-rc.d snaplex defaults 98 02

   
   

   Note
   title Troubleshooting if the machine reboot fails
   We recommend that you reboot the machine to verify whether the Snaplex service is restarting automatically on machine reboot. Under some conditions, the symlink resolution might fail when the machine is starting up. In this case, you can change the Snaplex startup script to be a file instead of a symlink. Run the following commands a root user: Code Block 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.

   
   

5. To stop the Snaplex as a Service, remove the service from update-rc.d management:
   

   Code Block
   update-rc.d -f snaplex remove

   
   

Configuring Java 11 on Linux

To update your JCC 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/openjdk-11.0.5+10-jre/


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/snaplogic as 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 properties 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.

System Limits

Some Linux installations have system ulimit settings that are set to low values. This low setting can cause errors when running higher Pipeline loads on the Groundplex JCC node, such as, java.lang.OutOfMemoryError: unable to create new native thread.

...

See Also

Video: Installing a Groundplex through a Debian-based Linux Distribution

...