In this article
We recommend you disable any anti-virus or firewall software (including Windows firewall) installed on the Snaplex node. If you cannot disable the software, then ensure that the Snaplex process is not scanned by the anti-virus. The specific action depends on the antivirus software type and scanning rules enabled. The following are the guidelines:
c:\opt\snaplogic
folder.Function | Port | Protocol |
---|---|---|
JCC node's HTTPS | 8081 | TCP |
FeedMaster node's HTTPS | 8084 | TCP |
FeedMaster node's broker | 8089 | TCP |
If another application already uses one of the JCC ports used by SnapLogic, the JCC nodes do not complete a full start cycle. The workaround is to override the default port by assigning the following entries in the global.properties file to ports that are available:
For HTTPS port: jcc.cc_secure_port = 8x81
You must install the Java Development Kit (JDK) before installing your on-premise Snaplex. The SnapLogic platform supports Java 11. We recommend you use the latest patch version available of Java 11 for your Windows environment. To update your Snaplex to the Java 11, see Upgrading Your Groundplex to Java 11.
Only OpenJDK 11 is certified by SnapLogic. Since no other JDK 11 distribution is currently certified by SnapLogic, we recommend that you only use OpenJDK 11 when upgrading to Java 11. |
File names generated by SnapLogic for suggest data can be longer than 260 characters long. We recommended that you configure the Snaplex node to allow longer file paths. See Maximum Path Length Limitation - Win32 apps for details.
If the Snaplex is already installed on the machine, the old installation needs to be stopped before the installation can be done at a new location. To stop the old installation, run |
\opt
on your server in the root of the C: drive.c:\opt
. This will create a directory c:\opt\snaplogic
and a directory structure as follows:Check your Windows environment to see if you have a version 11 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 command java -version
in a command window.
c:\opt\java
.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.STATIC=1
option when running the JDK installer from the command line or from the Run dialog.opt\snaplogic\
etc
directory and make sure the file name ends with .slpropz
.\opt\snaplogic\bin
directory. You may start the node by running the command: jcc.bat start
jcc.bat install_service
.
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.
When running the Windows-based Snaplex as a service, performing a service restart causes the Monitor process to start with the old binaries files.
When upgrading your Snaplex to the 4.29 release (May 2022), you need to reinstall the Snaplex using the 4.29 installer zip file for Windows. Upgrading through Manager will only upgrade the war file, but not the binaries. |
To update the service to use the latest binaries, you can choose from one of the two following options:
Stop the Windows-based Snaplex service.
Remove using bin\jcc.bat remove_service
.
Back up the configuration files from \etc
folder.
If you have a customized node configuration, make sure to back up the global.properties file to retain the customized node configuration after the upgrade. |
Remove C:\opt\snaplogic
.
Reinstall the Windows-based Snaplex using the 4.29 zip file.
bin\cygwin1.dll
and bin\cygrunsrv.exe
from the new zip to the existing installation location.bin\jcc.bat update_service
.By default the JCC node will automatically update itself. To disable this, apply the following setting in c:\opt\snaplogic\etc\global.properties
:
jcc.enable_auto_download = False |
:\opt\snaplogic\run\log
folder full? If it is full, delete the logs and try restarting again.Temporary files created by the Snaplex service are stored under the user account that started the JCC process. In some cases, if the user account used to start the Snaplex is changed or if the Snaplex was previously started as an application and now is being started as a service, then you might encounter startup errors because of the user account being different. In such cases, deleting the following folders can help fix the issue:
|