Skip to Content
Information
This documentation supports the 20.02 version of Remedy Asset Management.To view an earlier version, select the version from the Product version menu.

Understanding the sandbox and production datasets

When multiple sources update the BMC Atrium Configuration Management Database (BMC Atrium CMDB), there must be some control on how the data is updated so that BMC Atrium CMDB does not become loaded with unintended data. BMC Atrium CMDB and BMC Asset Management provides a control mechanism: the sandbox dataset.

BMC Asset Management is installed with the sandbox dataset set to BMC.ASSET.SANDBOX and the production dataset set to BMC ASSET.


Related topics

BMC Atrium Core architecture and features

Sandbox views and datasets

An administrator defines what sources of updates have the most appropriate information to load into the production data, and 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 to also modify into the production data.

Warning

Important

During reconciliation, some modifications might not get updated in the production dataset because, there can be more then one data source for a production dataset. You can configure the precedence of the different datasources. If the two data sources make updates, the data source with the highest precedence determines 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*

Remedy Asset Management 20.02