Configuring the Normalization Engine
You can configure the BMC CMDB Normalization Engine parameters from the CMDB User Interface (UI). If you are in a server group environment, select the required AR server from the Select Server drop-down list. If you have a stand-alone environment, the required server name is automatically displayed.
To configure the Normalization Engine from the CMDB User Interface
- From the CMDB Dashboard, go to Configurations > Core Configurations.
- The left pane provides tabs for all the CMDB components, such as CMDB Engine, Normalization, and so on.
- Click Normalization to view all the normalization-related parameters in the right pane. An "i" icon is available next to a parameter that contains a tool-tip about the parameter usage. This helps you understand a parameter before setting its value. Parameters that already contain values are the default values. For example, the Maximum Threads for Continuous Jobs parameter contains the value 10, which is the default number of threads provided for continuous jobs.
- The normalization parameters are divided into two tabs, Global Configurations and Plugin Server Configurations, for ease of configuration.
- After you set values for the required parameters, click Save.
The following table describes the Normalization Engine parameters.
Setting in the AR Configuration file
|History Interval for Continuous Jobs||Specifies the History Interval in hours or days for continuous jobs.|
|Time Threshold for Continuous Jobs||Defines the number of seconds that must elapse after which the continuous jobs will start running.|
|Events Threshold for Continuous Jobs||Defines the number of events that must occur after which the continuous job will start running. An event is when a CI is created or updated.|
|Maximum Threads for Continuous Jobs||Enter the maximum number of threads to be allowed in the thread pool for continuous jobs.|
|Definition Check Interval|
Defines an expiration period for the Reconciliation Engine's cache of job definitions.
Example: If you change job, activity, precedence, or merge definitions, and then run a job, you might not see the results after the cache expires. Setting an expiration for the cached definitions helps to improve performance and reduce log size.
Batch Maximum Instance Per Thread
Defines the maximum number of instances of CIs and relationships allowed per thread for normalization. This value is also known as chunk size.
|Data Check Interval|
|Maximum Threads for Batch Jobs||Specifies the maximum number of threads to be allowed in the thread pool for batch jobs.|
For setting up Normalization Engine logging, see Contents of the logs.