Upgrading to Transaction Finder 3.1 - Transaction Finder 3.1

Transaction Finder Plugin Guide 3.1

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

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

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.
  • Local parsers are upgraded along with the plugin, but if you have parsers running remotely, you must upgrade them separately.
  • 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 the plugin role database.
  3. Confirm that the Elasticsearch database was backed up recently.
  4. If the parser runs on the plugin server, open the Windows Services console, and stop the parser service.
  5. Install the latest version of the plugin.
    This installs local versions of the parsers.
  6. If your deployment has the parsers running remotely, install the latest version of the remote parsers.
  7. 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.
  8. Update the SQL database:
    1. Click the Resources tab, in the Actions section, click Database update.
    2. Wait for the update to complete.
  9. Deactivate the plugin role, and then activate it.
    The plugin is ready for use.