The Knowledge Base uses a defined directory structure to organize its files and executables. The Knowledge Base directories are in the following locations:
■ The Knowledge Base used by the cell during runtime is located in
%MCELL_HOME%\etc\CellName\kb on Windows platforms and in
$MCELL_HOME/etc/CellName/kb on UNIX platforms.
NOTE
The SIM code of the unified KB is active only if the cell is configured as a SIM cell and the ServiceModelEnabled parameter of the MCELL_HOME/etc/mcell.conf file is set to Yes.
For additional information about the mcell.conf parameters, see Appendix B, “mcell.conf file parameters.”
The Event Management-only KB, stored under MCELL_HOME/etc/default/EM/kb, remains for backward compatibility with versions of the mcrtcell CLI older than version 7.2.00. It contains the KB elements used by Event Management to process events.
Knowledge Base directory structure
■ The template Knowledge Base resides in the MCELL_HOME\etc\default\SIM or MCELL_HOME\etc\default\EM directory. The Knowledge Base available (EM only or both EM and SIM) will depend on the type specified when the cell was created.
Cells are created during installation of a BMC Impact Manager instance or by using the mcrtcell command. For information about this command, see “mcrtcell—
Creating a new cell” on page 231.
Figure 10 lists the directory structure for a Knowledge Base.
In the Knowledge Base, each subdirectory is labeled to indicate the type of files or programs it stores, as listed in Table 15 on page 68.
NOTE
The environment variables created during installation that define paths to BMC Impact Manager configuration files and executables are listed in the BMC Impact Solutions Installation Guide.
Figure 10 Knowledge Base directory structure kb
\bin
\A
\h1
\l2
\p4
\s5
\w4
\classes
\collectors
\data
\lib
\records
\rules
Knowledge Base directory structure
Table 15 Knowledge Base subdirectories (part 1 of 2) Knowledge
Base
subdirectory Description
bin stores the external scripts that can execute during rule processing and actions that can be run from BMC Impact Explorer
The bin directory organizes the scripts and programs in subdirectories specific to the appropriate operating system, as follows:
■ A—independent, all UNIX, or non-Windows
■ h1—HP-UX
■ l2 —Linux
■ p4 —AIX
■ s5 —Solaris
■ w4 —Windows
The .load file in the bin directory specifies the order in which external scripts or programs are presented to clients. Actions are defined in .mrl files. There is one default file, .load, in the bin directory. Actions and their syntax are described in the BMC Impact Solutions Event Management Guide.
classes stores event class, data class, and interface definitions
Classes are stored in .baroc files. The .load file in the classes directory specifies the order in which classes are loaded. Parent classes must be loaded prior to child classes.
Event and data classes are described in the BMC Impact Solutions Knowledge Base Development Reference Guide.
collectors stores collector rule definitions
Collector definitions are used to organize the event lists that are viewed in the BMC Impact Explorer console. Collector rules are defined in .mrl files. Collectors and their syntax are described in BMC Impact Solutions Event Management Guide.
data instances of dynamic data stored in files that are loaded when the cell is initialized
Dynamic data instances are stored in .baroc files. The .load file indicates the order in which the files are loaded into the cell. After the values are loaded into the cell any changes are
maintained in the mcell.db. Dynamic data objects and their syntax are described in the BMC Impact Solutions Knowledge Base Development Reference Guide and in the BMC Impact Solutions Event Management Guide.
lib stores primitives and functions used in the Knowledge Base
For example, the SIM Knowledge Base contains the following files that cannot be modified:
■ sim.wic—contains the compiled implementation of primitives and functions that are loaded by the cell at startup
■ sim_decl.wic—contains the compiled definitions for primitives and functions; it is loaded by the compiler to compile rules that reference SIM primitives
For more information about functions and primitives, see the BMC Impact Solutions Knowledge
Knowledge Base directory structure
Table 16 lists the file extensions and directory location for the each of the components contained in a KB.
records stores global record definitions, which store dynamic information across all rule phases A global record stores persistent dynamic information in a .baroc file. Many rule processing phases use global records for retrieving dynamic information. The .load file indicates the order in which the files are loaded into the cell. The default copy of record definitions is stored in baroc files in the records directory. After the values are loaded they are maintained in the mcell.db. Dynamic data objects and their syntax are described in the BMC Impact Solutions Knowledge Base Development Reference Guide and in the BMC Impact Solutions Event Management Guide.
rules stores the rule definitions for the Knowledge Base
The source for rule definitions are the files with an .mrl extension. The compiled versions of rules are contained in files with the .wic or .pkg extension. The .load file indicates the order in which the rules are loaded into the cell. Rules and their syntax are described in the BMC Impact Solutions Knowledge Base Development Reference Guide and in the BMC Impact Solutions Event Management Guide.
Table 16 Knowledge Base file extensions and directories
Component File extension Directory
event classes .baroc kb\classes
data classes .baroc kb\classes
data instances .baroc kb\data
global records .baroc kb\records
rules .mrl kb\rules
collectors .mrl kb\collector
action executables .mrl kb\bin
service model class definitions .baroc kb\classes
interface classes .baroc kb\classes
scripts and programs not applicable kb\bin\platform Table 15 Knowledge Base subdirectories (part 2of 2)
Knowledge Base
subdirectory Description