Integrating with Corporate ITSM for Foundation data

Important

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

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.

Note

  • The supported versions of BMC Remedy Change Management that you can integrate are 7.6.04 SP1, 8.0, 8.1.01, and 9.1.
  • 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.
  • For a successful integration of BMC Cloud Lifecycle Management and BMC Remedy ITSM 9.1, make sure that you have BMC Cloud Lifecycle Management 4.6.04 and that LDAP/AD is integrated with the CLM AR server and the Corporate ITSM server.

This topic includes:

Warning

As a best practice, integrate ITSM with BMC Cloud Lifecycle Management before you create new data on BMC Cloud Lifecycle Management. If you must create cloud data first, avoid conflicts by creating Foundation data that is different from the Corporate ITSM data. If you encounter conflicting data, clean up the data before you transfer the data from Corporate ITSM through DSO.

You can use the BMC CLM ITSM Brownfield utility to synchronize Foundation data.

Integration overview

So that BMC Cloud Lifecycle Management will work with updates to users in BMC Remedy IT Service Management, the Foundation data must be synchronized as outlined in this topic.

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 (Corporate ITSM AR) are automatically available on the BMC Cloud Lifecycle Management AR System server (CLM AR). In addition, CMDB data created on CLM AR is automatically made available on Corporate ITSM AR.

Corporate ITSM (or Corporate Atrium) integration extension consist of two extensions:

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

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 ITSM AR to CLM AR as soon as it is created on Corporate ITSM AR. In the same way, CMDB CI data like ComputerSystem, OperatingSystem, Product, ServiceOffering, and so on start moving from CLM AR to Corporate ITSM AR.

Note

There is one additional step (discussed in To ensure continuous synchronization for People data below) when a People record is created in Corporate ITSM 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.

Before you begin

Before you begin the integration with brownfield Corporate Atrium, enable BMC Distributed Server Option (DSO) on the Corporate ITSM AR server and ask BMC Support to run the Data Consistency Checker.

  1. To enable DSO:
    1. Stop the Corporate ITSM AR server.
    2. Open the armonitor.conf (or armonitor.cfg) file.
    3. Uncomment the DSO plugin path line, and save the file.
    4. Restart the server.
  2. Contact BMC Support and ask them to run Data Consistency Checker before setting up Foundation data sync.
    Continue only if your Support representative sees no issues (such as conflicting IDs).
  3. Review the BMC Remedy ITSM Integration extensions and other supporting files, which are available in a ZipKit (CLM vx.x.zip) on BMC Communities at https://communities.bmc.com/docs/DOC-39920.

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 transferred through DSO from Corporate ITSM AR.

Corporate extensions (bundled with 4.x extensions) are required for integrating Corporate Atrium with BMC Cloud Lifecycle Management, based on the 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 the corporate extension from Atrium on Corporate ITSM AR. 
Similarly, after CLM AR is ready for integration with Corporate ITSM AR, you can install the clm extension from Atrium on CLM AR.

Data that is transferred through DSO from Corporate ITSM AR to CLM AR

 (4.6.04) Click here to view the data that DSO transfers from Corporate ITSM AR to CLM AR.
  • COM:Company

  • COM:Company Alias

  • CTM:People Organization

  • CTM:People

  • CTM:People Permission Groups

  • CTM:SYS-Access Permission Grps

  • SIT:Site

  • SIT:Site Alias

  • SIT:Site Group

  • SIT:Site Company Association

  • Roles

  • User

  • Groups

  • FIN:CostCenterUDAAssociations

  • FIN:ConfigCostCategory

  • FIN:ConfigRules

  • FIN:ConfigCostCentersRepository

  • FIN:CostCategoryRepository

  • FIN:Association


 (4.6.00) Click here to view the data that DSO transfers from Corporate ITSM AR to CLM AR.
  • COM:Company

  • COM:Company Alias

  • CTM:People Organization

  • CTM:People

  • CTM:People Permission Groups

  • CTM:SYS-Access Permission Grps

  • SIT:Site

  • SIT:Site Alias

  • SIT:Site Group

  • SIT:Site Company Association

  • Roles

  • User

  • Groups

  • BMC.CORE:BMC_Person

  • FIN:CostCenterUDAAssociations

  • FIN:ConfigCostCategory

  • FIN:ConfigRules

  • FIN:ConfigCostCentersRepository

  • FIN:CostCategoryRepository

  • FIN:Association

