Page Comparison

...

1. As an org admin, log into Manager.
2. 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.
3. Click the Create button and complete the Create dialog (later know as the Update Snaplex dialog). Once completed, the dialog reopens to the Downloads panel.
4. Download the RPM/DEB and the configuration file onto a Linux machine. The Downloads panel has links to the installer and config files.

5. For CentOS (or Redhat) 6.3 or newer, do sudo rpm -i <filename>.rpm.
   For Ubuntu 14.04 or newer, do sudo dpkg -i <filename>.deb.
   where <filename> is the name of the current installer file.  

6. 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

   
   

7. To start the on-premises service, type:  sudo /opt/snaplogic/bin/jcc.sh start

8. 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.

...

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.

Automatically Starting and Stopping 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.

Using systemd to Start/Stop the Snaplex 

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:

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

   
   

3. Change the permissions on the file as follows:

   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 wiht a text editor. For example, the 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 as follows – the service will start automatically when the host reboots.

   Code Block
   systemctl enable snaplogic.service

   
   

8. Start the service as follows:

   Code Block
   systemctl start snaplogic.service

   
   

To delete the Snaplex as a service:

Disable the service as follows:

 systemctl disable snaplogic.service

Using init.d to Start/Stop the Snaplex

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

...

1. Login to the Linux machine as root.

2. Change directories as follows:

   Code Block
   cd /etc/init.d/

   
   

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

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

   


4. Add the softlink to chkconfig management as follows:

   Code Block
   chkconfig --add snaplex

   
   

   Note

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

   
   

To delete the Snaplex as a Serviceservice:

Remove the service from chkconfig 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

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