Skip to main content

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 default, a Windows service named “apache <version number>” is created at the moment the Apache server is installed.

This service can be controlled using the standard Windows mechanisms (Service Manager, Command Line).

IIS on Windows

You can stop/start IIS using the user interface (UI) or a command line.

From the IIS Manager :

1.       Open IIS Manager and navigate to the Web server node in the tree.

2.       In the Actions pane, click Start if you want to start the Web server or Stop if you want to stop the Web server.

From the Command line:

1.       Open an elevated command-line window.

2.       At the command prompt, type net stop WAS and press ENTER; type Y and then press ENTER to also stop W3SVC.

3.       To restart the Web server, type net start W3SVC and press ENTER to start both WAS and W3SVC.

Backup your environment

In order to backup all customer specific configuration/ data you need to backup following directories and files on a regular basis:

Directory

Content

$PRODUCT_HOME/data

Product generated data

$PRODUCT_HOME /config/custom

Custom configuration files

$PRODUCT_HOME /security

User & group settings

$PRODUCT_HOME/product.lic

Product license file

$PRODUCT_HOME/Tools/etc

LDAP integration configuration

Impact of application shutdown

If the ProactivePack application is not available (because of http server shutdown, network outage, etc), the ProactivePack console is obviously unavailable. However, there is no impact on the the target monitoring solution and the backend processes that may be in place.

-          Any data provided through the “DDA Editor”, modules remain  in their respective location (cell/BHOM/BigPanda etc) and can be in the worst case edited directly with the monitoring tool

-          All blackouts created in ProactivePack remain and can be in the worst case be edited using the monitoring tool

-          QuickQueries: Events are still imported in the database. If the database, or the server where the import script runs, are unavailable, import will resume when the database/server are available again. If duration of the unavailability of the database or the server is inferior to the event retention period (as configured in the cell), there should be no loss of information.

 

Back to top