Depth and filtering of CI data

The depth value specified for a CI type specifies the number of classifications to be included when importing actual CI data. You can also specify that some types should not be included.

You can specify a depth value for each CI type. The depth specifies the number of classifications to be included when importing actual CI data using the TADDMadapter. By subtracting one from the depth value, you can calculate the number of relationships that will be traversed in your CI tree during data importing, and therefore how many subclasses will be imported.

For example, if the depth for the Computer System classification is set to three, the following three classes will be imported:

Depth level	Class
1	Computer System
2		Operating System
3			Software

In this example, with a depth of three, two levels of relationships are traversed: one between the Computer System and Operating System classifications, and another between the Operating System and Software classifications.

There is a default value for CI type depth, which is used for all classifications that do not have a depth specified. The initial value for this default depth is three (3). You can modify the default value if you wish to include more or fewer classifications when actual CI data is imported. If you increase the depth, the import process will take longer to complete.

The default depth value, and the depth values for all CI types, are maintained in the ccmdb.properties file on the Integration Composer server. This file is located in installation_dir\data\properties\provider, where installation_dir is Integration Composer on Windows operating systems and Integration_Composer (with underscore) on other operating systems.

When you import actual CI data using the ImportIDML tool, the depth level and other filtering values are not used.

To check the current value for the level of depth, look at the mxe.db.queryDepthLevel property in the ccmdb.properties file.

To change the default value for the depth, follow these steps:

If Integration Composer is running, close all open windows and sign out of the application.
Edit the file installation_dir\data\properties\provider\ccmdb.properties.
Modify the value of the mxe.db.queryDepthLevel property.
Save the file.

In addition to setting the default depth, you can specify a value for each top-level CI. In some cases you will also need to set a depth value for a CI that is not at the top level. You can also specify that you do not want CIs of a certain type imported, even though they are related to a top-level CI and would be included according to its depth value. All these values are included in the ccmdb.properties file.

After determining depth values, you should configure filtering options for the CI data. There are two levels of filtering available: classification filtering and authorized space and promotion scope filtering. To specify which type of filtering should be applied, update the ccmdb.actualci.filtering.level property in the ccmdb.properties file. The following are the possible values:

0: Filter classifications where depth is set to -1 in this property file. This enables classification filtering.
2: Default value. Filter classifications and attributes based on the authorized CI space and promotion scopes. This enables authorization space filtering.

Feedback