How the Asset Management Sandbox feature works
Page 1 of 1
How the Asset Management Sandbox feature works
How the sandbox feature works in Asset Management
giby.varghese@gmail.com- Posts : 107
Points : 222
Reputation : 3
Join date : 2009-11-11
Re: How the Asset Management Sandbox feature works
1. The Sandbox feature is enabled in Asset Management with the following steps:
Launch Application Configuration Management
Choose Asset Management --> Advanced Options --> Asset Management Settings
Set Sandbox Enabled to Yes.
Set Sandbox Dataset Name to BMC.ASSET.SANDBOX. (The Reconciliation Job named "BMC Asset Management - SandBox"
operates on this DatasetID, so if you were to specify a different one, you would have to customize the Reconciliation Job)
2. When you create or modify a CI in the production dataset with the sandbox enabled, a "Waiting for Reconciliation" dialog is
displayed when you Create or Modify a CI in Asset Management. The CI is created in the specified sandbox dataset (default is
BMC.ASSET.SANDBOX) and the "BMC Asset Management - SandBox" Reconciliation Job is triggered by workflow. It the RE
Job runs asynchronously, but you can check the progress and results using the Job History Console.
3. The "BMC Asset Management - SandBox" reconciliation job merges data using the "BMC Default Merge Precedence Set."
The "BMC Default Merge Precedence Set" specifies the datasets and their respective precedence groups. The "BMC Default
Merge Precedence Set" includes the datasets and precedence groups shipped with BMC applications, so when the data is
merged to the production dataset, it preserves the data from datasets with higher precedence weights than
BMC.ASSET.SANDBOX.
4. A "Delete Dataset" activity in the RE job removes the temporary data from the BMC.ASSET.SANDBOX dataset.
Launch Application Configuration Management
Choose Asset Management --> Advanced Options --> Asset Management Settings
Set Sandbox Enabled to Yes.
Set Sandbox Dataset Name to BMC.ASSET.SANDBOX. (The Reconciliation Job named "BMC Asset Management - SandBox"
operates on this DatasetID, so if you were to specify a different one, you would have to customize the Reconciliation Job)
2. When you create or modify a CI in the production dataset with the sandbox enabled, a "Waiting for Reconciliation" dialog is
displayed when you Create or Modify a CI in Asset Management. The CI is created in the specified sandbox dataset (default is
BMC.ASSET.SANDBOX) and the "BMC Asset Management - SandBox" Reconciliation Job is triggered by workflow. It the RE
Job runs asynchronously, but you can check the progress and results using the Job History Console.
3. The "BMC Asset Management - SandBox" reconciliation job merges data using the "BMC Default Merge Precedence Set."
The "BMC Default Merge Precedence Set" specifies the datasets and their respective precedence groups. The "BMC Default
Merge Precedence Set" includes the datasets and precedence groups shipped with BMC applications, so when the data is
merged to the production dataset, it preserves the data from datasets with higher precedence weights than
BMC.ASSET.SANDBOX.
4. A "Delete Dataset" activity in the RE job removes the temporary data from the BMC.ASSET.SANDBOX dataset.
giby.varghese@gmail.com- Posts : 107
Points : 222
Reputation : 3
Join date : 2009-11-11
Similar topics
» Add attributes to CMDB classes for use in Asset Management
» What needs to be configured to give an Asset Admin user access to view and modify a CI?
» Incident Management Script vs. Decision Tree vs. Template
» What needs to be configured to give an Asset Admin user access to view and modify a CI?
» Incident Management Script vs. Decision Tree vs. Template
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum