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.



Installation Steps

To be able to install NetVizura, you will need a root privileges.

To install NetVizura follow these steps:

Step 1: Download and execute Centos 7 prerequisites script:

su -
yum install wget -y
wget https://www.netvizura.com/files/products/general/downloads/netvizura-4.7.3-prerequisites-centos7.sh --output-document=/tmp/netvizura-prerequisites-centos7.sh
bash /tmp/netvizura-prerequisites-centos7.sh


Step 2: Installing NetVizura package

Download NetVizura RPM package from NetVizura website to NetVizura server's /tmp directory and execute the following command:


yum -y localinstall /tmp/netvizura-package.rpm


Step 3(optional): Install Elasticsearch

wget https://www.netvizura.com/files/products/general/downloads/elasticsearch-prerequisites-centos.sh --output-document=/tmp/elasticsearch-prerequisites-centos.sh
bash /tmp/elasticsearch-prerequisites-centos.sh


To learn more about why this is an optional step at the moment read Why is Elasticsearch currently just an option?


Step 4: Verify installation


Post Install Steps

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 RAMPostgreSQLTomcatOS
4 GB2 GB1 GB1 GB
16 GB10 GB5 GB1 GB

Tweaking PostgreSQL

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 GuidePostgreSQL Tuning Guide, this article and this book.

In order to apply following tweaks edit file /var/lib/pgsql/PG_VERSION_NUMBER/data/postgresql.conf. You will need to restart the PostgreSQL service after done editing with command: service postgresql restart. 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.

Tomcat Memory Allocation 

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 RAMTomcat
3 GB1 GB
4 GB1 GB
16 GB5 GB

However, if you need to tweak Tomcat RAM allocation differently (the example for 2048MB):

  1. Edit file /etc/tomcat/conf.d/netvizura.conf
  2. Locate JAVA_OPTS environment variable that defines memory This line looks something like the following:
    JAVA_OPTS="${JAVA_OPTS} -Xmx1024m -Xms1024m"
  3. Modify the -Xmx and -Xms to the same amount. This should look something like:
    JAVA_OPTS="${JAVA_OPTS} -Xmx2048M -Xms2048M"
  4. Save the file and restart Tomcat: systemctl restart tomcat.service
    <?xml version='1.0'?> <!DOCTYPE fontconfig SYSTEM 'fonts.dtd'> <fontconfig> <alias> <family>serif</family> <prefer><family>Utopia</family></prefer> </alias> <alias> <family>sans-serif</family> <prefer><family>Utopia</family></prefer> </alias> <alias> <family>monospace</family> <prefer><family>Utopia</family></prefer> </alias> <alias> <family>dialog</family> <prefer><family>Utopia</family></prefer> </alias> <alias> <family>dialoginput</family> <prefer><family>Utopia</family></prefer> </alias> </fontconfig>























In case you have installed newer version of PostgreSQL, use different PostgreSQL service name, that matches your PostgreSQL version, in the commands from the Step 3.