How user licenses work

When users are transferred through DSO, the user license (fixed, floating, or read) is not changed. For example, a user with a fixed license in Corporate ITSM would also have fixed license in CLM AR after the user is transferred. Make sure enough licenses are on the CLM AR server for each specific type before the DSO transfer occurs. Following is the license availability requirement on CLM AR:

  • Fixed – The number of free (unused) fixed licenses in CLM AR should be equal to or more than the number of users with fixed licenses that will be transferred from Corporate ITSM AR through DSO.
  • Floating – The number of floating licenses in CLM AR should be equal to or more than the addition of the number of users with floating licenses in CLM AR and users that will be transferred from Corporate ITSM AR through DSO.
  • Read – No restrictions for the number of licenses.

The following license types give BMC Cloud Lifecycle Management users varying levels of access:

  • Fixed – Users with a fixed license can perform all required actions in BMC Cloud Lifecycle Management.
  • Floating – Users with a floating license can perform all required actions in BMC Cloud Lifecycle Management when a floating license is available. A best practice is to have the same number of or more floating licenses than the number of users in CLM AR.
  • Read – Users with a read license cannot perform BMC Cloud Lifecycle Management actions, including end user actions. If any user transferred (or soon-to-be transferred) through DSO has a read license, the license should be changed to floating or fixed on Corporate ITSM AR or CLM AR.

Accessing the Corporate ITSM Integration ZipKit

To download the Corporate ITSM Integration ZipKit for BMC Cloud Lifecycle Management:

  1. Go to https://communities.bmc.com/docs/DOC-39920, and log in.
  2. Download the Remedy ITSM Integration Artifacts for CLM vnn.nn.nn.zip file to a location where you can copy the files to the Corporate ITSM AR server and the CLM AR server, as follows:

    BMC Cloud Lifecycle Management VersionFile name to download
    4.6.03 or earlierRemedy ITSM Integration Artifacts for CLM v4.6.zip
    4.6.04 or laterRemedy ITSM Integration Artifacts for CLM v4.6.04.zip

    Note:
    If you are using 4.6.04 or later with Extensions installed (Remedy ITSM Integration Artifacts for CLM v4.6.04.zip) and want to upgrade to 4.6.05 or later, do not apply Extensions again. 
  3. Unzip the file.

To install the corporate extensions on Corporate ITSM AR

  1. Copy the corporate folder from the unzipped location (corporate_integration/atrium/corporate) to the Corporate ITSM AR server.
    Alternatively, you can run extensions from a remote system where the extensions are unzipped from the ZipKit and that has the Atrium Maintenance Tool.
  2. Launch the Atrium maintenance tool at C:\Program Files\BMC Software\AtriumCore\atriumcore\AtriumCoreMaintenanceTool.
  3. Select Configuration > Run Extensions
     
  4. Select ExtensionLoader.xml from the corporate folder based on either of the following criteria:

    • If Cloud Roles are to be managed on the Corporate ITSM server, select the ExtensionLoader_PrivilegeControlAtCorporate.xml file from the corporate folder.
      Or

    • If Cloud Roles are to be managed on BMC Cloud Lifecycle Management, select the ExtensionLoader.xml file from the corporate folder
      The path to either file is:
      <Copy location or unzip location>\corporate_integration\atrium\corporate 

  5. Click Next.
  6. Enter the details of the Corporate ITSM AR (User Name, Password, Port Number, and AR Server Host Name), and then click Next
    This creates data (AR artifacts) on Corporate ITSM AR.
     
  7. Click Run to run the ExtensionLoader.xml file.
  8. For Corporate ITSM 9.1 support, after extensions are installed successfully, perform the following steps.

    1. Copy the <unzipped location>\corporate_integration\CLM_AR9X_Fixes folder to the Corporate ITSM server.
      For details about downloading the zip and unzipping the fille,  see Accessing the Corporate ITSM Integration ZipKit.
    2. In BMC Remedy Developer Studio, apply the LDAP_Password_filter_Fix.def file on the Corporate ITSM server.
      For details about applying the definition, see the ReadMe.txt file in the CLM_AR9X_Fixes folder.
  9. Configure DSO on the Corporate ITSM server.
    1. Using the AR System mid tier, connect to the Corporate ITSM server, and open the AR System Administration Console.
    2. Go to System > Distributed Server Option > Distributed Logical Mapping to open the DSO Distribution Logical Mapping Form.
    3. In the Logical Name field, enter CLM-DESTINATION-SERVER to find the CLM destination server entry, and update its value with the CLM AR host name or IP Address.
    4. 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 ITSM AR server, for example:
      http://midTier:8080/arsys/forms/corporateARServer/SHR%3ALandingConsole/ 
    5. In the AR System Administration Console, select System > General > Server Information
    6. Click the Connection Settings tab.
    7. Click the DSO Server tab, and then add the DSO server details (port in the first table and password in the second table) for the CLM AR server.
       

      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.)

    8. Click OK to save your changes. 

