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.
|Module||Items to Back Up|
|Advanced Matching Module, Data Normalization Module, and Universal Name Module||Back up the contents of these subfolders located in
|Data Hub Module||If you do not already have a backup
copy of your models, create a backup manually. To create a
backup manually, open the Relationship Analysis Client and
click Manage. Select the model you
want to back up then click
In addition to backing up your models, back up these two property files:
|Location Intelligence Module||Back up your named resources, data, and configuration files.|
You can see when the server has started up by opening the log file <Spectrum Installation Location>\server\app\repository\logs\wrapper.log and looking for this message:
INFO [Server] Pitney Bowes Spectrum(TM) Technology Platform Database (Version version build) Started
You can specify multiple comma-separated IP addresses. You should specify multiple seed nodes so that if one is down others can be used to allow the node to join the cluster. The node will attempt to access each seed node in the order listed. If none of the seed nodes can be reached, the node will not join the cluster.
Some modules have post-upgrade steps you need to perform.
|Data Hub Module||Open this file in a text editor:
server/modules/hub/neo4j.properties and set the
property allow_store_upgrade property to
true. The purpose of this property is to protect
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/app/repository/logs/wrapper.log for errors or warning messages. Once all models have been upgraded, go back to the hub.properties file and comment out the allow_store_upgrade property.