...
- As an Org admin, log into SnapLogic 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 Windows ZIP file and the configuration file onto the Windows machine where you want the Groundplex installed.
- Create the directory
\opt
on your server in the root of the C: drive. - Unzip the zip file to
c:\opt
. This will create a directoryc:\opt\snaplogic
and a directory structure as follows: Check your Windows environment to see if you have a version 8 or 11 of Java.
Note title Version of Java Make sure the version of Java that you are installing matches the type (32-bit or 64-bit) of Windows machine.
Do this by executing the commandjava -version
in a command window.- If the version of Java is less that 8 (or the latest recommended version, which is JRE 11), download the Windows JRE and install the JRE at
c:\opt\java
. - If JRE 8 or 11 is already available on the machine, the existing installation can be used. Use Notepad to edit the file
c:\opt\Snaplogic\bin\jcc.bat
and change the entry for the JAVA_HOME environment variable to the location of the existing installation, putting double quotes around the value. - If the host machine is configured for JRE auto-update, then each time a JRE update occurs, the older JRE installation is deleted by default. As a result, the Snaplex fails to start after the JRE update. To avoid this issue, use the static installation feature of the JRE installer. (Refer to Static JRE Installation for more information.)
To do a static install:- Add the
STATIC=1
option when running the JRE installer from the command line or from the Run dialog. - When the JRE auto-update occurs, uncheck the uninstall option for older JRE installations. This prevents the older installation from being removed.
- Add the
- If the version of Java is less that 8 (or the latest recommended version, which is JRE 11), download the Windows JRE and install the JRE at
- 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
. - From the command prompt, change to the
\opt\snaplogic\bin
directory. You may start the node by running the command:jcc.bat start
To establish if the process started, run the command:
jcc.bat status
It should be in the RUNNING state.
To verify the Snaplex has started, visit https://elastic.snaplogic.com/sl/dashboard.html#Health
The newly installed node should show up in the list of nodes for the Snaplex.
Starting a Snaplex as a Service
...
Alternatively, to install the Snaplex as a Windows service, run the following command as an administrator:
.jcc install_service
Then, go to the Windows Control Panel services,
...
- to view the entry for the SnapLogic Snaplex
...
- , and start the service from
...
- Tools in the
...
The installation instructions are as follows:
...
- If the version of Java is less that 8 (or the latest recommended version, which is JRE 11), download the Windows JRE and install the JRE at
c:\opt\java
. - If JRE 8 or 11 is already available on the machine, the existing installation can be used. Use Notepad to edit the file c:\opt\Snaplogic\bin\jcc.bat and change the entry for the JAVA_HOME environment variable to the location of the existing installation, putting double quotes around the value.
...
- Services window.
To establish if the process started, run the command:
jcc.bat status
...
. The state should be
...
Running
.To verify
...
the Snaplex has started, visit https://elastic.snaplogic.com/sl/dashboard.html#Health
The newly installed node should show up in the list of nodes for
...
the Snaplex.
Upgrading on Windows
By default the JCC will automatically update itself. To disable this, apply the following setting in c:\opt\snaplogic\etc\global.properties
:
...
Note |
---|
The autoupgrade process updates the binaries for the JCC process. When running as a service, doing a service restart causes the Monitor process to start with the old binaries files. To update the service to use the latest binaries, run the command: |
...