• Install JAVA openjdk, required version is V21 minimum.

• No /opt/Redpeaks folder must exist, otherwise the install script will not install the application

• 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 Redpeaks with systemctl
  
  • systemctl start redpeaks

• Perform a configuration snapshot (recommended)
• Stop the service: systemctl stop redpeaks
• 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 Redpeaks with systemctl
  
• systemctl start redpeaks

• Once the service is started, visit http://localhost:8888 to access the application
• Default credentials
  • User: admin
  • Password: admin

• By defaults Redpeaks servers listens on 8888 for HTTP and 8443 for HTTPS
• You can change those ports in the /opt/Redpeaks/bin/setenv.sh
  • -Dport.http.nonssl=8888
  • -Dport.http.ssl=8443

• You can modify dedicated application heap memory from setenv.sh file
• Set the Xmx parameter using a sed command as such:
  • sed -i 's/Xmx2048/Xmx4096/g' setenv.sh

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

* 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

• 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

• 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

• To start, stop or restart Redpeaks, it is recommended to use its service controls directly.
  • systemctl start/stop redpeaks
• A restart can also be triggered from the Settings→Admin menu→Maintenance

• To use a proxy for outgoing HTTP and HTTPS connections, edit bin/setenv.sh file from redpeaks server
• Add to the JAVA_OPTS variable the following parameters:
  • -Dhttps.proxyPort=<HTTPS proxy port> and -Dhttps.proxyHost=<HTTPS proxy host>
  • -Dhttp.proxyPort=<HTTP proxy port> and -Dhttp.proxyHost=<HTTP proxy host>

• Stop redpeaks service: systemctl stop redpeaks
• Remove service file: rm /etc/systemd/system/redpeaks.service
• Remove Redpeaks application and data: rm -rf /opt/Redpeaks
• Remove Redpeaks user and group

• Java OpenSDK 21 is a prerequisite for using V7.0.
  • If you are on RHEL/Red Hat, you can upgrade Java using dnf sudo dnf install -y java-21-openjdk
  • If you are on Debian/Ubuntu (or any non-RHEL distro), use the provided ./install_java.sh script to upgrade Java (internet access required)
  • If you updated java, make sure you switched the JVM using alternatives –config java
  • Important: Make sure the collector's service user has the authorizations to execute the VM.
    • sudo -u redpeaks java -version
    • If the command returns an error, you need to fix VM's installation folder authorization, user must have read & execution privileges on the entire folder, not only the binaries.

• Deploying a V7.0 base version over a V6.8 can only be done from Linux shell.
• The Redpeaks update package provides a migration script which will do the following:
  • Install a new instance of the promonitor collector, now rebranded Redpeaks, within a new folder.
  • Create a new service and service user (redpeaks)
  • Migrate pre-existing artefacts and configurations such as keystore, reports, drivers and snapshots to the new instance
  • Apply the latest snapshot in the new instance to recover the existing monitoring configuration
  • Apply any existing license
• Existing plugins, integrations, agents and failover connections will continue working as before.
• Once the migration script is executed, no extra operation are required from within the web application.

• Before executing migration script, do the following:
  • Perform a configuration snapshot from Snapshot menu
  • Restart the promonitor service

• Log into the VM via SSH and run following commands:

systemctl stop promonitor
tar zxvf Redpeaks-7.X.X_yyy.tar.gz
./migrate.sh

• Follow the instructions of the migration script

• After validating that the new installation performs correctly, you can remove the former application
• Important: You must at least disable the former promonitor service to avoid its restart upon VM reboot.

systemctl disable promonitor
rm -rf /opt/Pro.Monitor*

Note:

• The update script has been tested on most Linux distributions, however, it might sometimes fail to start the service of the new instance.
• If that happens, try restarting the service.

• Shall anything goes wrong and you need to revert from V7.0 to V6.8, just restart promonitor service
• The former application is left untouched by the migration.

This procedure applies when you already have an existing Redpeaks instance
and want to replace it with a fresh installation on a new virtual machine.

• Perform a snapshot of the existing configuration and save the snapshot file locally using your browser.
• Install a new instance of Redpeaks on the new VM.
• Copy the file certificates/.keystore from the old instance to the new one (required if self-signed certificates were previously imported).
• If you implemented SNC, you must also copy SNC folders in the new instance, preserving the path
• Start the new instance.
• Navigate to the Snapshot menu, then upload and apply the snapshot file.
• At this stage, the previous configuration should be replicated on the new instance.
• Apply your license key(s). Existing license keys can be found on the old instance in snapshots/licenses.txt.
• Cockpit Integration:
  • If the collector was attached to a cockpit, it will appear automatically as a new collector.
  • You must reassign the groups to the new collector.