Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Using DSO to integrate brownfield Corporate AR and CLM AR

You can use DSO to move users from brownfield AR/Atrium/ITSM into CLM AR. Or to be more specific, you can use DSO to transfer Company-related information (for example, sites and people) from existing brownfield BMC Atrium Core (Corporate Atrium), AR System (Corporate AR), or BMC Remedy IT Service Management (Corporate ITSM) into BMC Cloud Lifecycle Management AR.

In addition, after you complete the DSO integration between brownfield AR/Atrium/ITSM, data that is created in CLM AR is DSO'd to ITSM AR. Specifically,  DSO transfers IT assets (for example, BMC_ComputerSystem or BMC_Tag CIs) created in BMC Cloud Lifecycle Management to Corporate AR.

This topic contains the following information:

Corporate extensions

 

Note

Perform the corporate integrations with Atrium extensions before you create CLM data and integrate corporate change. Use the Tenants and users to create CLM data that are DSOed from corporate AR/ITSM.

Corporate extensions (bundled with 4.0 extensions) are required for integrating Corporate Atrium with BMC Cloud Lifecycle Management, based on following type of deployments:

  • CLM AR if there is a single AR CLM deployment
  • Enterprise-AR if there is a two AR CLM deployment

After Corporate ITSM is ready for integration with BMC Cloud Lifecycle Management, you can install corporate extension from atrium on Corporate AR. 
Similarly, after CLM AR is ready for integration with corporate AR, you can install the clm extension from atrium on CLM AR.

To install the corporate extension on Corporate AR

  1. Copy the corporate folder from the following location on CLM AR (and Enterprise-AR if there is a two AR CLM architecture) to the Corporate AR System.
    For example:
    <Enterprise AR install dir>\BMCCloudLifeCycleManagement\Cloud_DB \extensions\corporate_integration\atrium
    Or you can run extensions from a remote system where this corporate extension is copied and point to the Corporate AR while running the extension.
  2. Launch the Atrium maintenance tool.
    For example:
    C:\Program Files\BMC Software\AtriumCore\atriumcore\AtriumCoreMaintenanceTool
  3. Select Configuration > Run Extensions. 
    AtriumCoreMaintenanceTool.png 
  4. Select ExtensionLoader.xml from the corporate folder, and then click Next. 
    For example:
    C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Cloud_DB\extensions\corporate_integration\atrium\corporate 
  5. Enter the details of the Corporate AR (Server name, Port, Username, and Password), and then click Next. 
    This creates data (AR artifacts) on Corporate AR.
    AtriumCoreMaintenanceTool2.png 
  6. Click Run to run the ExtensionLoader.xml file. 
  7. Using the Mid-Tier, connect to Corporate AR.
  8. Open the Distributed Logical Mapping form.
    For example:
    http://midTier:8080/arsys/forms/corporateARServer/Distributed+Logical+Mapping/
  9. Search for the CLM-DESTINATION-SERVER entry and update its value with the CLM AR hostname or IP Address.
  10. From the IT Home page, select Applications > AR System Administration > AR System Administration Console. 
    Make sure that you connect to the IT Home page for the Corporate AR server. For example:
    http://midTier:8080/arsys/forms/corporateARServer/SHR%3ALandingConsole/ 
  11. In the AR System Administration Console, select System > General > Server Information. 
  12. Click the Connection Settings tab.
  13. Click the DSO Server tab, and then add the DSO server details (CLM AR).
    ConnectionSettings.png 
  14. Click OK to save your changes. 

To install the clm extension on CLM AR

  1. Locate the clm folder in the following location on the CLM AR system (and Enterprise-AR if there is a two AR CLM architecture).
    For example:
    <Enterprise AR install dir>\BMCCloudLifeCycleManagement\Cloud_DB \extensions\corporate_integration\atrium\clm
    Or you can run extensions from remote system where this clm extension is copied and point to the CLM AR while running the extension.
  2. Launch the Atrium maintenance tool.
    For example:
    C:\Program Files\BMC Software\AtriumCore\atriumcore\AtriumCoreMaintenanceTool 
  3. Select Configuration > Run Extensions. 
  4. Select ExtensionLoader.xml from the clm folder, and then click Next. 
    For example:
    C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Cloud_DB\extensions\corporate_integration\atrium\clm 
  5. Enter details of the CLM AR (Server name, Port, Username, and Password), and then click Next.
    • CLM AR if there is a single AR CLM architecture
    •  Enterprise AR if there is a two AR CLM architecture
      This creates data (AR artifacts) on CLM AR.
  6. Click Run to run the ExtensionLoader.xml file. 
  7. Using the Mid-Tier, connect to CLM AR.
  8. Open the Distributed Logical Mapping form.
    For example:
    http://midTier:8080/arsys/forms/clmARServer/Distributed+Logical+Mapping/
  9. Search for the CORPORATE-DESTINATION-SERVER entry and update its value with the Corporate Atrium hostname or IP Address.
  10. From the IT Home page, select Applications > AR System Administration > AR System Administration Console. 
    Make sure that you connect to the IT Home page for the CLM AR server. For example:
    http://midTier:8080/arsys/forms/clmARServer/SHR%3ALandingConsole/  
  11. In the AR System Administration Console, select System > General > Server Information. 
  12. Click the Connection Settings tab.
  13. Click the DSO Server tab, and then add the DSO server details (Corporate AR).
  14. Click OK to save your changes. 

