Advanced Search
Search Results
360 total results found
Access, users and passwords
Access Initially, the network IP is retrieved from DHCP. The DHCP provided address can be found using VMWare VCenter or in the VM console : The Appliance home page is available at https://<appliance IP>/ User and passwords Default users/pass...
System Configuration
In order to manage the appliance, a Webmin interface is available on https://<appliance IP>:1000/ It is also possible to log in to the machine itself using the “admin” linux user. The admin user can su to root (sudo su -) System keyboard layout The applianc...
DB Configuration
In order to manage the appliance Postgres DBs, a “pgadmin” interface is available on https://<appliance IP>/pgadmin4/ It is also possible to log in to the machine itself using the “dbadmin@localhost.com” user. You may need to change PostgreSQL sever to you...
ProactivePack configuration
In order to integrate ProactivePack with your BMC environment, basic configuration stepss should be followed as described below. License upload If no license is set or expired (a license file is required for each of the ProactivePack instances), the followin...
Components management
Apache server In order to restart http server, go to webmin / Bootup and Shutdown Select service you would like to restart; Click “Restart” at the bottom of the page: You can also manage stop/start/status using systemctl command l...
Legal notice
Copyright This document and software are subject to copyright. You must not reproduce or publish this document in whole or in part for commercial gain without the prior written consent of ProactivePack SARL. You may reproduce and publish this document in whol...
Release Notes
What is new in this version Global Improved sessions management REST API logout function REST API sample scripts (Linux) Container security vulnerabilities addressed Blackout Management REST API hardening and Sample script for BigPanda Stop perio...
Concepts
ProactivePack is a web-based application that provides IT Operations administrators and users with powerful tools that will help them in their daily tasks. Various modules co-exist in the ProactivePack platform. While the modules share a common infrastructu...
Architecture
The logical architecture of the solution is as follows. Core component The ProactivePack console is a web browser (Chrome, Internet Explorer, Firefox) Core component The ProactivePack server is the main server...
Deployment options
At high-level, ProactivePack can be deployed in 3 ways : The standard product installation consists in installing ProactivePack on a server provided by the customer The appliance is a pre-configured VMWare image that has the ProactivePack software preinsta...
General HW and SW Prerequisites
Consider using the ProactivePack appliance or container deployment and skip this part. See Deployment options Hardware requirements The software requires 10GB of disk space and a minimum of 4GB of RAM and 2CPU to run. Additional resources may be require...
Additional prerequisites by module
QuickQueries Prerequisites Consider using the ProactivePack appliance or container and skip this part ! See Deployment options PHP The PHP extensions of the corresponding database (mysqli, oci8, sqlsrv, pgsql) must be loaded. See corresponding sections b...
Required network ports
The following table summarizes communication ports that need to be open between the different ProactivePack components. As all ports can be configured, only the default or typical values are presented. Source Destination Port (default) ...
Installation
Consider using the ProactivePack appliance or container deployment and skip this part Server installation The contents of the package must be unzipped in DOCUMENT_ROOT/ProactivePack/ where DOCUMENT_ROOT is the ‘base directory’ of html pages on the web s...
Upgrading from version 21.05 and above
Direct upgrade is possible from version 21.05 onwards, using the ProactivePack console : Download the patch file Go to our download site https://dowloads.proactivepack.com Go to the "upgrade and patches" tab of the page Select the platform (Windows or ...
Upgrading from earlier versions
When there is no direct upgrade path, some manual steps are involved. We assume below that the current installation is under /path/current_ppack and you want to install a version XXYY Steps : Create a folder /path/ppackXXYY and unzip the new product file t...
Configuration basics
Initial configuration 1. Open the ProactivePack console. By default, the “LOCAL” authentication is used. The username is “admin” and the default password is “Ppack12345” 2. Navigate to “Administration” and choose “Modules” 3. In...
Console usage
Login/Logout To logout : - Click on your avatar icon in the top toolbar - Click on the right-most “exit” button : - Close your browser completely (not just the tab used for ProactivePack) User preferences - Cl...
General administration procedures
Stopping and starting ProactivePack ProactivePack only “runs” when its web server is running. Apache on Linux The default command to stop, start, or restart the Apache server on Linux is as follows : service httpd stop|start|restart Apache on Windows By ...
General configuration
Module reference The main configuration file for ProactivePack module is $PRODUCT_HOME/config/custom/Global.conf. Parameter Description Default/typical value [Global] section functionality Used to organize the modul...