...

You can add nodes to your Self-managed Snaplex and upgrade their configuration files. Learn more about customizing your Snaplex configuration.

Adding Nodes to your Groundplex

After you create a Self-managed Snaplex, you can still add nodes to your existing Groundplex by using the following procedure to update the Snaplex properties file:

1. Download and install the appropriate package for your operating system.

   The Downloads tab is not visible until after a Snaplex is created.
   

2. After installing the software, download the following configuration file and place it in the /opt/snaplogic/etc directory and make sure the file name ends with slpropz. The download link is valid for one hour. 
   

3. To migrate existing Groundplex nodes to use the slpropz configuration file, make sure the values in the Node Properties and Node Proxies match what you have configured in your global.properties file.
   

4. Download the slpropz configuration file, place it in the /opt/snaplogic/etc directory, and restart the JCC service. 

...

The Snaplex nodes should run with the new slpropz mechanism, therefore allowing for remote configuration updates.

Use case for display of pipelines after the JCC node is killed

The use case pertains to the display of pipelines after the JCC node has been terminated.

If there are multiple JCC nodes running, then a task with several instances is divided among them. For example, if we have an Ultra Task of nine instances, they will be split into three, each between the three JCC nodes. However, if any one of the nodes crashes, then the JCC state is not updated in the SLDB (Service Level DataBase). As a result, the JCC instance will remain in the RUNNING state, creating zombie instances on the Dashboard.

The zombie instances are seen on the Dashboard for a span of eight hours or until they reach the maximum heartbeat limit specified in the cleanup pipelines method. After the cleanup process is complete, the instances will no longer be visible on the Dashboard.