Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Memory (RAM) is used by the Pipelines to execute. Some Snaps, like Sort Snaps, which accumulate many documents, consume more memory; the amount of memory used is influenced by the volume and size of the documents being processed. For an optimum sizing analysis based on your requirements, contact your SnapLogic Sales Engineer.

Supported Operating Systems

The SnapLogic on-premises Snaplex is supported on the following operating systems:

...

Network In (Min/Rec)

Min: 10MB/sec, Recommended: 15MB/sec+

Depends on usage

Network Out (Min/Rec)

Min: 5MB/sec, Recommended: 10MB/sec+Depends on usage

Network Firewall Requirements

...

After the Snaplex service is started on a node, the service connects to the SnapLogic Cloud service. Runtime logs from the Snaplex are written to the /opt/snaplogic/run/log (or c:\opt\snaplogic\run\log) directory. The Dashboard shows the nodes that are currently connected for each Snaplex.

Snaplex Node Configuration

Snaplex nodes are typically configured using a slpropz configuration file, located in the $SL_ROOT/etc folder. 

If you use the slpropz file as your Snaplex configuration, then:

...

After a Snaplex node is started with the slpropz configuration, subsequent configuration updates are applied automatically.

...

each Snaplex

...

Some configuration changes, such as an update to the logging properties does not require a restart and are applied immediately.

...

If you have an older Snaplex installation and its configuration is 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.

...

.

Understanding Distribution of Data Processing across Snaplex Nodes

...