Data (AR artifacts) created on Corporate ITSM when running corporate_extensions

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

  •  Groups (Click to see which groups.)
    • 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 BMC Cloud Lifecycle Management for DSO.
  • Share Application Properties: Application named Corporate ITSM Integration - Corporate Artifacts that is version 4.6.04 or 4.6.00 based on which version of zipkit you are installing.
  • Distributed Logical mapping: CLM-DESTINATION-SERVER logical name with dummy value of <CLM-DESTINATION-SERVER>
  • Distributed Pool: CorporatePool1
  •  Distributed mappings (Click to see which distributed mappings.)
    • CorporateCSM:DSOMapping:BMC_Person

    • CorporateCSM:DSOMapping:Company

    • CorporateCSM:DSOMapping:CompanyAlias

    • CorporateCSM:DSOMapping:CTMSYS_AccessPermissionGrps

    • CorporateCSM:DSOMapping:FINAssociation

    • CorporateCSM:DSOMapping:FINConfigCostCategory

    • CorporateCSM:DSOMapping:FINConfigCostCentersRepository

    • CorporateCSM:DSOMapping:FINConfigCostRates

    • CorporateCSM:DSOMapping:FINConfigRules

    • CorporateCSM:DSOMapping:FINCostCategoryRepository

    • CorporateCSM:DSOMapping:FINCostCenterUDAAssociations

    • CorporateCSM:DSOMapping:FINCosts

    • 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 (Click to see which filters.)
    • CorporateCSM:DSO:BMC_PersonFilter (This filter is disabled from BMC Cloud Lifecycle Management 4.6.04.)

    • CorporateCSM:DSO:CompanyAlias

    • CorporateCSM:DSO:CompanyFilter

    • CorporateCSM:DSO:CompanyFilter_Delete

    • CorporateCSM:DSO:CTMSYS_AccessPermissionGrps

    • CorporateCSM:DSO:FINAssociation

    • CorporateCSM:DSO:FINConfigCostCategory

    • CorporateCSM:DSO:FINConfigCostCentersRepository

    • CorporateCSM:DSO:FINConfigCostRates
    • CorporateCSM:DSO:FINConfigRules

    • CorporateCSM:DSO:FINCostCategoryRepository

    • CorporateCSM:DSO:FINCostCenterUDAAssociations

    • CorporateCSM:DSO:FINCosts

    • CorporateCSM:DSO:GroupFilter

    • CorporateCSM:DSO:GroupFilter_Delete

    • CorporateCSM:DSO:People

    • CorporateCSM:DSO:People_Delete

    • CorporateCSM:DSO:PeopleAccessRestriction

    • CorporateCSM:DSO:PeopleOrganization

    • CorporateCSM:DSO:PeoplePermissionGroup

    • 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

  •  Escalations (Click to see which escalations.)
    • CorporateCSM:InitialLoad:010_Company

    • CorporateCSM:InitialLoad:020_CompanyAlias

    • CorporateCSM:InitialLoad:030_CTMSYS_AccessPermissionGrps

    • CorporateCSM:InitialLoad:040_Site

    • CorporateCSM:InitialLoad:050_SiteAlias

    • CorporateCSM:InitialLoad:060_SiteCompanyAssociation

    • CorporateCSM:InitialLoad:070_SiteGroup

    • CorporateCSM:InitialLoad:080_Group

    • CorporateCSM:InitialLoad:090_People

    • CorporateCSM:InitialLoad:100_PeopleOrganization

    • CorporateCSM:InitialLoad:110_PeoplePermissionGroup

    • CorporateCSM:InitialLoad:120_User

    • CorporateCSM:InitialLoad:130_BMC_Person (Important: If you are using BMC Cloud Lifecycle Management 4.6.04, do not run this escalation. After running the CorporateCSM:InitialLoad:120_User escalation, run the CorporateCSM:InitialLoad:140_FINAssociation escalation.)

    • CorporateCSM:InitialLoad:140_FINAssociation

    • CorporateCSM:InitialLoad:150_FINConfigCostCategory

    • CorporateCSM:InitialLoad:160_FINConfigCostCentersRepository

    • CorporateCSM:InitialLoad:170_FINConfigCostRates

    • CorporateCSM:InitialLoad:180_FINConfigRules

    • CorporateCSM:InitialLoad:190_FINCostCategoryRepository

    • CorporateCSM:InitialLoad:200_FINCostCenterUDAAssociations

    • CorporateCSM:InitialLoad:210_FINCost

