If you have been running action logging with a previous release of Spotfire Server, then logging should continue to run, out of the box, after a successful upgrade. However, you might not be able to make full use of any new functionality unless you perform some manual changes. If you upgrade by installing new computers, you must ensure that the new hardware can connect to the database.

Things that might be added in a newer release are new categories, actions, extra properties, measures, etc. Occasionally, there will be updates to database views for more important additions. For Microsoft and Oracle databases there is an example analysis file and information services layer available, which might be updated.

Depending on which categories you enabled earlier, you should review the list of categories (including the web services settings). If you configure user action logs with the configuration tool, selecting categories is easy: you can review and select categories using the check boxes. If you previously selected all, any new categories will automatically be enabled.

• If you are logging to a file only, then no additional changes are necessary.
• If you are logging to database, there are some things to note. As before, all measures are logged to one single table called "ACTIONLOG". New categories, actions, properties, and measures will be logged to this table and you should not lose any log points. This table is the only thing required to run the logging to database.

No SQL related to the action logging functionality is executed automatically during an upgrade. This design gives full control to you and your database administrator, so the upgrade will not interfere if you have chosen to do some specific adaption, e.g., partitioned the "ACTIONLOG" table.

The database scripts used to configure database logging can also be used to update the views. They include the following functionality:

• Create user, schema and/or database. After an update, you can continue to log to the same location, so you do not need to recreate these.
• Create the ACTIONLOG table. This table is still used, and the structure is not altered.
• Optionally, create index to help with searches on the ACTIONLOG table. If you configured your earlier installation to omit indexes, then you do not need to change this configuration. With pruning enabled, the ACTIONLOG table has rows both added and deleted, so indexes benefit from being rebuilt regularly.
• Create views for the most important categories and actions, with more informative column names, using the same information as described in Action log entries. The views are needed only if you use them for analysis. There might be more views in a later release. The SQL for creating the views is available in the create_actionlog_db.sql scripts, which are found in the installation kit in the following directory:
  • ./scripts/{database type}_install/actionlog

See the specific topic below for details on how to update the database in your environment.