Search Results

 Consider using the ProactivePack appliance or container deployment and skip this part. See Deployment options    Server installation The contents of the package must be unzipped in DOCUMENT_ROOT/ProactivePack/ where DOCUMENT_ROOT is the ‘base directory’ of...

Direct upgrade is possible from any version from version 21.05 and above, 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 plat...

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...

Initial configuration Most of the steps below are not necessary if you use the ProactivePack appliance or container.       1. Open the ProactivePack console. By default, the “LOCAL” authentication is used. The username is “admin” and the default password is...

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...

Stopping/Starting 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 default, a Windows...

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...

Introduction The security of ProactivePack uses a system of users and groups to determine what permission users have in the product.  Users are first authenticated using one of the following mecanisms : Internal autentication : Performed at the level o...

Introduction The « Quick Queries » module allows the easy generation of event graphs and reports. Reports can be generated transparently out of events stored in a cell, or events stored in a separate SQL database. To run a quick query, you must define a time...

Common parameters The graph type is chosen from the main selector :   All types of quick queries share a series of same configuration options: The target data source, which can be a cell or the database :    The Quick Queries time window, whi...

Dashboards Dashboards let you combine several saved QuickQueries into single pages that can be set to refresh periodically. To create, select “Create new Dashboard” in the “Query Sets” page.   -          In the first screen : o   Specify the refresh rate ...

Queries and reports can be sent over email on a periodic basis. For this, open the context menu (wrench icon) for the object you would like to schedule. A dialog like below opens :     - Provide one or more email addresses separated by a comma or semic...

In order to integrate ProactivePack Dashboards or Queries in TrueSight Presentation Server, you can use the “Web Page” Dashlet in TrueSight Dashboards. The ProactivePack URL can be copied directly from the QuickQueries or Query sets menu:   Some options c...

The Quick Queries module can be used to query events from a database. In that case, events must of course be stored in that database. A script is provided under $PRODUCT_HOME/Tools/bin to enable the import of events into a database. Other mechanisms can be us...

Introduction Virtual slots allow the transformation of “real” slot values into “virtual” values – and vice versa. Virtual slots can be very powerful, but require some (limited) php coding to be configured. Virtual slots can be used e.g. for the following pur...

it is possible to configure custom actions to ease the creation of DDA entries based on events  selected in an event table report. When configured, the cross-launch will lead the user into the “add entry” dialog of an existing Data Editor module, with DDA slo...

The main configuration file for the Quick Queries module is $PRODUCT_HOME/config/custom/QuickQueries.conf. As for other configuration files, it can be edited from the ProactivePack console.   Parameter Description Default/typical value ...

All permissions must be set in the configuration file of the groups (either using the console or editing the <groupname>.conf files in $PRODUCT_HOME/security.   Permission Name Expected Value Description Configure 0 or 1 ...