To install the clm extension on CLM AR

The following steps are similar to the steps in To install the corporate extension on Corporate ITSM AR, which includes helpful screenshots.

  1. Copy the clm folder from the unzipped location (corporate_integration/atrium/clm) to the CLM AR server.
    Alternatively, you can run extensions from a remote system where the extensions are unzipped from the ZipKit and that has the Atrium Maintenance Tool.

  2. Launch the Atrium maintenance tool at 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.
    The path to the file is: 
    <Copy location or unzip location>\corporate_integration\atrium\clm

    Note

    Be sure that the ExtensionLoader.xml file is located in the clm folder; otherwise, you may run into issues.

  5. Enter details of the CLM AR server (server name, port number, user name, and password) to create data (AR artifacts) on the server, and then click Next
    • CLM AR if there is a single AR CLM architecture
    • Enterprise AR if there is a two-AR CLM architecture
  6. Click Run to run the ExtensionLoader.xml file.

Data (AR artifacts) created on CLM AR when running corporate_extensions

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

  • Reconcilation job: BMC CSM Import (standard job with identification and merge activities)
  • Dataset: BMC.IMPORT_CSM
  • Share Application Properties: Application named Corporate ITSM Integration - Corporate Artifacts that is version 4.6.00

Synchronizing ITSM Foundation data for the first time (INITIAL LOAD)

Before the ITSM Foundation integration is enabled between Corporate ITSM AR and CLM AR, if Corporate ITSM AR has ITSM Foundation data in place and there is a requirement to synchronize the data on CLM AR with the Corporate extensions, you can use predefined escalations to synchronize the data between Corporate ITSM AR and CLM AR. You must run the escalations in a predefined sequence. Then, you can transfer the respective form data through DSO from Corporate ITSM AR to CLM AR, and then enable the data to be used for BMC Cloud Lifecycle Management. Synchronizing the ITSM Foundation data has two required steps:

Step 1 – Getting the ITSM Foundation data from the Corporate ITSM server to the CLM server

The predefined escalations are numbered from 1 to 19 so that it is easy to understand the flow of data and so that the escalations are executed in the required sequence.

Note

If you do not execute the escalations in the correct sequence, data corruption related to the relations between the data might occur. (For example, you must run CorporateCSM:InitialLoad:01_Company before CorporateCSM:InitialLoad:02_CompanyAlias.)

