Population utility parameters

The following table describes the population utility parameters that you can specify in the population utility XML file.

Parameter

Description

CDBProfileName

Name of the CDB profile (CDB-cluster-profiles)

DataSourceName

Name of the data source (Connecting-to-a-CDB-cluster)

Platform

Name of the platform to which the business data extension belongs (Using-the-CDB-BDE-tool)

CSVInput

Name of the file that contains the business data you want to process

ErrorsOutput

Name of the file where error messages should be sent

NormalizeToExistingIntervals

Determines whether the input data will be normalized to existing intervals

True – Input data is normalized to those intervals that already exist in the specified data source.

False – Intervals are created exactly as specified.

Note

  • Specifying overlapping intervals of the same type (such as measurement or daily summary) where you do not match one of them exactly can cause unpredictable results.
  • For the normalization rules that apply to business data, see CSV-input-file-format-and-structure.

ResolveIncompleteKeys

Determines whether the population utility requires a complete set of key properties or can recognize a class instance based on incomplete information

True - The population utility attempts to recognize the correct class instance based on partial information provided in the CSV input file.

False - All key properties for all class instances (both those that already exist in BMC CDB and those that must be created during population) must be specified.

Note

For successful population of the BMC CDB database, the population utility must provide a complete set of key properties for each class instance in a particular CSV input file. However, the population utility can, in some cases, recognize class instances by incomplete keys, if those instances already exist in the database.

For example, the complete key for an LPAR contains LPAR Name, Physical System name, CPU Serial number, Number of Logical processors, and other attributes. If complete data for all LPARs already exists in the database, the population utility can recognize an LPAR instance by the LPAR Name alone.

TreatWarningsAsErrors

Determines how the population utility responds if it finds records that cannot be populated

True – Records that cannot be populated are treated as errors and no records are populated.

False – Records that cannot be populated are treated as warnings and the population process continues.

Regardless of this setting, information about the population process appears in the ErrorsOutput file.

SupressProgressIndicator

Determines whether the population utility progress indicator is displayed

True – The progress indicator should be suppressed because the population utility runs in the background and does not have access to a terminal screen.

False – The progress indicator should be displayed.

 

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