4. Install on Linux

Installation prerequisites

First of all, please check java version. It should be >= 1.8.0_172

rpm -qa | grep jre
jre1.8-1.8.0_151-fcs.x86_64

If needed, update or install jre, using :

For an installation

sudo rpm -ivh jre-8u172-linux-x64.rpm

For an upgrade

sudo rpm -Uvh jre-8u172-linux-x64.rpm

No /opt/Pro.Monitor folder must exist, otherwise the install script will not install the application

Check if Network Firewall is enabled

On CENTOS or REDHAT

systemctl status firewalld

If the state is Active and Loaded, this means that it has been started

Please see the firewall Section below

Other Linux

sudo iptables -L

This will shows the firewall rules, check if rules are applied to the different chains. Please see the Firewall Section below

Install or Upgrade Pro.Monitor using Shell Script

Install Pro.Monitor

Download the TarGZ file on the server. As root user, un-compress the archive in /home/[loggued user] DO NOT USE /OPT TO UNTAR !:

tar -zxvf [ARCHIVE FILE NAME]

Then, run installation script as root, wait for the installation to be finished in /opt (default setting)

./install.sh

Start Pro.Monitor with systemctl

systemctl start promonitor

Update Pro.Monitor

Perform a configuration snapshot (recommended)

Download the TarGZ file on the server. As root user, un-compress the archive in the /home/[loggued user] directory : DO NOT USE /OPT TO UNTAR !

tar -zxvf [ARCHIVE FILE NAME]

Then, run update script as root, wait for the update to be finished in /opt (default setting):

./update.sh

Start Pro Monitor with systemctl

systemctl start promonitor

Install or Upgrade Pro.Monitor using RPM Package ON AGENTIL INTERNAL NETWORK ONLY

First, create in /etc/yum.repos.d/ as super user the repo file : agentil.repo

To install or update promonitor, use “yum” as detailled below

To install : yum install promonitor

To update : yum update promonitor

To check is promonitor is running, start and stop, use systemctl command

To stop : systemctl stop promonitor

To start : systemctl start promonitor

To get Status : systemctl status promonitor

Firewall

To be able to configure and use Pro.Monitor, the admin port (by default 8888) should be open

On REDHAT / CENTOS 7

Use the following command to open port 8888 and reload configuration

sudo firewall-cmd --zone=public --add-port=8888/tcp --permanent

sudo firewall-cmd --reload

Other Linux

Use the following command to open port 8888

sudo iptables -I INPUT -p tcp -m tcp --dport 8888 -j ACCEPT

sudo service iptables save

Distant DB settings

Distant DB settings is optional. Local DB can handle any kind of size of configurations

To configure Pro.Monitor to use a distant DB, you will have to change the settings in conf/server.xml

Look for “Resource” tag and modify it as such:

MYSQL:

<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="100" maxIdle="30" maxWait="10000" validationQuery="SELECT 1" name="jdbc/DsWepAppDb" password="[DB user password]" type="javax.sql.DataSource" url="jdbc:mysql://[DB server]/[DB name]" username="[DB user]"/>

MSSQL:

<Resource auth="Container" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" maxActive="100" maxIdle="30" maxWait="10000" validationQuery="SELECT 1" name="jdbc/DsWepAppDb" type="javax.sql.DataSource" url="jdbc:sqlserver://[DB server URL];databaseName=[DB name];user=[DB user];password=[DB user password];"/>

Finally, edit webapps/ROOT/WEB-INF/classes/applicationContext.xml and look for property <prop key=“hibernate.dialect”>. Change it accordingly:

MYSQL:

<prop key="hibernate.dialect">org.hibernate.dialect.MySQLDialect</prop>

MSSQL:

<prop key="hibernate.dialect">org.hibernate.dialect.SQLServer2008Dialect</prop>

Pro.Monitor life cycle

To start, stop or restart Pro.Monitor, it is recommended to use its service controls directly.

A restart can also be triggered from the Administration->System menu