In this Article
|JCC node's HTTPS||8081||TCP||McAfee Framework Service (FrameworkService.exe) |
|FeedMaster node's HTTPS||8084||TCP||Apache Tomcat server (Netbeans JSP servlets)|
|FeedMaster node's broker||8089||TCP||Splunk web-interface|
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 which are available:
- For http port: jcc.jetty_port = 8x89
Java Runtime Environment (JRE)
You must install the Java Runtime Environment (JRE) 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.
Installing the Snaplex
To install Snaplex on-premises on Windows:
- 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 directory
c:\opt\snaplogic and a directory structure as follows:
Check your Windows environment to see if you have a version 11 of Java.
Do this by executing the command
java -version in a command window.
- If the version of Java is less than JRE 11, download the Windows JRE and install the JRE at
- If JRE 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.
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.
- After the software has been installed, place the downloaded configuration file in the \
etc directory and make sure the file name ends with
- From the command prompt, change to the
\opt\snaplogic\bin directory. You may start the node by running the command:
Alternatively, to install the Snaplex as a Windows service, run the following command as an administrator:
Then, go to the Windows Control Panel services, to view the entry for the SnapLogic Snaplex, and start the service from Tools in the Services window.
To establish if the process started, run the command:
jcc.bat status. The state should be
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
- Are you starting the JCC node as an Administrator?
- Is the c
:\opt\snaplogic\run\log folder full? If it is full, delete the logs and try restarting again.
- Is JAVA_HOME set correctly?