In this article
| Table of Contents | ||
|---|---|---|
|
Overview
Previously, when the SnapLogic control plane was updated for a quarterly release, Snaplex nodes and Snap Packs were automatically updated at the same time. When a quarterly release goes outis deployed, each SnapLogic customer can decide to keep their existing version of Snaplex (Cloudplex or Groundplex) and Snap Packs for up to 35 four weeks + two days before upgrading. This gives time window allows you the opportunity to make sure ensure that the new Snaplex and Snap Packs are stable and working as expected before rolling them out to all your entire companyOrgs.
You can update Snaplex instances within an Org automatically by selecting the checkbox on Manager > Settings > Auto Upgrade Snaplex. This setting updates the Snaplex to the latest available version.
...
Impact on your SnapLogic instance during the release window
...
The release update has zero downtime for the SnapLogic
...
platform during the quarterly release. This implementation means that there
...
is not a maintenance notice on the SnapLogic UI; you can continue accessing the UI during the maintenance window and make updates. Your Pipelines, API calls,
...
and Scheduled Tasks will operate normally.
| Note |
|---|
To achieve zero downtime and high availability, your Snaplex should have multiple nodes. As with prior releases, if your Snaplex has only one JCC or FeedMaster node, then your node will be down for a few minutes during the Snaplex upgrade process. Hence, scheduled Pipelines and Ultra Tasks will not run while the node is down for a few minutes. No action is required by you and all operations will restart normally once the node is running again. |
Grace Period for Upgrades
Thirty-five days after a quarterly release, Snaplex and Snap Pack upgrades automatically occur four weeks plus two days after a quarterly release. Older Snaplex nodes and Snap Packs are automatically updated and Snaplex rollbacks are not allowed. Warning messages are provided well before the grace period ends.
If you do not select the checkbox in Manager > Settings > Auto Upgrade Snaplex, then for the first 35 days during this time period after a quarterly release, automatic updates for Snaplex nodes are suspended and the version is not changed. During this grace period, you can manually upgrade the new Snaplex War file to make sure everything is WAR (Web Application Resource) file to test your pipelines and ensure they are working as expected, . You can then try out the new Snaps and Snap Packs.
| Note |
|---|
|
To upgrade automatically to the latest available version, select the checkbox in Manager > Settings > Auto Upgrade Snaplex.
...
In addition to the menu choices (Latest/Stable, Old/New), you can also configure individual Snap Pack "local overrides" to use when a Pipeline runs. For example, you might have a Stable set of Snap Packs configured for your Org, but you can select a later (or earlier) version for a few of the Snap Packs, depending on your needs. 
...
- For the Org you want to test, log in to SnapLogic as an Org administratoradmin.
- For all Snaplexes, update to the latest version in Manager. Since the updates are automatic, no manual JCC node process restarts are required.
- Selectively execute and monitor a few Pipelines to ensure that they are working as expected.
...
During the grace period, you might need to downgrade a Snaplex or Snap Pack because of compatibility issues, platform restrictions, and so on. In this case, you can rollback a Snaplex. Change the Snaplex version to an older version in the Manager.
Rolling back a Snaplex
To rollback roll back a Snaplex, replace your existing Snaplex software with an older version.
...
Learn more about updating a Snaplex version.
- In the Update Snaplex dialog, select the Recommended version from the Version dropdown list.
Do not select the version with the designation Deprecated or Restricted Distribution unless advised by SnapLogic Support. - Click Update.
...