Snaplex configuration changes
Snaplex nodes are typically configured using the slpropz
configuration file located in the $SL_ROOT/etc folder
.
If you use the slpropz
file as your Snaplex configuration, then you can expect the following:
-
After a Snaplex node is started with the slpropz configuration, subsequent configuration updates are applied automatically.
-
Changing the Snaplex properties in Manager causes each Snaplex node to download the updated
slpropz
and do a rolling restart with no downtime on Snaplexes with more than one node. -
Some configuration changes, such as an update to the logging properties, do not require a restart and are applied immediately.
-
Some configuration properties, like the Environment value, cannot be changed without doing manual updates for the
slpropz
files on the Snaplex nodes.
The Groundplex nodes must be set up to use a slpropz
configuration file before changes to these properties take effect. If you change that affect the software configuration, but there are nodes in the Snaplex that are not set up to use a slpropz
configuration file, a warning dialog appears with a listing of the unmanaged nodes.
Restart groundplex nodes
To restart the Snaplex process on your Groundplex nodes, run the following commands, depending on your OS:
Linux: /opt/snaplogic/bin/jcc.sh restart
Windows: c:\opt\snaplogic\bin\jcc.bat restart
.
Manage older groundplex installations
If you have an older Snaplex installation with a configuration defined in the global.properties
file, then the Environment value must match the jcc.environment
value In the JCC global.properties
file. To migrate your Snaplex configuration to the slpropz
mechanism, see Migrating Older Snaplex Nodes.
You should always configure your Snaplex instances using the slpropz
file because you do not have to edit the configuration files manually. Changes to the Snaplex done through Manager are applied automatically to all nodes in that Snaplex.
The temporary folder stores unencrypted data. These temporary files are deleted when the Snap/Pipeline execution completes. You can update your Snaplex to point to a different temporary location in the Global properties table by entering the following:
jcc.jvm_options = -Djava.io.tmpdir=/new/tmp/folder
The following Snaps write to temporary files on your local disk:
-
Anaplan: Upload, Write
-
Binary: Sort, Join
-
Box: Read, Write
-
Confluent Kafka: All Snaps that use either Kerberos and SSL accounts
-
Database: When using local disk staging for read-type Snaps
-
Data Science (Machine Learning) Snaps: Profile, AutoML, Sample, Shuffle, Deduplicate, Match
-
Email: Sender
-
Hadoop: Read, Write (Parquet and ORC formats)
-
JMS: When the user provides a JAR file
-
Salesforce: Bulk Query, Snaps that process CSV data
-
Script: PySpark
-
Snowflake: When using internal staging
-
Teradata: TPT FastExport
-
Transform: Aggregate, Avro Parser, Excel Parser, Join, Unique, Sort
-
Vertica: Bulk Load
-
Workday Prism Analytics: Bulk Load