You can upgrade the Transaction Finder
plugin version 3.0 directly to version 3.1.
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.
- 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.
Procedure
-
Open Server Admin, and back up the Directory database.
-
Back up the plugin role
database.
-
Confirm that the Elasticsearch
database was backed up recently.
-
If the parser runs on the plugin server, open the Windows Services console, and stop
the parser service.
-
Install the latest version of the
plugin.
This installs local versions of the parsers.
-
If your deployment has the parsers running remotely, install the latest version of the remote
parsers.
-
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.