To DSO people records from Corporate AR to CLM AR

To create people in corporate AR (or corporate ITSM) and then use People records (for example, one with a Cloud Admin role) in CLM AR, use the following steps to DSO the BMC.CORE:BMC_Person details from Corporate AR to CLM AR.

  1. From the IT Home page on Corporate AR, select Applications > Administrator Console > Application Administration Console. 
  2. In the ITSM Application Administration Console, create a People record in a company on Corporate AR.
  3. On Corporate AR, run the BMC Asset Management – Sandbox reconciliation job.
    From the IT Home page, select Applications > Atrium Core > Atrium Core Console > Applications > Reconcilation.
    Wait for the job to complete.
    ReconJob.png 
  4. Log on to CLM AR server, search for the People record, assign the appropriate cloud role (for example, Cloud Admin, Cloud Organization Admin, Cloud End User) to that record, and then click Save.
  5. On CLM AR, run the BMC CSM Import reconciliation job. 
    Wait for the job to complete.
  6. As a Cloud Admin user, log on to the CLM Administration Console and go to the Tenant Management Workspace.
  7. If the company (and its people) is not already onboarded, then onboard it with the appropriate details.
  8. Select the company and then click Sync to synchronize the people (its users) in that company.
    The people record is ready to use with assigned cloud role.

Data that will DSO from Corporate AR to CLM AR

DSO will transfer the following data from Corporate AR to CLM AR:

COM:Company

CTM:People Organization

CTM:People

SIT:Site

Roles

User

Groups

 

CIs that will DSO from CLM AR to Corporate AR

DSO will transfer the following CIs from CLM AR to Corporate AR:

BMC_Cluster

BMC_Component

BMC_Component_WeakChildren

BMC_ComputerSystem

BMC_ConcreteCollection

BMC_ContractLine

BMC_Dependency

BMC_Dependency_WeakChildren

BMC_LogicalDisk

BMC_MemberOfCollection

BMC_OperatingSystem

BMC_Product

BMC_ProtocolEndpoint

BMC_ServiceOffering

BMC_ServiceOfferingInstance

 

Data (AR artifacts) created when running corporate_extensions

The following data (AR artifacts) are created when you run corporate extensions.

On Corporate Atrium as part of atrium/corporate extension

  • Group: Cloud Admin, Cloud Organization Admin, Cloud Org Admin Computed, Cloud Admin Computed, Cloud End User, Cloud End User Computed, CMDB Data Change Group, CMDB Data View Group
  • Roles: On the BMC Cloud Management Foundation, BMC Cloud Management Administrator, and BMC Cloud Management User applications
  • License: DSO App License.This license is only bundled but not called in the extension. If the license is required, you can import it separately. The license is similar to that used in CLM for DSO.
  • Share Application Properties: Application named Corporate ITSM Integration - Corporate Artifacts that is version 4.0.00
  • Distributed Logical mapping: CLM-DESTINATION-SERVER logical name with dummy value of <CLM-DESTINATION-SERVER>
  • Distributed Pool: CorporatePool1

  • Distributed Mappings:

    CorporateCSM:DSOMapping:Company

    CorporateCSM:DSOMapping:Group

    CorporateCSM:DSOMapping:People

    CorporateCSM:DSOMapping:PeopleAccessRestriction

    CorporateCSM:DSOMapping:PeopleOrganization

    CorporateCSM:DSOMapping:PeoplePermissionGroup

    CorporateCSM:DSOMapping:Roles

    CorporateCSM:DSOMapping:Site

    CorporateCSM:DSOMapping:SiteAlias

    CorporateCSM:DSOMapping:SiteCompanyAssociation

    CorporateCSM:DSOMapping:SiteGroup

    CorporateCSM:DSOMapping:User

  • Filters:

    CorporateCSM:DSO:CompanyFilter

    CorporateCSM:DSO:CompanyFilter_Delete

    CorporateCSM:DSO:GroupFilter

    CorporateCSM:DSO:GroupFilter_Delete

    CorporateCSM:DSO:People

    CorporateCSM:DSO:PeopleAccessRestriction

    CorporateCSM:DSO:PeopleOrganization

    CorporateCSM:DSO:PeoplePermissionGroup

    CorporateCSM:DSO:People_Delete

    CorporateCSM:DSO:Roles_filter

    CorporateCSM:DSO:Roles_filter_delete

    CorporateCSM:DSO:Site

    CorporateCSM:DSO:SiteAlias

    CorporateCSM:DSO:SiteCompanyAssociation

    CorporateCSM:DSO:SiteGroup

    CorporateCSM:DSO:UserFilter

    CorporateCSM:DSO:UserFilter_Delete

  • Reconcilation job: BMC CSM Import (standard job with identification and merge activities)
  • Dataset: BMC.IMPORT_CSM 

