You can upgrade the Transaction Finder
plugin version 3.0 or 3.1 directly to version 3.2.0.0.
Before you begin
- Read the release notes to learn about important
information for this release.
- 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.
Procedure
-
Open Server Admin, and back up the Directory database.
-
Back up your Elasticsearch
data.
-
Create a copy of your ElasticSearch data.
-
In Windows, navigate to your ElasticSearch program folder. By default, this is
located in C:\Program Files\Elastic-Search-X.XX.X.
-
Copy the \backups and \data folders
locally to a different drive on your server.
-
Uninstall the existing version of the Transaction Finder plugin.
-
Install the latest version of the
plugin.
-
Create the Transaction Finder and
Transaction Templates plugin roles.
-
Open Config
Tool and verify that the
plugins are running properly without warnings.
-
Point Elasticsearch to the \backups and \data
folders that you copied locally.
-
In Windows, navigate to , and open the elasticsearch.yml file.
-
In the Paths section, point path.repo to
the \backups folder.
-
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
#
-
In Config
Tool, select the Transaction Finder plugin role.
A warning is displayed stating that Elasticsearch indices must be upgraded.
-
Click Close.
-
Upgrade the Elasticsearch database so that events received before the upgrade are
available.
-
In Config
Tool, open the
Plugins task, and select the Transaction Finder plugin
role.
-
Click the Elasticsearch tab, scroll down to the
Upgrade section, and then click Upgrade
indices.
-
Wait for the message All indices are up to date.
-
Update the SQL database:
-
Click the Resources tab, in the Actions
section, click Database update.
-
Wait for the update to complete.
-
Deactivate the plugin role, and then activate it.
The plugin is ready for use.