v5 Server Pre-Flight Upgrade Check
The Polarity v5 Pre-Flight Check Tool will generate a report to help the Polarity Customer Success team plan your v5 upgrade. The tool will generate a report that includes:
Analyst Telemetry Check
Authentication Scheme Check
Auto-Updates Check
Config.js TLS Options Check
Global Proxy Check
Integrations Check
Elastic/Splunk RPM Agent Check
Node Extra CA Certs Check
Operating System Check
PostgreSQL SSL mode Check
Polarity Version Check
Redis Env Var Check
SMTP Check
RPM Requirements Check
SSL Certificate Check
Polarity User Creation Check
Polarity CLI Integration Search Tool Check
Polarity Integration Auto Subscribe Check
Polarity CSV Loader Check
Polarity Annotation Manager Check
Usage
Installation
This CLI tool is built on NodeJS and should be run on your Polarity Server. Once complete the script will generate an upgrade report called polarity-upgrade-report.txt
. You will need a NodeJS runtime > v12.
To begin, download the tool, and untar it.
Check the SHA256:
Untar the tool and change into the directory:
To run the CLI tool ensure the polarity-integration-auto-subscribe.sh
script is executable.
You can now run the CLI tool and pass in the required options. Here is an example with the minimum required options. As tool connects to your Polarity Server over the REST API, you will be prompted for a a valid local Polarity admin username and password. The tool will connect to localhost by default which requires the --rejectUnauthorized=false
option to be set.
This command will generate a report file called polarity-upgrade-report.txt
. Please copy this file and provide it to your Polarity Customer Success representative.
All Options
Troubleshooting
You may see a "self signed certificate" error right after providing your Polarity admin credentials like this:
This error means the SSL certificate was not trusted (this will happen if you use the default https://localhost
url to connect locally, or if the SSL certificate on your Polarity Server is self signed). You can easily work around this issue by providing the --rejectUnauthorized=false
option:
Last updated