The data that is transferred through DSO after running the escalation is listed in Data that is transferred through DSO from Corporate ITSM AR to CLM AR

 (IMPORTANT) Click here to see the SEQUENCE OF ESCALATION EXECUTION
  1. CorporateCSM:InitialLoad:010_Company
  2. CorporateCSM:InitialLoad:020_CompanyAlias
  3. CorporateCSM:InitialLoad:030_CTMSYS_AccessPermissionGrps
  4. CorporateCSM:InitialLoad:040_Site
  5. CorporateCSM:InitialLoad:050_SiteAlias
  6. CorporateCSM:InitialLoad:060_SiteCompanyAssociation
  7. CorporateCSM:InitialLoad:070_SiteGroup
  8. CorporateCSM:InitialLoad:080_Group
  9. CorporateCSM:InitialLoad:090_People
  10. CorporateCSM:InitialLoad:100_PeopleOrganization
  11. CorporateCSM:InitialLoad:110_PeoplePermissionGroup
  12. CorporateCSM:InitialLoad:120_User
  13. CorporateCSM:InitialLoad:130_BMC_Person (Important: If you are using BMC Cloud Lifecycle Management 4.6.04, do not run this escalation. After running the CorporateCSM:InitialLoad:120_User escalation, run the CorporateCSM:InitialLoad:140_FINAssociation escalation.)
  14. CorporateCSM:InitialLoad:140_FINAssociation
  15. CorporateCSM:InitialLoad:150_FINConfigCostCategory
  16. CorporateCSM:InitialLoad:160_FINConfigCostCentersRepository
  17. CorporateCSM:InitialLoad:170_FINConfigCostRates
  18. CorporateCSM:InitialLoad:180_FINConfigRules
  19. CorporateCSM:InitialLoad:190_FINCostCategoryRepository
  20. CorporateCSM:InitialLoad:200_FINCostCenterUDAAssociations
  21. CorporateCSM:InitialLoad:210_FINCost
To run the escalations
  1. Log in to BMC Remedy Developer Studio as the AR System administrator (for example, Demo).
    You will be connecting to the Corporate ITSM server.
  2. Select the correct workspace, and click OK.
  3. In the Login dialog box, enter the user name and password for the AR Administrator (for example, Demo).
  4. Click Edit Server List, provide the ITSM Server details, and OK.
  5. Click Log In.
  6. In the AR System Navigator, under the AR System server, double-click Escalations under All Objects.
  7. To filter the escalations, in the Display items where fields, enter Name contains CorporateCSM:InitialLoad:

    This displays all the escalations to be executed on Corporate ITSM as part of initial load in the sequence listed above.
  8. Right-click the escalation you want to execute, and click Run Now.
  9. Repeat step 8 for each escalation.

    Note

    Be sure to provide enough time for each escalation to be executed completely before running the next escalation. Depending on the amount of data in each escalation, the length of time may vary. To know when an escalation has completed, you can enable AR Escalation logs. (For more information, see Enabling logs for performance issues in the BMC Remedy AR System documentation.)

Step 2 – Making the synchronized data in the CLM server compatible for BMC Cloud Lifecycle Management usage

In BMC Cloud Lifecycle Management 4.6.04 or later, after the initial load data is transferred through DSO from the Corporate ITSM server to BMC Cloud Lifecycle Management, you must onboard the company (tenant). You can onboard the tenant in either of the following ways:

  1. On the CLM AR server, run the CMF:USE:02_OnboardTenant_Bulk escalation by using BMC Remedy Developer Studio.

Or

  1. Log in to BMC Cloud Lifecycle Management as the Cloud Admin.
  2. Go to Cloud Lifecycle Management -> Administration Console.
  3. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Tenants.
  4. In the Tenant Management pane, click Create or import tenant .
  5. On Add Tenant dialog box, select Import Existing Tenant, complete the fields, and click Add. (For more information, see Creating and importing tenants.)

    If the tenant is already onboarded and only the People/Users data is synched, the tenant is automatically onboarded if the Company/Tenant to which they belong is already onboarded.

    If the Cloud Roles are managed BMC Cloud Lifecycle Management (and not on the Corporate ITSM server), you can allocate the Cloud End User role to all users by running the CMF:USE:01_AssignCloudEnduserEsc_Corporate escalation on the CLM AR server.

    If the Cloud Roles are managed on Corporate ITSM server, no extra step is required and the user is automatically onboarded.
 Click here for instructions for versions 4.6.00 - 4.6.03