On CLM AR as part of atrium/clm extension

  • Group: Cloud Admin, Cloud Organization Admin, Cloud Org Admin Computed, Cloud Admin Computed, Cloud End User, Cloud End User Computed, CMDB Data Change Group, CMDB Data View Group
  • Roles: On BMC Cloud Management Foundation, BMC Cloud Management Administrator, and BMC Cloud Management User applications
  • License: DSO App License This license is only bundled but not called in the extension. If the license is required, you can import it separately. The license is similar to that used in CLM for DSO.
  • Share Application Properties: Application named Corporate ITSM Integration – CLM Artifacts that is version 4.0.00
  • Distributed Logical mapping: CORPORATE-DESTINATION-SERVER logical name with dummy value of <CORPORATE-DESTINATION-SERVER>
  • Distributed Pool: CLMPool1

  • Distributed Mappings:

    DIST-CMDB:CSM_TO_CORP-BMC_Cluster

    DIST-CMDB:CSM_TO_CORP-BMC_Component

    DIST-CMDB:CSM_TO_CORP-BMC_Component_WeakChildren

    DIST-CMDB:CSM_TO_CORP-BMC_ComputerSystem

    DIST-CMDB:CSM_TO_CORP-BMC_ConcreteCollection

    DIST-CMDB:CSM_TO_CORP-BMC_ContractLine

    DIST-CMDB:CSM_TO_CORP-BMC_Dependency

    DIST-CMDB:CSM_TO_CORP-BMC_Dependency_WeakChildren

    DIST-CMDB:CSM_TO_CORP-BMC_LogicalDisk

    DIST-CMDB:CSM_TO_CORP-BMC_MemberOfCollection

    DIST-CMDB:CSM_TO_CORP-BMC_OperatingSystem

    DIST-CMDB:CSM_TO_CORP-BMC_Product

    DIST-CMDB:CSM_TO_CORP-BMC_ProtocolEndpoint

    DIST-CMDB:CSM_TO_CORP-BMC_ServiceOffering

    DIST-CMDB:CSM_TO_CORP-BMC_ServiceOfferingInstance

    DIST-CMDB:CSM_TO_CORP-BMC_Organization

    DIST-CMDB:CSM_TO_CORP-BMC_Person

  • Filters:

    DIST-CMDB:CSM_TO_CORP-BMC_Cluster_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Component_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Component_SettingsOf_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Component_HostedSystemComponents_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Component_ContractComponent_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ComputerSystem_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ConcreteCollection_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ContractLine_MM_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ContractLine_C_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ContractLine_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ContractLine_C_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ContractLine_MM_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ContractLine_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Dependency_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Dependency_HostedAccessPoint_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Dependency_TaggedWith_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Dependency_TaggedWith_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Dependency_TaggedWith_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Dependency_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Dependency_TaggedWith_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_LogicalDisk_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_MemberOfCollection_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_OperatingSystem_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Product_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ProtocolEndpoint_CommunicationEndpoint_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ProtocolEndpoint_IPEndpoint_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ProtocolEndpoint_LANEndpoint_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ServiceOffering_C_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_ServiceOfferingInstance_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Organization_DSO

    DIST-CMDB:CSM_TO_CORP-BMC_Person_DSO

  • Initial Load escalations:

    DIST-CMDB:CSM_TO_CORP_CIs_CategorizationSubclass_InitialLoad

    DIST-CMDB:CSM_TO_CORP_Rels_InitialLoad

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*