Introduction

• JS7 products ship with a JS7 - Software Bill of Materials that can be used to identify vulnerable components and package dependencies.
• For existing installations of JS7 products users can manage included software packages:
  • Disable packages, for example in case of vulnerabilities affecting 3rd-party components.
  • Enable packages from a backup location.
• Software package management is performed by scripts available for JOC Cockpit, Controller and Agents.
  • Software Package Management scripts are available for
    • Unix Shell with Linux, MacOS®, AIX® and Solaris® using bash, dash, ksh and zsh POSIX-compatible shells.
    • PowerShell version 5.1, 6 and 7 on Windows®, Linux, MacOS®.
  • Software Package Management scripts are available for download from JS7 - Download.

• Display feature availability
  StartingFromRelease 2.5.3

• The JS7 - Download page provides information and links for downloading current releases of the product. For the initial installation procedure see the JS7 - Installation articles.
• Updates and upgrades are performed using the .tar.gz/.zip installation archive files provided for the initial installation of newer releases.
  • The JS7 - Installation instructions also apply for updates and upgrades.
  • The JS7 - Deployment article explains strategies to update JS7 components on a larger scale.
• JS7 follows semantic versioning, with the wording being applied as follows:
• JS7 - Update to newer JS7 maintenance releases: update to a maintenance release within the same branch, for example within minor release 2.2
  • update from 2.2.1 to 2.2.2
  • update from 2.2.0 to 2.2.2 (the latest maintenance release includes any fixes of previous maintenance releases)
JS7 - Upgrade to newer JS7 minor releases: upgrade to a newer minor release, for example from minor release 2.1 to 2.2
• upgrade from 2.1.0 to 2.2.0
upgrade from 2.1.1 to 2.2.2

Resources

...