...
| Note |
|---|
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:
|
In a Snaplex installation on a Windows machine, you need to install the JRE and configure the JRE location in the jcc.bat property. 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 version in your self-managed Snaplex.
We recommend installing the latest JRE 11 version available at https://adoptium.net/temurin/releases/?version=11.
If you are running with 11.0.10 onwards, endpoint connections to TLS 1.0 and 1.1 are disabled by default. We recommend that you update the endpoint to support TLS 1.2 or higher, for security.
Older Versions of JRE and TLS
JRE versions prior to 11.0.8 have issues connecting to TLS 1.3 endpoints. We recommend using a newer JRE version.
Renabling Support for Older Versions
If updating the TLS endpoint is not possible, then the Snaplex JRE can be updated to re-enable support for older TLS versions by doing these steps:
Open the jre/conf/security/java.security file in the JRE installation folder that you configured during installation.
Change the jdk.tls.disabledAlgorithms configuration property by removing TLSv1, TLSv1.1.
Restart the Snaplex to re-enable support for TLS 1.0 and 1.1.
...