Integrating with brownfield Remote Atrium
You can integrate BMC Cloud Lifecycle Management with existing brownfield BMC Atrium Core products installed on a remote Atrium server (Remote Atrium).
Integrating Remote Atrium with CLM specifically lets you transfer CIs from selected classes and some basic AR System forms to Remote Atrium. Here you have one central CMDB with a golden copy of data that reflects the latest version of the infrastructure.
- Remote Atrium ports and data flow process overview when transferring CIs
- Corporate extensions
- To install the corporate extension on Remote Atrium
- To install the clm extension on CLM AR
- Data that will DSO from Remote Atrium to CLM AR
- CIs that will DSO from CLM AR to Remote Atrium
- Data (AR artifacts) created when running corporate extensions
You can use existing brownfield AR System, BMC Atrium Core, or BMC Remedy IT Service Management (sometimes called Remote ITSM) for adding Company-related information (for example, their sites and people) into BMC Cloud Lifecycle Management, as shown in the following picture. You can also add IT assets created by BMC Cloud Lifecycle Management to Remote Atrium.
Remote Atrium ports and data flow process overview when transferring CIs
When you integrate BMC Cloud Lifecycle Management with Remote Atrium, the following diagram illustrates the ports and data flow used when CIs are transferred from the Remote Atrium server to the Cloud Portal and Database server (as shown below):
- Remote Atrium on port 46262 uses DSO to transfer companies and users configured in ITSM Foundation to the Cloud Portal and Database server.
- Cloud Portal and Database server on port 46200 uses DSO to transfer CMDB CIs to Remote Atrium on port 46262.
Corporate extensions
Corporate extensions (bundled with 4.0 extensions) are required for integrating Remote 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
The following tree hierarchy describes Remote Atrium integration extension in 4.0.
After Remote ITSM is ready for integration with BMC Cloud Lifecycle Management, you can install corporate extension from atrium on Remote Atrium. Similarly, after CLM AR is ready for integration with Remote Atrium, you can install the clm extension from atrium on CLM AR.
To install the corporate extension on Remote Atrium
- Copy the corporate extension from following location on CLM AR (and Enterprise-AR if there is a two AR CLM architecture) to the Remote Atrium 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 Remote Atrium while running the extension. - Launch the Atrium maintenance tool and select ExtensionLoader.xml from corporate extension.
- Enter the details of the Remote Atrium (Server name, Port, Username, and Password) and run the extension. This creates data (AR artifacts) on Remote Atrium.
- Using the Mid-Tier, connect to Remote Atrium.
- Open the Distributed Logical Mapping form.
- Search for the CLM-DESTINATION-SERVER entry and update its value with the CLM AR hostname or IP Address.
- Open the AR Server Information form, click the Connection tab, and then add the DSO server details (CLM AR)
To install the clm extension on CLM AR
- Add an AR Distributed Server license to the Remote ITSM server.
Open armonitor.conf or armonitor.cfg, uncomment the dsoj entry, and then save your changes.
For example:"C:\Program Files\Java\jre7\bin\java" -Xmx512m -classpath "C:\Program Files\BMC Software\ARSystem\dsoj;C:\Program Files\BMC Software\ARSystem\dsoj
\ardsoj81_build001.jar;C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arapi81_build001.jar;C:\Program Files\BMC Software\ARSystem
\arserver\api\lib\arcmnapp81_build001.jar;C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arutil81_build001.jar"
com.bmc.arsys.dsoj.DSOServer -i "C:\Program Files\BMC Software\ARSystem" -m- Restart the AR System server.
- Locate the clm extension from 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
Or you can run extensions from remote system where this clm extension is copied and point to the CLM AR while running the extension. - Launch the Atrium maintenance tool and select ExtensionLoader.xml from clm extension.
- Enter details of the CLM AR (Server name, Port, Username, and Password) and run the extension.CLM AR if there is a single AR CLM architectureEnterprise AR if there is a two AR CLM architectureThis create data (AR artifacts) on CLM AR.
- Using the Mid-Tier, connect to CLM AR.
- Open the Distributed Logical Mapping form.
- Search for the CORPORATE-DESTINATION-SERVER entry and update its value with the Remote Atrium hostname or IP Address.
- Open the AR Server Information form, click the Connection tab, and then add the DSO server details (Remote Atrium).
Data that will DSO from Remote Atrium to CLM AR
DSO will transfer the following Company, Site, and People data from Remote Atrium to CLM AR:
- COM:Company
- CTM:People Organization
- CTM:People
- SIT:Site
- Roles
- User
- Groups
CIs that will DSO from CLM AR to Remote Atrium
DSO will transfer the following CIs from CLM AR to Remote Atrium:
- 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 on Remote Atrium when you run atrium or corporate_extensions.
Data | Description |
|---|---|
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 Remote ITSM Integration - Remote Atriumtifacts 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 |
|
Filters |
|
Reconcilation job | BMC CSM Import (standard job with identification and merge activities) |
Dataset | BMC.IMPORT_CSM |
The following data (AR artifacts) are created on CLM AR when you run atrium or clm extensions.
Data | Description |
|---|---|
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 Remote 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 |
|
Filters |
|
Initial Load escalations |
|