For security reason, make sure that your server or VM doesn't have anything installed on it before NetVizura installation. Other software of services running on the same server can impact installation. |
Before installing NetVizura make sure to set the time on your server correctly. Time change after the installation will invalidate the license! |
NetVizura requires working connection to the internet to install required dependent software. After installation is successful you can turn off internet access for NetVizura server. |
Netvizura depends on OpenJDK 8, Tomcat 8.0.14 or higher and PostgreSQL 12 or higher. NetVizura relies on 3rd-party repositories for installation of these software packages. The installation process has been tested on Debian 10 and Debian 11. It is important that Debian is 64-bit OS. |
To be able to install NetVizura, you will need a root privileges. |
To install NetVizura follow these steps:
Step 1: Installation of 3rd-party repositories and prerequisite software
Download and execute Debian prerequisite installation script:
su apt update -y ; apt-get -y install sudo wget wget https://www.netvizura.com/files/products/general/downloads/netvizura-5.4-prerequisites-debian.sh --output-document=/tmp/netvizura-prerequisites-debian.sh bash /tmp/netvizura-prerequisites-debian.sh |
Step 2: NetVizura package installation
/tmp
directory and execute the following command:sudo dpkg -i /tmp/downloaded_file_name.deb |
After installation tweaking of configuration files is required in order to utilize the installed RAM to the fullest extent. The main consumers of RAM are operating system, PostgreSQL database and Tomcat. General rule for distributing memory is to split it in ratio 2:1 between PostgreSQL and Tomcat with 1 GB or more reserved for operating system. For instance:
Installed RAM | PostgreSQL | Tomcat | OS |
---|---|---|---|
4 GB | 2 GB | 1 GB | 1 GB |
16 GB | 10 GB | 5 GB | 1 GB |
Tweaking PostgreSQL for best performance is a topic on which many books were written, but the following are some common sense suggestions. For the curious ones recommended reads (among countless others) are PostgreSQL Optimization Guide and PostgreSQL Tuning Guide.
In order to apply following tweaks edit file /etc/postgresql/PG_VERSION_NUMBER/main/postgresql.conf
. You will need to restart the PostgreSQL service after done editing with command: systemctl restart postgresql
. Almost all of the following parameters are commented with carron character (#
). Be aware that if you comment out the parameter that has been changed, PostgreSQL will revert to the default value.
In the following example it is assumed that 4 GB of RAM is allocated for PostgreSQL.
|
During installation NetVizura automatically allocates memory for Tomcat process. The amount allocated to Tomcat process is calculated according to the formula:
(RAMtotal - 1GB) / 3
but no less than 1GB.
For instance:
Total RAM | Tomcat |
---|---|
3 GB | 1 GB |
4 GB | 1 GB |
16 GB | 5 GB |
However, if you need to tweak Tomcat RAM allocation differently (the example for 2048MB):
/etc/default/tomcat8
(Debian 9) or /etc/default/tomcat9
(Debian 10)
JAVA_OPTS
environment variable that defines memory and uncomment it if it is commented. This line looks something like the following:JAVA_OPTS="${JAVA_OPTS} -Xmx1024m -Xms1024m +UseConcMarkSweepGC"
-Xmx
parameter to allocate additional memory to Tomcat. Additionally, set parameter -Xms
to the same amount. This should look something like:JAVA_OPTS="-Djava.awt.headless=true -Xmx2048M -Xms2048M -XX:+UseConcMarkSweepGC"
Save the file and restart Tomcat: systemctl restart tomcat8
(Debian 9) systemctl restart tomcat9
(Debian 10)
By default, the memory limit for Elasticsearch should be set to 30% of RAM. If you need it to be set to any other value, edit the file: /etc/elasticsearch/jvm.options, and set values -Xms and Xmx to desired size. Then, restart the Elasticsearch and Tomcat services.