...
Therefore, any extra latency or network hops between neighboring JCC nodes can introduce performance and reliability problems.
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.
Changing the Snaplex properties in Manager causes each Snaplex node to download the updated slpropz and does a rolling restart with no downtime on Snaplex instances with more than one node.
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. |
You should always configure your Snaplex instances using the slpropz file because you do not have to edit the slpropz files manually and changes to the Snaplex done through Manager are applied automatically to all nodes in that Snaplex, making configuration issues, which may prevent the Snaplex from starting, automatically reverted. |
Hardware Requirements
The Groundplex (also known as the on-premises Snaplex) is a local server running on hardware, that may be virtual, provisioned by the customer and must conform to the following minimum specifications:
...