Renaming datasets by using the Reconciliation Engine
The Reconciliation Engine works with logical dataset names, each corresponding to a dataset ID. The dataset ID is what is stored with instance data. This allows you to rename a dataset without modifying the dataset ID of every instance in the dataset.
A Rename activity changes only the logical name of the dataset you select. It retains the old logical name in a new dataset with a GUID as its dataset ID.
When you rename a dataset, you should manually update all job definitions, components, and applications with
the new dataset name. Otherwise, the job fails to execute.
Some of the job definitions, applications, and components include:
- Reconciliation jobs (OOTB as well as Customized)
- Atrium Integrator Engine \ Atrium Integrator jobs (OOTB as well as Customized)
- Normalization Engine jobs (OOTB as well as Customized)
- Cloud Lifecycle Management jobs (OOTB & Customized)
- Workflows (OOTB as well as Customized) provided by different applications like ITSM.
- Discovery tools like ADDM\Blade.
- Existing CIs populated in the particular dataset.
To create a Rename reconciliation activity
- In the Reconciliation console, click Create Job or open an exist reconciliation job.
See Creating and editing a customized reconciliation job.
- In the Activities area, click New.
- For Type, select Rename.
Complete the following fields:
Type a unique name. The name cannot contain any characters that are not allowed in file names for the operating system of your server. For example, on a Windows server, your job name cannot contain the following characters: \ / : * ? " < > |.
Select a namespace using the controls with the Namespace field. Only classes in the selected namespaces can participate in the activity. For more information, see Dynamic dataset and qualification values in event-driven reconciliation jobs.
Select Active. You can later disable the activity by changing this to Inactive.
Continue on Error
Define whether the job continues if the activity has an error.
Checked — A job containing this activity continues to run if an error occurs in this activity.
Unchecked — A job containing this activity terminates if an error occurs in this activity.
Specify in what order you want this activity to run relative to other activities in a job. For example, if this activity has a value of 2 it runs before an activity with a value of 3. The sequence can be 0 to 1000, inclusive.
- From the Dataset to rename list, select the dataset to rename.
- In the New Dataset Name field, enter a new name for the selected dataset.
- Click Done.
- In the Job Editor, click Save.
When you have added activities to a job, you can execute the job manually or with a schedule. See Starting and stopping a reconciliation job.
After renaming the reconciliation activity, you need to update the job definitions for those jobs that referred the older dataset name or are standard ID merge jobs.
To update job definitions
- From the Reconciliation menu click Edit Job.
- In the Job Editor window, select the Identification activity and click Edit Activity.
In the Edit Activity pane, select the old dataset displayed under Dataset Configuration pane and click Delete.
- From the Job Editor window seelct the merge activity and click Edit.
- From the Dataset Configuration pane select the new dataset from the Source Dataset column.
- Click the Launch Legacy Reconciliation Console icon on the Reconciliation menu.
- In the Jobs pane, select the rename job, the Related Activities pane displays the related activities.
- Select the merge activity and click View.
- From the Merge tabbed page, delete the old dataset.
- From the Configuration Console, in the Show drop-down list select BMC Default Dataset Merge Precedence Set.
- Select the BMC Default Merge Precedence Set, delete the old dataset name from the dataset list displayed below.
- From the Activity Type window, on the Rename Dataset tabbed page delete the old dataset name from the drop-down list in the Dataset field, click Save.