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 following page will display :
Contact ProactivePack support to get a license file and upload it for each ProactivePack instance
Authentication
Local authentication
By default, the ProactivePack instances of the appliance use the ProactivePack "local" authentication . A user "admin", member of the admins group, is presented out of box.
Other authentication mechanisms
Refer to the ProactivePack Administration Guide to know about other authentication options and how they are configured.
BMC TrueSight Operations Management configuration
mcell.dir configuration
TProactivePack uses a mcell.dir file to know about the cells that must be connected. Please note that by default this directory file is shared between the QUAL and PROD ProactivePack instances (This can be changed)
To do this:
· Copy/paste the cell entries you need from the TrueSight mcell.dir file
· Save the content by pressing the “save” button at the bottom of the screen.
TrueSight configuration
TrueSight Event Management cell
Several ProactivePack features require the TrueSight event management cell to include additional resources.
These specific classes, collectors and rules are located in the $PRODUCT_HOME/Tools/kb folder of ProactivePack.
The classes must be loaded in the order set in the table below. For more details refer to the ProactivePack administration guide and to your TrueSight administrator.
|
Filename |
Content |
Usage |
|
classes/ProactivePack_Events.baroc
|
General event classes definitions |
Optional for QuickQueries and Data Replication
|
|
classes/ProactivePack_Data.baroc
|
General data classes definitions |
Optional for QuickQueries Required for Data Replication |
|
classes/Maintenance_Enums.baroc |
Blackout Enumeration definitions |
Mandatory for Blackout |
|
classes/Maintenance_Event.baroc |
Blackout Event classes definitions for Event Management cell |
Mandatory for Blackout |
|
classes/Maintenance_Custom_Event.baroc |
Optional set of Blackout class definitions that must be loaded in case custom blackouts are used AND must be managed from the CLI |
Optional for Blackout |
|
classes/Maintenance_Data.baroc |
Data classes definitions for Blackout |
Mandatory for Blackout |
|
classes/Maintenance_Impact.baroc |
Event and Data classes definitions for Impact Management cell |
Optional for Blackout |
|
|
|
|
|
rules/ProactivePack_QuickQueries.mrl
|
Rules to manage events sent by the db import script |
Optional for QuickQueries |
|
rules/Maintenance_Event.mrl |
Rules for event management |
Mandatory for Blackout |
|
rules/Maintenance_Custom_Event.mrl |
Set of rules that must be loaded in case custom blackouts are used AND must be managed from the CLI. |
Optional for Blackout |
|
rules/Maintenance_Impact.mrl |
Optional - Rules for Impact management. |
Optional for Blackout |
|
collectors/Maintenance_collectors.mrl |
Blackout Management specific collectors for event management. |
Optional for Blackout |
|
records/Maintenance_options.baroc |
Blackout options for both Event and Impact Management |
Mandatory for Blackout |
|
collectors/ProactivePack_cols.mrl |
ProactivePack collectors |
Optional for QuickQueries and Data Replication |
For Blackout management, the IM_POLICY definition in the out-of-box KB must also be changed, please refer to the administration guide.
TrueSight Presentation Server
Required only if you will use the Self-Service Monitoring Portal module.
For Self-Service Monitoring, the following configuration change must be applied.
The TrueSight Presentation Postgres database (host and https port) must be accessible from the ProactivePack server. This access is disabled by default in TrueSight. To enable :
o Open the file $TRUESIGHTPSERVER_HOME/truesightpserver/data/pgsql/pg_hba.conf file on the TrueSight Presentation Server
o Edit the file and add an entry as follows in the IPv4 local connections (can also be much more restrictive if local security needs it):
host truesight all 0.0.0.0/0 trust
o Restart the TrueSight Presentation Server
Integration
i Required only if you will use the Self-Service Monitoring Portal module.
To allow ProactivePack to connect to TrueSight for SelfService Monitoring Portal (using TrueSight PostgreSQL DB and Rest API), the following configuration should be set in SelfServiceMonitoringPortal (ProactivePack Administration => Modules => SelfServiceMonitoringPortal => Edit)
1. PGSHost: TrueSight postgreSQL host (typically the TSPS hostname)
2. PGSPasswd: TrueSight postgreSQL password (as set during TSPS installation)
3. RESTAPIHost: TrueSight REST API host (typically the URL that you would use to connect to TSPS)
4. user: TrueSight presentation server user (this user needs to have full access to TrueSight)
5. password : TrueSight presentation server user password
BMC Helix Operations Management
The connection strings to BHOM must be supplied in the Global configuration. To do so, navigate to Administration => ProactivePack => Modules => Administration => ProactivePack => Edit, and fill-in the connection strings of BHOM in the HELIX section.
The account of the access key must have administrator access into BHOM.
Save the changes.
To enable usage of the Self-Service Monitoring Portal for BHOM, navigate to Administration => ProactivePack => Modules => SelfServiceMonitoringPortal => Edit, and enable the module. Also provide the username associated to the access key and his group :
Save the changes.
Verifying the configuration
To check if all prerequisities and connections are operational, navigate to
ProactivePack Administration -> About -> Additional Information -> Prereqs validation
