CMDB Engine configuration settings


The parameters in the CMDB Engine section allow you to :

  • Configure cache settings in a server group environment
  • Configure orphan data settings
  • Configure data handling parameters
  • Configure inline normalization
  • Subscribe to an event

If you are in a server group environment, select the required AR System server from the Select Server drop-down list. If you have a stand-alone environment, the required server name is automatically displayed.

Function

Parameter

Description

Default Value

Setting in the AR Configuration file
(ar.cfg or ar.conf)

Configure cache settings

Cache Refresh Interval 

Defines the interval after which CMDB to refreshes its cache in the background. Changes you make to this parameter takes effect at the next refresh interval or engine task kill. 

Notes:

  • Set the value of this parameter to be greater than 60000 milliseconds (60 seconds). Else, the default value is taken.
  • To disable this parameter, set the value to minus one (-1). 

300000 milliseconds

CMDB-Cache-Refresh-Interval

Initial Delay for Cache Refresh

Defines the time after which the cache is refreshed after the server is started.

Note: Set the value of this parameter to be greater than 60000 milliseconds (60 seconds). Else, the default value is taken.

900000 milliseconds

CMDB-Cache-Refresh-Initial-Delay

Configure orphan data settings

ChunkedItem Cleanup Interval

Defines the interval at which the CMDB server performs orphan data checks. Changes you make to this parameter take effect at the next refresh interval or CMDB Engine task kill. 

Notes:

  • Set the value of this parameter to be greater than 60000 milliseconds (60 seconds). Else, the default value is taken.
  • To disable this parameter, set the value as minus one (-1). 

300000 milliseconds

CMDB-ChunkedItem-Cleanup-Interval

Initial Delay for Chunked Item Cleanup

Defines the delay to start checking for orphan data after CMDB server has started. 

Note: Set the value of this parameter to be greater than 60000 milliseconds (60 seconds). Else, the default value is taken.

900000 milliseconds

CMDB-ChunkedItem-Cleanup-Initial-Delay

Duration for Chunked Item in Cache

Defines the interval after which the data is treated as orphaned and the memory is reclaimed by the AR System. 

Note: Set the value of this parameter to be greater than 60000 milliseconds (60 seconds). Else, the default value is taken.

3600000 milliseconds

CMDB-ChunkedItem-Allowed-Period-In-Cache

Configure data handling parameters



 

Maximum Results Per Query

Defines the maximum number of results that are returned per query.

A value of 0 implies that the maximum results per query are unlimited.

Important: Setting this parameter to 0 for large models can lead to memory issues. Configure this parameter based on your system’s capacity and expected graph size.

Zero (0)

CMDB-Max-Results-Per-Query

Graph Walk Chunk Size

Defines the chunk size for the results returned by the graph walk API.

200

CMDB-Graph-Walk-Chunk

GQ Recursion Limit

Defines the number of levels of recursion for the CMDB graph query.

Important: Setting this parameter to 0 for large models can lead to memory issues. Configure this parameter based on your system’s capacity and expected graph size.

Zero (0)

CMDB-GQRecursion-Limit

Recursive Query For Graph Walk 

Used to disable the recursive query for the Graph Walk API. 

Possible values are True and False.

The recursive query is enabled, by default, for the Graph Walk API. 

You can disable the recursive query for the Graph Walk API by adding the CMDB-Use-RecursiveQuery-For-Graph-Walk parameter in the Centralized Configuration and setting its value to False.

For information about adding the Centralized Configuration settings, see Updating configuration settings by using the AR System Configuration Generic UI form. 

 

True

CMDB-Use-RecursiveQuery-For-Graph-Walk

(com.bmc.cmdb.server )

Default Impact Weight

Defines the default weight attached to an impact relationship. This value is used to configure the Impact Simulator to set default Impact weight in relationships when the hasImpact attribute is set to Yes

Zero (0)

CMDB-Impact-Weight-Default

Hard Delete Only if Marked for Delete

Specifies that, if a CI is to be hard deleted, it should be first marked for deletion.

Note: This setting does not apply to the CIs of classes from BMC.CORE.CONFIG namespace.

False

CMDB-Hard-Delete-Only-If-Marked-For-Delete

Validate Federation Source

Validates if data is present in Federated data store. Has values True or False.

If set to True, the CMDB Engine performs the validation around federation data sources.

True

CMDB-Validate-Federation-Source

Create Log Per Thread

Creates a separate log file for each thread of API/SQL/Filter Logs.

Zero (0)

CMDB-Log-Per-Thread

Allow Global BSSO Delete

Checks the out-of-the-box global instances of the three classes, BMC_BusinessService, BMC_ServiceOffering, and BMC_SERVICEREALIZEDBYOFFERING for deletion.

False

CMDB-Allow-Global-BSSO-Delete

Configure inline normalization

Enable Inline Normalization

If Inline normalization is enabled, the CIs are normalized as soon as it is created or modified in the CMDB. In this mode, CIs are normalized before it is saved in the CMDB.

This check box is selected by default so that the CIs are normalized as soon as it is created, updated, or modified.

Important

The normalization mode should be selected as Inline always, unless while normalizing large amounts of data, when the batch mode should be used. Use the batch mode and schedule it to run outside of peak hours to minimize the impact on users. 

True

CMDB-Inline-Normalization

Subscribe to an event

Enable Event Channel

Enables the subscriber to receive the event as soon as a CI is created, updated, or modified.

False

Event-Channel-Enabled

 

 

 

 

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