Upgrading a Cluster with a Separated Database
- Before upgrading, be sure to read the release notes for the new version. The release notes contain a list of known issues, important compatibility information, supported upgrade paths, and module-specific data backup recommendations.
- Apply all the latest updates available for your operating system, especially those that resolve issues with Java.
- Important: We recommend that you create a backup before upgrading so that you can recover your flows, security settings, and other settings, if an error occurs during the upgrade process.
-
Note: If you have customized settings in the wrapper.conf file located in <SpectrumDirectory>/server/bin/wrapper, we recommend that you copy this file to a separate location before you upgrade the Spectrum™ Technology Platform server. After you complete the upgrade, compare the contents of wrapper.conf installed during the upgrade with the contents of the saved copy of the file. You can then manually copy customizations that you want to retain after the upgrade into the updated version of the file. This is particularly important for changes to the initial and maximum Java heap sizes.
This procedure describes how to upgrade Spectrum™ Technology Platform when you have separated the configuration database from the server. To upgrade an environment that has a separated configuration database, you first upgrade the configuration database cluster, then the server cluster.
Note: Any job or subflow stored in the system during a server upgrade is marked as
exposed to provide the same behavior for those jobs and subflows as before the
upgrade. Any job or subflow that is exported prior to the upgrade will not be
exposed. Therefore, when importing these jobs or subflows back into the system, you
must manually expose the imported job or subflow.
Some modules have post-upgrade steps you need to perform.
Data Hub Module | Open this file in a text editor: server/modules/hub/db/neo4j.properties and set this property to true: dbms.allow_upgrade=true. This property protects against unintentional and irreversible store upgrades. Setting this property to "true" indicates that you understand the ramifications of proceeding with an upgrade and have taken the necessary precautions before proceeding. Restart the Spectrum™ Technology Platform server. The server will upgrade each model. Examine the file server/logs/spectrum-server.log for errors or warning messages. Once all models have been upgraded, edit the neo4j.properties file again and comment out the dbms.allow_upgrade property. |
Spatial Module | During an upgrade, the pool size is reset to 4 if set to a lower value. A pool size setting of 4 or more is unaffected. To change the Remote Component Pool Size value after upgrading, open the Management Console and select . Change the pool size value and click Save. For details, see Modifying the Pool Size in the Spectrum Spatial Guide. |
Spectrum Screener ™ | See the Upgrading Screener section of the Screener guide for details. |