Classification filtering

Classification filtering allows you to exclude CIs of a particular classification from being imported.

This provides a lower level of control over data filtering than authorized space promotion scope filtering provides, but it provides some performance improvement if unneeded classifications are identified and filtered. This is recommended for small to medium sized environments.

To prevent CIs of a particular class from being imported, set the depth value for that CI type to negative one (-1). Note that if no depths are set to -1, then no filtering will be applied.

For example, suppose you want to manage the CIs in a certain top-level class, as well as some of the related CIs. Perhaps this top-level class has three child classes, and you want to manage two of them, as well as their children, but you do not want to manage CIs in the third child class. You set the depth for the top-level class to three, and then set the depth for the third child class, the one you do not want to manage, to -1. Do not set a depth value for the other two child classes. With those settings, CIs of the top-level class are imported, along with CIs of the two classes that do not have their own depth values, and CIs of the child classes of those two classes. CIs of the third child class, whose depth was set to -1, are not be imported.

When you exclude a CI class from being imported, the relationships between the CIs that precede it and the CIs that follow it in the tree are not imported. Only relationships between CI classes that are contiguous from the top level down are included.

As a best practice, certain CI types are initially set (out of the box) to be filtered out. This is controlled by un-commenting (or removing the double slash "//") in each desired line in the ccmdb.properties file. Enabling for filtering, or un-commenting, the line with the value set to -1 will filter out these CIs.

Note: The ccmdb.properties file contains lines for all of the classifications. Initially, the following list of classifications are un-commented so these CIs will be filtered out. You can change the ccmdb.properties file to filter more or less CIs, as desired:

  
APP.CONFIGFILE=-1
APP.DB.DB2.DB2DATABASECONFIGVALUE=-1
APP.DB.DB2.DB2INSTANCECONFIGVALUE=-1
APP.DB.DB2.DB2SYSTEMCONFIGVALUE=-1
APP.PROCESSPOOL=-1
CORE.LOGICALCONTENT=-1
DEV.DISKPARTITION=-1
DEV.MEDIAACCESSDEVICE=-1
DEV.MEDIAACCESSDEVICEDEV.STORAGEVOLUME=-1
SYS.AIXSOFTWARECOMPONENT=-1
SYS.DATAFILE=-1
SYS.SOFTWARECOMPONENT=-1
SYS.WINDOWS.WINDOWSSERVICE=-1
SYS.ZOS.ZREPORTFILE=-1

Note: In previous releases of Maximo IT, the preceding classifications might not be enabled to filter out these CIs, in which case you would need to change the ccmdb.properties file to filter out any desired CIs.

Note: Also note that if you have upgraded Maximo IT from a previous release, the ccmdb.properties file is not upgraded and might need to be changed to filter out any desired CIs.

To change any of these CI types to be included (not filtered out), edit the ccmdb.properties file and comment (add the leading double slash "//" to) the desired classification line. For example:

//APP.CONFIGFILE=-1

(Comment out a line instead of deleting a classification line, so that you can easily un-comment it later as needed for future filtering.)

Before you activate a CI type, be sure to check the value specified in the ccmdb.properties file to verify that the desired number of child classes will be imported.