• Loading...
This documentation refers to a previously released version of BMC Atrium Discovery.
See the information on this topic for 9.0 or see the documentation for the latest version (10.0).
Skip to end of metadata
Go to start of metadata
Space Search

Searching ADDM 8.3

Table of Contents

Goal for migrating data to populate the CMDB for ITSM

Your primary goal for migrating data to populate the CMDB is to ensure that only essential information is reconciled in BMC Atrium CMDB. After the necessary CIs have reconciled in the CMDB, ITSM applications can consume the data for asset, incident, contract, change, problem management, and purchasing information. Just as importantly, you want to ensure that older, unnecessary data that does not have any association with your ITSM assets are not used in the future, enabling you to maintain an accurate, single source of truth in your CMDB. The migration approach in BMC Atrium 8.3 ensures that all CIs in BMC Atrium CMDB that are not reconciled involved with ITSM items (such as incidents and changes) will be deleted.

The process you will follow is illustrated in Process for migrating data to populate the CMDB, and the specific steps outlined in the process are detailed in the following sections.

Migrating data for population to the CMDB for ITSM applications

The following sections detail the specific steps outlined in the process overview to complete the migration process end-to-end.

Scan your infrastructure using BMC Atrium Discovery 8.3

The first step for migrating data from previous releases is to ensure that your current environment is up and running with BMC Atrium Discovery 8.3 to prepare for the migration. With discovery running, do the following:

  1. Start a scan of your infrastructure to discover data in the Discovery dataset. See Performing an initial discovery scan for more information. This enables you to roll out the new version into the estate and have it discovering all the same data that BMC Atrium 7.5 was discovering, only using the tools and technology you will use moving forward.
  2. Test the data in the Discovery dataset to ensure the new version is running on your estate as you expect.

Turn off synchronization between BMC Atrium Discovery 7.5 and the BMC.IMPORT.TOPO dataset

Before proceeding with the migration, the CI data from BMC Atrium Discovery 7.5 should no longer be synchronizing to the staging dataset. Disable synchronization so that CIs are no longer being pushed from version 7.5 to the CMDB. You cannot have the same CI being populated by both versions of the product at the same time.

Run and analyze a CI association report

With BMC Atrium Discovery working as expected, you can now run the migration utility on the command line with the -F option to generate a report that details the current CI associations in the incoming configuration data. This will help you analyze and understand how configuration data will ultimately get populated to your CMDB.

To run an analysis report:

  1. Type the following command:
     tw_cmdb_addm75_migration -F <cmdb> 
    A text file is generated that lists all CIs have active associations with SIM, AE, ITSM, and so forth. The report also contains the list of CIs that are not associated with any of these applications and are therefore to be soft deleted.
  2. Review the report to understand the impact on your ITSM applications when the data is migrated.
    All CIs that are not actively associated with other applications will be set for soft deletion, and all CIs that are, will be set for AssetLifecycleStatus = End of Life in the BMC.IMPORT.TOPO dataset.
    Note

    CIs are flagged as End of Life to enable migration of data in BMC Atrium Discovery, not because the asset itself is being retired.

For an example report, see Sample report.

Turn off synchronization between BMC Atrium Discovery 7.5 and the BMC.IMPORT.TOPO dataset

Before proceeding with the migration, the CI data from BMC Atrium Discovery 7.5 can no longer be synchronizing to the staging dataset. Disable synchronization so that CIs are no longer being pushed from version 7.5 to version 8.3. You cannot have the same CI being populated by both versions of the product at the same time.

Run the migration utility to make the CI changes in BMC.IMPORT.TOPO

You can run the migration utility with the --migrate option to make the necessary changes to the BMC.IMPORT.TOPO dataset to ensure that it is ready to reconcile with version 8.3 data.

Note

Running the utility with the --migration option generates a report in addition to executing the changes in the BMC.IMPORT.TOPO dataset. No changes are made to the BMC.ASSET dataset.

To make CI changes in the BMC.IMPORT.TOPO dataset:

  1. Type the following command:
     tw_cmdb_addm75_migration --migrate 
    A text file is generated that lists all CIs that are and are not actively associated with any other applications or services, and the utility performs the corresponding data changes in the BMC.IMPORT.TOPO dataset. This process involves marking unnecessary CIs for deletion so that they will not be used in the future.

For ITSM, unnecessary items are CIs that match the following conditions:

    • They were populated by BMC Atrium Discovery 7.5
    • They are not associated to any ITSM item: incident, problem, change, or contract
    • They do not have any audit history
    • They have not been reconciled with any other data source (this ensures that BMC Atrium Discovery does not delete items that another data source has an interest in)

For all CIs that have either audit history or that have at least one ITSM item associated to them, the migration utility sets the AssetLifecyleStatus attribute to End of Life. This prevents additional ITSM items from being associated with these CIs, thereby preventing them from being used to create new incidents in ITSM.

Reconcile CIs in BMC Atrium CMDB

After running the utility, you must ensure that CIs are reconciled in the CMDB, because some of the version 7.5 data will co-exist with the version 8.3 data until the migration process is complete. Reconciliation ensures that the changes that the migration utility has made to the BMC.IMPORT.TOPO dataset are populated to BMC.ASSET.
To reconcile the data in the CMDB:

  1. From the Atrium Core console, run a Reconciliation Engine Purge job on the BMC.ASSET dataset.
  2. Turn off the reconciliation between the BMC.IMPORT.TOPO dataset and the BMC.ASSET dataset.
  3. Turn on the reconciliation between the version 8.3 Discovery dataset and the BMC.ASSET dataset.
    This approach ensures that only pertinent, version 8.3 CIs are populated in the CMDB, while retaining the history of obsolete version 7.5 CIs. For more information about working with reconciliation jobs, see the BMC Atrium CMDB Normalization and Reconciliation Guide.

