Migrating your Spotfire Statistics Services configuration and data

Upgrading from a previous release of Spotfire Statistics Services requires a new installation. However you can retain and migrate configuration and data.

About this task

We recommend shutting down the previous version service and installing the new version in a different location. After you have installed the new version, follow this guidance.

Before you begin

Install the new version, test that the service works, and then shut down the new version's service before completing these steps.

Procedure

Copy any .jar files from your endorsed directory to your new installation.
From the older installation, open the folder SPSERVER_HOME/conf and copy the appropriate configuration and data from the old installation to the new.
For most configuration and data, you can migrate from the previous installation to the new one, with the cautions and exceptions listed in here.
Important: Do not modify the following entries in the file conf/server.properties:
- service.id
- service.url
Do not modify the following properties, unless you need to change them from the values you selected during installation.
- jmxremote.port
- jmxremote.password
- jmxremote.username
If you are upgrading from a version of Spotfire Statistics Services earlier than version 6.0, do not copy the older versions of the files conf/database.properties and conf/ldap.properties. These files have changed. Specifically, do not copy the entry database.url in the file conf/database.properties from the older installation. Instead, just change the SPSERVER_SHARE location to point to the new installation.

If you are installing a cluster, do not copy the file conf/cluster.properties.
Locate previous user data in SPSERVER_HOME/data/common and TSSS_HOME/data/users, and then copy these directories directly from the previous installation to the new installation.

Note: All other directories under SPSERVER_HOME/data contain temporary data from the previous installation and should not be copied.

What to do next

Complete any remaining configuration tasks. If no further tasks are needed, start the service.