Versions Compared

Old Version 29

changes.mady.by.user Ankur Parekh

Saved on

compared with

New Version 30

changes.mady.by.user John Brinckwirth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Put 'Org' in title case and conformed all instances of organization to org

In this page

...

You can update Snaplex instances within an org Org automatically by selecting the checkbox on Manager > Settings > Auto Upgrade Snaplex.  This updates the Snaplex to the latest available version.

...

Note
  • All nodes within a Snaplex must be configured to run the same Snaplex version and Snap Pack versions.
  • Snap Catalog displays older version of Snap Packs until all JCCs in an organization Org upgrade to the new version. Newly published premium Snap Packs are not available in the Snap Catalog until all JCCs are upgraded. Pipeline execution do use the appropriate Snap Pack, based on whether the JCC is upgraded or not. 
  • Private Snap Packs can be used regardless of the JCC version.

To upgrade automatically to the latest available version, select the checkbox in Manager > Settings > Auto Upgrade Snaplex. 

...

The options you set on the Manager > Snap Pack page control which Snap Packs are used when pipelines run. As an org Org administrator, you can choose the options that work best for your organization Org or project. For example, you might configure a Developer org developer Org to always have the Latest Snap Packs to test new features, etc. But, for a Production orgOrg, you might choose Stable Snap Packs to make sure everything works as expected. 

...

The Latest/Stable menu provides an orgOrg-wide setting that controls which Snaps are used when a pipeline runs. Choices are:

...

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 orgOrg, but you can select a later (or earlier) version for a few of the Snap Packs, depending on your needs. 

...

When a quarterly release occurs, follow these steps to test the new Snaplex and Snap Packs:

  1. For the org Org you want to test, log in to SnapLogic as an org Org administrator.
  2. For all Snaplexes, update to the latest version in Manager. Since the updates are automatic, no manual JCC process restarts are required.
  3. Selectively execute and monitor a few pipelines to ensure that they are working as expected.

When you've finished testing pipelines for an orgOrg, you can manually roll out the changes to your other orgsOrgs. Alternatively, you can wait until the grace period ends and the orgs Orgs are updated automatically.

...

  1. Either validate or execute a pipeline in the given org Org where you have upgraded a Snap Pack.
  2. Click the pipeline statistics  icon to open the Pipeline Validation Statistics screen and hover over a Snap row (notice the associated Snap build number on the right bottom of the screen below). 

...

  • When a Dot Release is available for a Snap Pack, the Snap Pack is published and the Latest distribution points to the new Snap Pack.
  • Only orgs Orgs configured for a Latest distribution with a new Snaplex will automatically get the Snap Pack change. If you have orgs Orgs configured for a Stable distribution and a new Snaplex, you can manually apply a local Snap Pack override to use the new Snap Pack. 
  • Customers who need a Snap Pack patch will have to upgrade to the latest Snaplex to get the change. Using new a Snap Pack Dot Release with an old Snaplex is not supported.