Versions Compared

Key

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

...

  • When upgrading a Windows-based 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 Global Properties of the Snaplex to False. This workaround works for all UTF-8 characters, and therefore supports all global languages.

  • By default, if the first run of an Ultra Task fails, SnapLogic attempts to run the Task 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 Tasks) to avoid service disruption during Snaplex upgrades.

...

  1. Manually update the global.properties file.

  2. Copy the updated configuration to all the nodes.

  3. Restart all the nodes.

We recommended users migrate to the new slpropz mechanism for defining configuration files.

...

  1. Update the Snaplex properties in Manager by adding custom configurations, which remain in the global.properties into the Snaplex properties.

    If you do not complete this step, then the configuration changes applied to the nodes are not available when running with slpropz.

  2. Navigate to the Manager > Update Snaplex > Downloads tab, and download slpropz file into the $SL_ROOT/etc folder.

  3. Back up the global.properties and keys.properties files, then remove them from the $SL_ROOT/etc folder.

  4. Restart the JCC process on all the Groundplex nodes through the Public API.

  5. Alternatively, as an Org admin, you can restart the JCC node through the Dashboard by clicking (blue star) on the target Groundplex node and selecting Node Restart.

...