This documentation supports the 23.3 version of BMC Helix ITSM Asset Management.To view an earlier version, select the version from the Product version menu.

Configuring Asset Management settings

In the Mid Tier interface, you use the Asset Management Settings form to designate the sandbox and production datasets, and the behavior of the CI form after you save the CI. When multiple sources update the BMC Helix Configuration Management Database (BMC Helix CMDB), there must be some control on how the data is updated so that BMC Helix CMDB does not become overloaded with unintended data. For this purpose BMC Helix CMDB and BMC Helix ITSM: Asset Management provide a control mechanism, which is the sandbox dataset.

BMC Helix ITSM: Asset Management is installed with the sandbox dataset set to BMC.ASSET.SANDBOX and the production dataset set to BMC ASSET. The sandbox dataset is used to stage updates to a production dataset. You are required to use reconciliation rules to move the data to production.

An Asset administrator defines what sources of updates have the most appropriate information to be loaded into the production data. The administrator can disable the sandbox. Users do not make changes directly to production data, unless the sandbox is disabled. When a user modifies data, the data flows through a temporary storage area (the sandbox dataset), and then runs through the Reconciliation Engine. The Reconciliation Engine determines which modified attributes are to be included in the production data.

Important

During reconciliation, some modifications might not get updated in the production dataset because there can be more than one data source for a production dataset. You can configure the precedence of the different datasources. If two data sources make similar updates, the data source with the highest precedence is allowed to update the production dataset. For information, see Learning about reconciliation.

 

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