Verify CIs have been set to End of Life in BMC Atrium CMDB

Next, as a check on how well the migration process has completed, you can verify which CIs have been set to End of Life in BMC Atrium CMDB. To perform this verification:

  1. In the BMC Remedy Action Request System Server (AR System Server) User tool, open the BMC_BaseElement form.
  2. Set the AssetLifecycleStatus attribute to End of Life.
  3. Click Search.
    This returns a list of all End of Life CIs in the BMC.ASSET dataset, which you can use to compare with the results of what the utility reported and changed.

Hide obsolete CIs to prevent them from being used by other applications

The migration from BMC Atrium Discovery 7.5 to BMC Atrium Discovery 8.3 entails running a script which changes the status of all CIs that were discovered with BMC Atrium Discovery 7.5 to End of Life. New CIs discovered with BMC Atrium Discovery 8.3 are created corresponding to each CI discovered with BMC Atrium Discovery 7.5. Any old CIs that had not been related to any Incident, Contract, Change, or so forth are also Marked As Deleted. CIs that are "Marked As Deleted" do not show up in ITSM CI search dialogs, so cannot be related to an Incident.

However, old CIs already related to an Incident, Contract, Change, or so forth before the migration cannot simply be "Marked As Deleted", as they are associated with an active ticket. So their status is simply changed to "End of Life".

After migrating, we only want relationships to be made to the new CIs discovered by BMC Atrium Discovery 8.3. Typically and ITSM user would not choose to relate an Incident, Contract, Change, or so forth for an old CI, since the "CI Relationship Search" form used for this purpose would clearly show its CI Status of "End of Life". To ensure that this occurs you can modify the behavior of the "CI Relationship Search" form (AST:CI Association Search) so that it does not display any CI that has been marked as "End Of Life" (AssetLifecycleStatus = "End of Life") and originates from an BMC Atrium Discovery 7.5 dataset (AttributeDataSourceList LIKE "%BMC.IMPORT.TOPO%").

To do this:

  1. In the left pane of BMC Remedy Developer Studio, expand "All Objects" then double-click on "Forms".
  2. Double click the AST:BaseElement entry. The Form is displayed in edit mode. Right click on the form and select Add Fields from BMC.CORE:BMC_BaseElement.
    This screen illustrates how to access the Add Fields dialog. The "Add Fields" dialog displays all fields that can be added to the form.
  3. Sort the fields by Name, find and select AttributeDataSourceList, and click OK.
    A new field displays at the top-left corner of the form.
  4. Drag and drop the field into some free space (for example, under the "Status Reason" field), and then save the modified form.

  5. In the left pane of BMC Remedy Developer Studio, expand "All Objects" and double-click on "Forms".
  6. Double-click the AST: CI Associations Search entry. The Form is displayed in edit mode.

  7. Scroll down to the z2TH_ConfigurationItem table (the only table on the form) and select it. The properties of the table are displayed in the right pane.

  8. In the Properties pane, under Attributes, Tree/Table, click the "25 Column(s)" value, and then click the "..." button.

  9. Modify the default qualification EXTERNAL($z1D_Qualification$) by appending it with the following:
    AND ( NOT (('AttributeDataSourceList' LIKE "%BMC.IMPORT.TOPO%") AND ('AssetLifecycleStatus' = "End of Life")))

  10. Click OK and then save the modified form.

When you have completed this, BMC Atrium Discovery 7.5 CIs that were set to End Of Life are not displayed in the result set of the AST: CI Associations Search form (CI Relationships Search) which is used to relate a CI.

Sample report

The following section of a report illustrates the CI details reported by the migration utility that are relevant for ITSM applications.

############################################################
Active ITSM records
__________________________________________________________________
These Topo (ADDM 7.x) CIs will not be deleted as they are related to
one or more ITSM records
__________________________________________________________________
    InstanceId : OI-F2ADC2D11E1A434EAAD3479C7A199502
       ReconId : OI-FE4E21C678394A208A2E17DEF161C855
       Dataset : BMC.ASSET
  Is a Topo CI : Yes
     ClassName : J2EE:BMC_J2EEAPPLICATIONSERVER
          Name : medrec:10.128.88.20:7011:mgcbr1s07:MedRecServer
    NameFormat : DomNm:AdmSrv.IP:AdmSrv.Port:NdNm:AppSrvNm
     ShortDesc : MedRecServer

  Associations : 

            Type : Incident
       CMDB Form : AST:J2EEApplicationServer
      ITSM ReqId : INC000000000003
       ITSM Form : HPD:Help Desk

------------------------------------------------------------------
    InstanceId : OI-06726C3DBA364E02866B008A0525B62A
       ReconId : OI-53417A05E9814BC7B8345DE73ED91CEF
       Dataset : BMC.ASSET
  Is a Topo CI : Yes
     ClassName : J2EE:BMC_J2EECLUSTER
          Name : medrec:10.128.88.20:7011:DefaultCluster
    NameFormat : DomNm:AdmSrv.IP:AdmSrv.Port:ClstNm
     ShortDesc : DefaultCluster

  Associations : 

            Type : Known Error
       CMDB Form : AST:J2EECluster
      ITSM ReqId : PKE000000000005
       ITSM Form : PBM:Known Error

------------------------------------------------------------------
Labels
  • None