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.

Transferring business service data from BMC Atrium CMDB to BMC Server Automation

BMC Server Automation does not support the concept of business services. By looking at a particular server managed by BMC Server Automation, it is not possible to determine which business services might be affected if the server changes. However, business service information is available in BMC Atrium CMDB. Transferring data from BMC Atrium CMDB to the BMC Server Automation database pulls business service information from BMC Atrium CMDB and associates it with the corresponding servers in BMC Server Automation as a custom property.

You can then create smart groups based on this custom property to determine the relationships between business services and servers.

Transferring data from BMC Atrium CMDB to the BMC Server Automation database involves importing a list of affected business services and Virtual Life Cycle Data. This process is implemented as a special Synchronization Job type called the Atrium Import Job. All instances of the Atrium Import Job share a common configuration.

Note

Enabling the BMC BladeLogic Atrium Integration is a prerequisite for Atrium Import Jobs. See Enabling BMC BladeLogic Atrium Integration for more details.

Configuring and scheduling a Synchronization Job

  1. Select Atrium Integration > Configuration from the Configuration menu and enter the following BMC Atrium CMDB details on the AR/CMDB Configuration tab:

    Parameter

    Description

    Host Name/IP Address

    host name or IP address of the computer where BMC Atrium CMDB is installed

    CMDB Port

    port used for communicating with BMC Atrium CMDB
    Note: If you are using a portmapper service for BMC Remedy AR System, specify a value of 0.

    CMDB User

    user name for connecting to BMC Atrium CMDB

    CMDB Password

    password for connecting to BMC Atrium CMDB

  2. Click Test Connection to verify that the credentials that you entered are correct.
  3. In the BMC Server Automation console, select Configuration > Atrium Integration > Atrium Import Job Configuration from the menu bar.
  4. In the Atrium Import Job Configuration tab, click to open each of the five groups of configuration parameters.
  5. Specify values for the configuration properties ad described in the following table:

    Configuration property

    Description

    General Atrium CMDB Details

    Production Dataset name

    The name of the BMC Atrium CMDB production dataset (BMC Asset)

    List of Computer System class names

    The computer system class names Only instances of these classes are transferred from BMC Atrium CMDB while the impact on the business services is determined. The class names must be specified in the following format: nameSpace: className (, BMC.CORE:BMC_BaseElement ).

    CMDB multi-tenancy attribute name

    BMC Atrium CMDB attribute name used to verify the company name Default value is AccountID. If this attribute is not available, you can specify any attribute of the BMC_BaseElement class to use instead.

    Company name

    Company name is compared with the value in the CMDB attribute as set in CMDB multi-tenancy attribute name. Business services are copied to BMC Server Automation from the CMDB only if the two company names match. If you do not specify a value, all business services and computer systems are analyzed and transferred to BMC Server Automation.

    Business Service and its Associations Details

    Business Service class name

    The name of the business service class , BMC Atrium CMDB provides the BMC_BusinessService class to identify business services. The class name must be specified in the following format: nameSpace: className (, BMC.CORE:BMC_BusinessService ).

    Relationship linking Business Service and Infrastructure CI

    The name of the relationship class that links business service CIs to infrastructure CIs. The class name must be specified in the following format: nameSpace: className (, BMC.CORE:BMC_Dependency ).

    Relationship linking Business Service CIs

    The name of the relationship class that links business service CIs to business service CIs You can edit this property if the class name is other than BMC_Dependency. The class name must be specified in the following format: nameSpace: className (, BMC.CORE:BMC_Dependency ).

    Direction of relationship linking Business Service CIs

    The direction of the connection between the business service CIs If the business service CI is the source of the relationship instance connecting it with another business service CI, the value is OUT. If the business service CI is the destination of the relationship instance connecting it with another business service CI, the value is IN.

    Use Service Impact relationship to traverse Infrastructure CIs

    Service Impact relationship class name

    The name of the relationship class that is used to associate impact and direction among CIs The name must be specified in the format: nameSpace: className{}
    Example: BMC.CORE:BMC_BaseElement

    Direction of Service Impact relationship

    The direction of the impact from the infrastructure CI (which is connected to the business service) to another CI (or Computer System CI). This property can have one of the following values: IN or OUT.

    List of Infrastructure CI class names

    A list of class names used to represent Infrastructure CIs
    Example: BMC.CORE:BMC_SoftwareServer or BMC.CORE:BMC_Application

    Use Infrastructure CI Class Name(s) to traverse Infrastructure CIs

    List of Infrastructure CI class names

    A list of class names used to represent Infrastructure CIs (, BMC.CORE:BMC_SoftwareServer or BMC.CORE:BMC_Application )
    *Note:* Use this property only if BMC Service Impact Manager is not present.

    Direction of relationship linking Infrastructure CIs

    The direction of the relationship linking the CI (connected to a business service) to another CI (or the Computer System CI). This property can have one of the following values: IN or OUT.

    Depth of CI graph traversal

    The maximum number of levels that must be traversed from the infrastructure CI to reach the impacting computer system CI The default value is 0, which means unlimited.

    BladeLogic Property Details

    Server custom property to store impacted Business Services

    A read-only property that represents the name of the server class custom property that is used by the Atrium Import Job to store business service names that are impacted by BMC Server Automation managed servers

    Custom property value separator

    The separator used to separate multiple business service names The default separator is a comma (,).

    Virtual Life Cycle Data

    VSSD Class Name

    The name of class that stores Virtual System Setting Data. , BMC Atrium CMDB provides the BMC_VirtualSystemSettingData class, which stores Virtual Life Cycle Data such as Owner, Proposed Expiry Date, Reconciliation Id, and Creation Date. The class name must be specified in the following format: nameSpace:className (, BMC.CORE: BMC_VirtualSystemSettingData)

    Rel Linking VSSD & CIs

    The name of the relationship class that links Virtual System Setting Data CIs to Computer System CIs. The class name must be specified in the following format: nameSpace:className (, BMC.CORE:BMC_SettingsOf).

  6. Click the Save icon.
  7. Open the Jobs workspace and create a job folder to store your Synchronization Job.
  8. Right-click a job folder and select New > Atrium Import Job.
  9. Enter a name and optional description for the job.
  10. Select a folder for the job, and then click Next.
  11. ( optional ) Set up job run notifications.
  12. Click Next.
  13. Select the appropriate option:
    • To run the job immediately, select Execute job now.
    • To schedule the report to run at another time or periodically, click the New Schedule icon .
    • To run the job manually later, select no option, and then click OK.
  14. Click Next.

    Note

    Because business service CIs change infrequently, you can initially set the schedule to run weekly. You can reset the schedule later to run more often.

  15. ( optional ) Select a property and then click the Edit Property icon .
  16. Click Next.
  17. ( optional) Use the controls to add, change, or delete permissions.

    Note

    For more information about these features, see Permissions and Properties.

  18. Click Finish.
  19. ( optional ) To run the Synchronization Job manually, if you did not make a selection in step 13, right-click the job and select Execute.
Was this page helpful? Yes No Submitting... Thank you

Comments