Table of Contents
The basic steps for upgrading Seven, that will be explained in greater detail int the next paragraphs, are:
obtain upgrader;
create backup of current installation;
install upgrader through ServiceUI or installation directory;
modify upgrader script if you have a complex installation of Seven;
perform actual upgrade by starting Seven, preferably
with the -i option;
if relevant merge the changes in the new start scipts in your current scripts.
While the upgrading capabilities of Seven will not be discussed here in great detail, the upgrade capabilities for the container itself are almost equivalent to the ones for JSC Services. The major difference is that for a container upgrade to become effective all container instances for a particular Seven installation have to be shutdown and that one instance has to be restarted before the others are. In case of a complex deployment scenario, such as one with multiple installation directories, the upgrader configuration file created during upgrading, has to be edited.
Another important feature is that no matter what the version number of the container to be upgraded is, the latest upgrader will always be able to upgrade your version to the latest version of Seven. In case of the default XML configuration plugin, the plugin will be able to perform the necessary conversions of XML configuration files on demand, so the upgrader is not involved in upgrading configuration files.
Before upgrading you should create a backup of the current
installation and all config,
data and
install directories in the
event the upgrade and next deployment can't be successfully
completed.
The upgrader for Seven is a regular SAR file that can be
obtained from the Seven
project at the Cheiron site and follows the naming scheme
seven-upgrader-<version>-<build>.sar.
There are no distributions that allows an integrated JRE to be
upgraded.