Upgrading to Transaction Finder - Transaction Finder

Transaction Finder Plugin Guide

Applies to
Transaction Finder
Last updated
Content type
Guides > Plugin and extension guides
Transaction Finder
Plugin and extension guides

You can upgrade the Transaction Finder plugin version 3.0 or 3.1 directly to version

Before you begin

  1. Read the release notes to learn about important information for this release.
  2. Confirm that your versions of Security Center, the POS system, and the plugin are compatible.

What you should know

  • The plugin must be upgraded on all Security Center client and server computers.
  • IMPORTANT: Transaction Finder 3.2 uses a different version of ElasticSearch (7.16.3) than previous versions of the plugin. As a result, data cannot be automatically migrated from Transaction Finder 3.1 to Transaction Finder 3.2. Instead, this action must be done manually.
  • An upgrade keeps your current entities and their configuration, and all event notifications.
    IMPORTANT: After installing the plugin, the Elasticsearch indices must be upgraded. If the indices are not upgraded, events that occurred before the upgrade are unavailable in reports and only the events received after the upgrade are available.


  1. Open Server Admin, and back up the Directory database.
  2. Back up your Elasticsearch data.
  3. Create a copy of your ElasticSearch data.
    1. In Windows, navigate to your ElasticSearch program folder. By default, this is located in C:\Program Files\Elastic-Search-X.XX.X.
    2. Copy the \backups and \data folders locally to a different drive on your server.
  4. Uninstall the existing version of the Transaction Finder plugin.
  5. Install the latest version of the plugin.
  6. Create the Transaction Finder and Transaction Templates plugin roles.
  7. Open Config Tool and verify that the plugins are running properly without warnings.
  8. Point Elasticsearch to the \backups and \data folders that you copied locally.
    1. In Windows, navigate to Program Files > Elastic-Search-7.16.3 > config, and open the elasticsearch.yml file.
    2. In the Paths section, point path.repo to the \backups folder.
    3. Point path.repo to the \data folder. For example:
    # ----------------------------------- Paths ------------------------------------
    # Path to directory where to store the data (separate multiple locations by comma):
    path.repo: D:\elasticsearch\backups
    path.data: D:\elasticsearch\data
    # Path to log files:
    #path.logs: /path/to/logs
  9. In Config Tool, select the Transaction Finder plugin role.
    A warning is displayed stating that Elasticsearch indices must be upgraded.
  10. Click Close.
  11. Upgrade the Elasticsearch database so that events received before the upgrade are available.
    1. In Config Tool, open the Plugins task, and select the Transaction Finder plugin role.
    2. Click the Elasticsearch tab, scroll down to the Upgrade section, and then click Upgrade indices.
    3. Wait for the message All indices are up to date.
  12. Update the SQL database:
    1. Click the Resources tab, in the Actions section, click Database update.
    2. Wait for the update to complete.
  13. Deactivate the plugin role, and then activate it.
    The plugin is ready for use.