Using a sandbox dataset for CI data
When multiple sources update BMC Atrium CMDB, there must be some control on how that data is updated. Without control, BMC Atrium CMDB can become loaded with unintended data. BMC Atrium CMDB and BMC Asset Management provide an underlying mechanism to control how your production data is updated. This mechanism is 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.
An administrator defines what sources of updates have the most appropriate information to load into the production data, and can disable the sandbox. For more information, see Configuring BMC Asset Management settings.
The user does 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.
During reconciliation, some updates might not get updated in the production dataset. The system can be configured to treat another data source as a higher precedence than the data being entered through BMC Asset Management. If two data sources make updates, the data source with the highest precedence determines the production dataset.
Depending on whether your system is configured with a sandbox dataset, the CI creation process varies slightly.
- If your system is configured with a sandbox dataset, CIs that you create or modify flow through the sandbox dataset. You can choose to wait until the data has been reconciled, or move on to the next CI.
- If your system does not have a sandbox dataset, CI data goes directly into the production dataset.