GridServer 7.1.1 Upgrade Checklist
You can migrate settings from your previous version of GridServer to your new version of a GridServer installation, but it’s important to not install on top of your previous installation. Instead, shut down your old Manager, and rename the old installation directory. You can then install the new version of GridServer in the same location. Later in the install, you supply a path to the renamed old installation so settings can be copied. An
upgrade.log file is generated that lists all changed configuration values, as well as settings that could not be migrated to the new installation.
It is recommended that before you start the upgrade, back up the
server.xml file from the DS_DATA/conf directory to a separate directory to preserve your custom configurations. After the upgrade, replace the server.xml file in DS_DATA/conf with the updated file from the release. Then, reapply any required customizations.
The only direct upgrade supported on GridServer version 7.1.1 is from GridServer versions 7.1.0. To upgrade from any other earlier version to GridServer 7.1.1, you must first upgrade to GridServer version 7.1.0.
Note:
-
.Authenticating all Grid Components is an additional security option provided in GridServer. For more information, see Authentication of Grid Components.
-
Migrate any deployed web components, Broker or Manager hooks, or bundled libraries that reference the
javax.*servlet API to thejakarta.*namespace.