Page Comparison

...

If the Groundplex fails to restart after a new configuration is installed, it reverts back to the last working configuration.

Best Practices

• When upgrading a Windows Groundplex to use the slpropz configuration file, the Monitor process would need to be updated by running jcc.bat update_service. The max heap space for the JCC process can be set incorrectly if the Monitor process is not updated.

• If you are unable to create an SLDB file using international language characters (such as æ, Æ, Ø) in the file name, update the jcc.use_lease_urls property in the Snaplex's Global Properties to False. This workaround works for all UTF-8 characters, and hence supports all global languages.

• By default, if the first run of an Ultra Task fails, SnapLogic attempts to run it for a total of five times. However, you can configure the number of times you want Ultra Tasks from a specific Snaplex to run by configuring the maximum number of allowed retries for an Ultra Task. To do so, modify the following parameter in Global Properties in Snaplex Update: ultra.max_redelivery_count to indicate the number of times you want a failed Ultra Task to run.

• We recommend that for your critical workloads on the production environment, you use a minimum of two worker nodes (and two FeedMaster nodes for Ultra) to avoid service disruption during Snaplex upgrades.

Migrating older Snaplex nodes 

If you have a Snaplex  running with a global.properties file in the $SL_ROOT/etc folder, you should consider migrating the Snaplex to use the slpropz mechanism for the configuration. Running with global.properties file requires that for any configuration change you must manually update the global.properties file, copy the updated configuration to all the nodes, and then restart all the nodes.

...