Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Integrating version 4.5 and earlier with brownfield Corporate Atrium

Important

If you use the method outlined in this topic, be sure to follow each step in the order provided.

Integration with Corporate Atrium/ITSM has two parts. First, you can use an existing brownfield BMC Remedy AR System, BMC Atrium Core, or BMC Remedy IT Service Management (sometimes called Remote ITSM) for adding Company-related information (for example, sites and people) into BMC Cloud Lifecycle Management, as shown below. You can also add IT assets (CMDB CIs) created by BMC Cloud Lifecycle Management to Remote Atrium.

brownfieldDiagram.png

Note

  • The supported versions of BMC Remedy Change Management that you can integrate are 7.6.04 SP1, 8.0, and 8.1.01.
  • Remote ITSM is sometimes called Corporate ITSM, Corporate Change, Corporate AR, or Remote AR. Within BMC Cloud Lifecycle Management, Remote ITSM describes the installation of a non-CLM AR System.

This topic includes:

Integration overview

With the help of the Corporate ITSM (or Corporate Atrium) integration extension, a Company, site, or people created on the Corporate ITSM AR System server is automatically available on the CLM AR System server. In addition, CMDB data created on the CLM AR System server is automatically made available on Corporate ITSM AR System server.

Corporate ITSM (or atrium) integration extension consist of two extensions

  • The “corporate” extension which you must apply and configure on the Corporate ITSM AR System server
  • The “CLM” extension which you must apply and configure on the CLM AR AR System server

After you apply the corporate ITSM integration extensions on Corporate ITSM AR and CLM AR (described below), data transfer begins between these two AR servers. For example, Foundation data like Company, location, people, and so on, starts moving from Corporate AR to CLM AR as soon as it is created at Corporate AR. In the same way, CMDB CI data like ComputerSystem, OperatingSystem, Product, ServiceOffering, and so on start moving from CLM AR to Corporate AR.

Note

There is one additional step (mentioned below) when a People record is created at Corporate AR. In the same way, CMDB CI data created by CLM AR are brought into a temporary dataset at Corporate ITSM AR. You can merge this data with the ASSET dataset by running the BMC CSM Import reconciliation job on the Corporate ITSM AR, as needed.

Considerations

  • When you initially integrate with Corporate ITSM, you can use an escalation to perform a bulk transfer of data. Create and run the escalation outlined below to transfer the initial load.

To create the escalation

1. Log in to the BMC Remedy Developer Studio and connect to Corporate ITSM server.

2. Switch to Best Practice Mode.

3. Create a new escalation (choose File > New > Escalation).

4. On the Associated Forms panel, select the form on which escalation will be run.

5. Keep Execution Status as Disabled and Run By as Interval.

6. Enter the appropriate Run If Qualification (for example, ‘Company Entry ID’ != $NULL$ ).

7. On the If Action panel, right-click and select DSO for the action.

8. Complete the fields similar to the following example:

escalation.png

9. Click Save, and name the escalation.

To run the escalation

1. Log in to the BMC Remedy Developer Studio and connect to Corporate ITSM server.

 2. From the All Objects branch, double-click Escalations.

 3. Right-click the escalation in the list, and select Run.

  • When new users are synchronized from Corporate AR to CLM AR, you must synchronize user activity in the Tenant Administration Console. (See Creating and managing users in BMC Cloud Lifecycle Management.)
  • When running a DSO sync, exclude the Demo user on the BMC Cloud Lifecycle Management server.
  • User groups and license types (fixed/floating) are transferred through DSO from the Corporate AR to the CLM AR.  Make sure the server and application license configurations are aligned on both the Corporate and CLM AR servers.
  • If you are integrating with BMC Remedy ITSM 9.1, go to Support for BMC Remedy ITSM 9.1at the end of this topic, and then continue with the next section below.
Warning

If the Corporate AR and CLM AR servers have conflicting user IDs for foundation data forms (such as user, company, and site), do not use DSO to synchronize the servers.

Warning

The ability to edit the host name, port, and so on is available if the Corporate ITSM server is the same as what you configured with BMC Cloud Lifecycle Management and if access details such as host name and port have changed.

Although editing is available, do not change the Corporate ITSM server after you have integrated with BMC Cloud Lifecycle Management.

Fresh integration: Synchronizing ITSM Foundation (Company, Site, People data) from Corporate ITSM AR to the CLM  AR server

Corporate ITSM/Corporate Atrium integration 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.x 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 

    Note

    If you enter 0 for the Port in the DSO Server Setting Table, the server name is retrieved from the Distributed Logical Mapping form. Then, when you open Server Information form after closing it, the server name is not listed in the DSO Server Setting Table. (If you enter a port number besides 0, the server name persists.)

  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. 

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.
    To onboard new tenants, you can use the cloud administrator account (clmadmin), which is installed by default with BMC Cloud Lifecycle Management.
  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.

    Note

    The Sync action applies to the users within the Tenant for which the Cloud Admin, Cloud Organization Admin, or Cloud End User roles have been assigned and gives them the appropriate Organization relationship. (Users not assigned to one of these roles do not get the Organization relationship added.)

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
  • BMC.CORE:BMC_Person

Data (AR artifacts) created when running corporate_extensions

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

Corporate AR

  • 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 Lifecycle Management Foundation, BMC Cloud Lifecycle Management Administrator, and BMC Cloud Lifecycle 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.1.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
    • CorporateCSM:DSOMapping:BMC_Person
  • 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
    • CorporateCSM:DSO:BMC_PersonFilter

CLM AR

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

To enable the CMDB CI transfer to Corporate AR or to enable BMC Change Management with Corporate ITSM, see Integrating-with-BMC-Change-Management.

Support for BMC Remedy ITSM 9.1

For successful integration of BMC Cloud Lifecycle Management and BMC Remedy ITSM 9.1, make sure that LDAP/AD is integrated with the CLM AR server and Corporate ITSM server and that passwords are not stored locally on any AR System server (that is, the CLM AR server and the Corporate AR server). Then, after this LDAP/AD integration and before the initial load, perform the following steps.

  1. Upgrade BMC Cloud Lifecycle Management 4.5 to version 4.5 patch 3.
  2. Apply Hotfix1 and Hotfix2 for BMC Cloud Lifecycle Management 4.5 patch 3.
    You can obtain the hotfix zip files at:
    ftp://ftp.bmc.com/pub/CLM4500_P3_HF/CLM4500P3HF1.zip
     ftp://ftp.bmc.com/pub/CLM4500_P3_HF/CLM4500P3HF2.zip

 

 

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