After the ITSM Foundation data is available in the BMC Cloud Lifecycle Management server, you must execute the following escalations on that server. These escalations are available with the standard BMC Cloud Lifecycle Management software. The escalations and their sequence are:

  1. CMF:USE:00_SyncCompanyGroupID_User_Corporate – This escalation adds the required tenant groups to the user. 
  2. CMF:USE:01_AssignCloudEnduserEsc_Corporate – This escalation assigns the BMC Cloud Lifecycle Management End User permission role to all of the People User records. 
  3. CMF:USE:02_OnboardTenant_Bulk – This escalation onboards (in BMC Cloud Lifecycle Management) all of the Operating and Customer companies present in the CLM AR server. 
  4. CMF:USE:03_SyncTenantUser_Corporate – This escalation synchronizes all of the tenant users so that all of the BMC_Person records have a BMC_Organization relationship so that the users are eligible to work with BMC Cloud Lifecycle Management. 
  5. CMF:USE:04_UserSyncCall_EUP – This escalation enables users to log in to the My Cloud Services console (end user portal).
To run the escalations
  1. Log in to BMC Remedy Developer Studio as the AR System administrator (for example, Demo).
    You will be connecting to the CLM AR server.
  2. Select the correct workspace, and click OK.
  3. In the Login dialog box, enter the user name and password for the AR Administrator (for example, Demo).
  4. Click Edit Server List, provide the CLM AR Server details, and OK.
  5. Click Log In.
  6. In the AR System Navigator, under the AR System server, double-click Escalations under All Objects.
  7. To filter the escalations, in the Display items where fields, enter Name contains CMF:USE:0:.


    This displays all the escalations to be executed on ITSM Foundation data as part of initial load in the sequence listed above.

  8. Right-click the escalation you want to execute, and click Run Now.
  9. Repeat step 8 for each escalation.

    Be sure to provide enough time for each escalation to be executed completely before running the next escalation. Depending on the amount of data in each escalation, the length of time may vary. To know when an escalation has completed, you can enable AR Escalation logs. (For more information, see Enabling logs for performance issues in the BMC Remedy AR System documentation.)

Continuous synchronization of ITSM Foundation data

After the initial load is completed, complete the following steps to finalize the DSO process from Corporate ITSM AR to CLM AR for Company and People. For all other data, no other configuration is required.

Going forward, create any new Company, People, and other data in Corporate ITSM AR, and the data will be automatically synchronized.

To ensure continuous synchronization for Company data

If the AR System administrator creates a new Company (tenant) on the Corporate ITSM server, the data is transferred through DSO to CLM AR. Then, you can onboard the newly transferred tenant on BMC Cloud Lifecycle Management using either of the following steps:

  • On CLM AR Server run the escalation "CMF:USE:02_OnboardTenant_Bulk" using BMC Remedy Developer Studio

Or

To ensure continuous synchronization for People data

In BMC Cloud Lifecycle Management version 4.6.04 or later, if the Cloud Roles for users are managed on the Corporate ITSM server, no extra step is required to synchronize People data created as part of continuous synchronization from the Corporate ITSM server to BMC Cloud Lifecycle Management.              

If the Cloud Roles for users are managed on the CLM AR server, then after you import the user into BMC Cloud Lifecycle Management, you must manually assign the user to the Cloud End User role as part of continuous Synchronization.

 Click here for instructions for versions 4.6.00 - 4.6.03

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

  1. From the IT Home page on Corporate ITSM AR, select Applications > Administrator Console > Application Administration Console.
  2. In the ITSM Application Administration Console, create a People record in a company on Corporate ITSM AR.
  3. On Corporate ITSM AR, run the BMC Asset Management – Sandbox reconciliation job.

    Tip

    Consider scheduling this reconciliation job daily, weekly, monthly, or for a time frame when new users are generally created.

  4. From the IT Home page, select Applications > Atrium Core > Atrium Core Console > Applications > Reconciliation.
  5. Wait for the job to complete.
  6. Log on to CLM AR, search for the People record, assign the appropriate cloud role (for example, Cloud Admin, Cloud Organization Admin, Cloud End User) to that record, and click Save.
  7. On CLM AR, run the BMC CSM Import reconciliation job.

    Tip

    Consider scheduling this reconciliation job daily, weekly, monthly, or for a time frame when new users are generally created.

  8. Wait for the job to complete.
  9. Execute the following escalations in the sequence shown, or schedule the escalations to execute in that sequence:
    • CMF:USE:00_SyncCompanyGroupID_User_Corporate
    • CMF:USE:01_AssignCloudEnduserEsc_Corporate
    • CMF:USE:03_SyncTenantUser_Corporate
    • CMF:USE:04_UserSyncCall_EUP

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. (The Organization relationship is not added to users who are not assigned to one of these roles.) 

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

