Snaplex node customizations

When updating the Java version on a node or when adding a new node to a Snaplex, any customizations done on the node will have to be manually copied over, including the following:

  • Custom trust store entries: The JRE uses a cacerts trust store file at <JAVA_HOME>/lib/security/cacerts that has the trusted root certificates. If there are Snap endpoints that are using certificates signed by other providers, then the providers need to be added to the cacerts file. The update needs to be done every time the JRE version is updated or when a new node is being provisioned.
  • ulimit changes: If the file and process limits are customized, then the changes have to be applied again when a new node is being provisioned to the Snaplex.
  • Custom binaries: Some Snaps require customer binaries to be installed on the Snaplex node, like native libraries for SAP and bulk loading tools for database Snaps. These changes have to be applied manually when a new Snaplex node is being provisioned.

JCC node debug mode

If you are using the Snaplex for Snap development and it needs to be put in debug mode, you can configure the monitor process to start the JVM with debug options enabled. Add the following line in etc/global.properties:

jcc.jvm_options = -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000

This starts the Snaplex process with the debug port set to 8000. With this configuration, any Pipeline executions sent to the Snaplex will hit breakpoints set in the Snap code.

Important: Enable debug mode only in non-production environments. The JDWP port (8000) allows unauthenticated remote access to the JVM. Restrict access to this port via firewall rules or bind it to localhost to prevent unauthorized access.