Loading and unloading KMs


Installing BMC PATROL for SAP Solution Manager places the KM files into the PATROL directory, but it does not place them into the PATROL Console. You must load the files into the PATROL Console so that the BMC PATROL for SAP Solution Manager applications classes, commands, and parameters appear in the PATROL Console.

BMC PATROL for SAP Solution Manager .km files are grouped together in the following .kml files:

  • ssm.kml - Groups together all KM files responsible for basic discovery of SAP Solution Manager systems. You load this .kml file after completing product installation.
  • ssm_d.kml - Groups together the KM files responsible for dynamic discovery of CCMS parameters. You load this .kml file after basic discovery of all non-dynamic application classes has taken place and after you receive a reminder message in the System Output Window.

Note

If you want your KMs to continue collecting data even when there is no console running, preload your KMs. A preloaded KM is a KM that is loaded by the PATROL Agent at startup and runs as long as the PATROL Agent runs. To preload, add the ssm.kml and ssm_d.kml files to the agent's preload list in the pconfig variable preloadedKMs.

If you no longer want to use application classes that you previously loaded, you can use the unload instructions to remove (or delete) the corresponding .km or .kml files so that application classes no longer appear in your console. When you delete KM files using a console, the file is not deleted from the patrol\knowledge directories on the PATROL Console or the PATROL Agent computers.

Instructions differ for the various types of PATROL Consoles.

Before you begin

Before you load KMs, perform the following actions:

  1. Start the PATROL Console.
  2. Start a PATROL Agent on each computer that you want to monitor.
  3. To protect the integrity of KM hierarchy over time, make sure that knowledge downloading is inactive. To do this, select Options > Preferences, and on the Configuration tab select Prevent downloading knowledge on Developer connection.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*