Managing cloud roles on Corporate ITSM AR server (version 4.6.00 - 4.6.03 only)

For version 4.6.00 - 4.6.03, the BMC Cloud Lifecycle Management roles that are used with the integration with BMC Remedy ITSM are managed on the CLM AR server. Alternatively, you can enable the roles management on the Corporate ITSM AR server. To do so, contact BMC Support for assistance.

Upgrade support

If you upgrade BMC Cloud Lifecycle Management to version 4.6.04, you should also upgrade the Corporate extensions as follows:

  1. Access the Corporate ITSM Integration ZipKit.
  2. Install the corporate extensions on the Corporate ITSM AR server.
    Do not install the CLM extensions on the CLM AR server or on the CLM side.
    Assuming that the ITSM Foundation extensions are upgraded, you may not need to perform the initial load using escalations.
  3. Onboard tenants as described in the Continuous synchronization of ITSM Foundation data section.
    Beginning with BMC Cloud Lifecycle Management 4.6.04, continuous synchronization of the Foundation data is automatic (except for onboarding tenants into BMC Cloud Lifecycle Management).

Related topic

Using the BMC CLM ITSM Brownfield utility

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Chandrashekhar Gosavi
    Under the section "Accessing the Corporate ITSM Integration ZipKit" please modify below line:
    "If you are using version 4.6.04, use the Remedy ITSM Integration Artifacts for CLM v4.6.04.zip file."

    TO

    "If you are using version 4.6.04 and above, use the Remedy ITSM Integration Artifacts for CLM v4.6.04.zip file."
    May 16, 2017 05:08
    1. Moiz Nalwalla

      Thanks, Chandrashekhar.

      I'll work on addressing this.

      May 24, 2017 06:30
  2. Chandrashekhar Gosavi
    Under section "Accessing the Corporate ITSM Integration ZipKit" please add below line under point #2:
    If you are on 4.6.04 and above with Extensions installed (Remedy ITSM Integration Artifacts for CLM v4.6.04.zip) and wants to upgrade to 4.6.05 and above then please don't apply Extensions again.
    May 16, 2017 06:26
    1. Moiz Nalwalla

      Thanks, Chandrashekhar.

      I'll work on addressing this.

      May 24, 2017 06:31
  3. Chandrashekhar Gosavi
    Under section "Synchronizing ITSM Foundation data for the first time (INITIAL LOAD)" refer "Step 2 – Making the synchronized data in the CLM server compatible for BMC Cloud Lifecycle Management usage", please modify first line

    "In BMC Cloud Lifecycle Management 4.6.04,"

    TO

    "In BMC Cloud Lifecycle Management 4.6.04 and above version
    May 16, 2017 06:30
    1. Moiz Nalwalla

      Thanks, Chandrashekhar.

      I'll work on addressing this.

      May 24, 2017 06:31
  4. Chandrashekhar Gosavi
    Under section "Continuous synchronization of ITSM Foundation data" refer "To ensure continuous synchronization for People data", please modify first line

    "In BMC Cloud Lifecycle Management 4.6.04,"

    TO

    "In BMC Cloud Lifecycle Management 4.6.04 and above version,"
    May 16, 2017 06:31
    1. Moiz Nalwalla

      Thanks, Chandrashekhar.

      I'll work on addressing this.

      May 24, 2017 06:31