Loading and unloading KMs

Before you can configure and use the installed product, you must load the relevant product .kml files. These files group product-related .km files into the BMC PATROL console so that the product, in the form of applications, commands, and parameters, appears in the PATROL console.

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

Before you begin

Before you load a Knowledge Module (KM), verify the following:

1. A BMC PATROL console is started.
2. A BMC PATROL Agent and Windows Azure services on each computer that you want to monitor are started.
3. Choose one of the following:
   • If you want BMC PATROL for Windows Azure to start automatically whenever you open the console, make sure the PATROL for Windows Azure files and the configuration file for the agent on the computer where the PATROL Agent is installed are loaded.

   • If you want to manually load PATROL for Windows Azure by using the console, make sure the PATROL for Windows Azure files on the computer where your PATROL console resides are loaded. 

     Warning

     Note

     If you want your KMs to continue collecting data even when there is no console running, preload your KMs. A preloaded KM is loaded by the PATROL Agent at startup and runs as long as the PATROL Agent runs. To preload, add the .kml file (or individual .km files) to the agent’s preload list in the preloadedKMs variable in the pconfig utility. To access the pconfig utility, see Accessing-the-pconfig-utility.

     The task of loading and unloading KMs differs, depending on the type of BMC PATROL console: