In this article

...

1. Log into SnapLogic Manager as an Org admin.

2. Navigate to the project where you want to create your Groundplex, and perform one of the following steps:

   • Click the Snaplex tab, then click   to display the Snaplex dialog.
     OR

   • Click to display the Assets drop-down list, then select Snaplex; the Snaplex dialog appears.
     

     Image RemovedImage Added

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 or DEB-based installer and configuration files onto a Linux machine, where <filename> is the name of the current installer file and fontconfig and zip are the required dependencies:
   

   • For CentOS (or Redhat) 6.3 or newer, run the following commands:
     $ sudo yum install fontconfig zip
$ sudo rpm -i <filename>.rpm
     

   • For Ubuntu 14.04 or newer, run the following command: 
     $ sudo apt-get install fontconfig zip
$ sudo dpkg -i <filename>.deb
     

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 that the Snaplex has started, visit https://elastic.snaplogic.com/sl/dashboard.html#Health. The newly installed Snaplex node should appear in the list of nodes for the Snaplex.

...

...

1. Log in to the 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

...

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

Configure Java 11 on Linux

...

Manage disk volumes for Groundplex nodes

To address issues that cause disk full errors and to ensure smoother operations of the systems that affect the stability of the Groundplex, you need to have separate mounts on Groundplex nodes. Follow the steps suggested below to create two separate disk volumes on the JCC nodes.

• The JCC nodes are equipped with two separate disk volumes to ensure that the operating system and pipeline execution workspace remain segregated.

  • The JCC is installed in /(root) volume, and the workspace is separated in the bind mounts.

  • The second disk volume is mounted on /workspace, and bind mount directories are created.

    Code Block
    sudo su mkdir /workspace

• Create subdirectories in /workspace and /opt/snaplogic/run directories using the commands specified below:

mount /dev/nvme2n1 /dev/workspace  #(replace nvme2n1 with the device name)
mkdir -p /workspace/{fs,broker,tmp}
mkdir -p /opt/snaplogic/run/{fs, broker}
chown -R snapuser:snapuser /workspace && chmod -R 0755 /workspace

• Create the bind mounts using the commands specified below:

mount --bind /workspace/fs /opt/snaplogic/run/fs
mount --bind /workspace/broker /opt/snaplogic/run/broker
mount --bind /workspace/tmp /tmp   

...

For Example:             

/dev/nvme1n1 /workspace xfs noatime 0 0
/workspace/fs /opt/snaplogic/run/fs none bind 0 0
/workspace/broker /opt/snaplogic/run/broker none bind 0 0
/workspace/tmp /tmp none bind 0 0 

Configure Java 11 on Linux

The JRE is bundled with the Snaplex installer. While a Snaplex auto upgrade updates the SnapLogic binaries in the installed Snaplex, the JRE version is not automatically updated. You must manage the JRE versions of your Snaplex.

...

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

...