Versions Compared

Version Old Version 7 New Version 8
Changes made by

Robert Fish

Robert Fish

Saved on

Key

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

Because the customer has to install the Snaplex software on nodes in the customer data center or in a private cloud, you should plan your Groundplex deployment.

Every Snaplex has Every Snaplex requires a name, for example ground-dev or ground-prod. In the SnapLogic Designer, you can choose which Snaplex pipelines Pipelines are executed on. The Snaplex configuration has an environment associated with it, for example dev or prod. When you configure the nodes are configured for the Snaplex, you must set the jcc.environment has to be set to the environment value as you’ve configured for the Snaplex.

...

After the Snaplex service is started on a node, the service connects to the SnapLogic cloud 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.

Best Practices for Setting Up JCC Node Communication within a Groundplex

We recommend that you set up JCC nodes in a Snaplex are setup within the same network and data center. Communication between JCC nodes in the same Snaplex is required for the following reasons:

...

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 initiates 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 globalJCC global.properties fileproperties 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 is a local server running on hardware, that may be virtual, provisioned by the customer, and must conform to the following minimum specifications:

...