This topic describes how to integrate BMC TrueSight Capacity Optimization with BMC Atrium Configuration Management Database (CMDB). This ETL extracts service-system and application-system relationships from an Atrium CMDB database. Use this extractor to automatically place systems in the BCO service tree according to your master enterprise CMDB. Configuration and performance data for the systems should simultaneously be loaded using another connector. Use this extractor if your enterprise CMDB is using the standard, unmodified BMC Unified Service Model. If your enterprise CMDB has customizations, then you might need to create a custom relationship extractor.
This topic contains the following sections:
|Connector name||Supported version of BMC Atrium CMDB|
|BMC - Atrium CMDB extractor||7.5, 7.6, 7.6.03, 7.6.04, 8.0, 8.1, 8.1.02, 9.0, 9.1+, 9.1.01|
+ You must install Certified HotFix CMDB_9.1.00_02FEB2016_SW00501532 to integrate with BMC Atrium CMDB 9.1. For downloading this Hotfix, contact BMC Support.
To integrate BMC TrueSight Capacity Optimization with the Atrium CMDB Parser, perform the following task:
In the Add ETL page, set values for the following properties under each expandable tab
Basic properties are displayed by default in the Add ETL page. These are the most common properties that you can set for an ETL, and it is acceptable to leave the default selections for each as is.
|ETL task name||By default, this field is populated based on the selected ETL module. You can specify a different name for the ETL Task. Duplicate names are allowed.|
|Run configuration name||Default name is already filled out for you. This field is used to differentiate different configurations you can specify for the ETL task. You can then run the ETL task based on it.|
|Environment||You can select Production or Test to mark the ETL tasks. For example, you can start by marking the task as Test and change it to Production after you have seen that you are getting what you wanted.|
|Description||(Optional) Enter a brief description for this ETL.|
|Log level||Select how detailed you want the ETL log to be. The log includes Error, Warning and Info type of log information.
Note: Log levels 5 and 10 are typically used for debugging or troubleshooting ETL issues. Using a log level of 5 is general practice, however, you may choose level 10 to get a high level of detail while troubleshooting.
|Execute in simulation mode||Select Yes if you want to to validate the connectivity between the ETL engine and the target, and to ensure that the ETL does not have any other configuration issues.
When set to Yes, the ETL will not store actual data into the data warehouse. This option is useful while testing a new ETL task.
Ensure that the Based on datasource option is selected.
If you select Based on Open ETL template, BMC TrueSight Capacity Optimization is integrated with a Generic extractor based on the selected Open ETL template. For more information, see Generic ETL based on a template.
|ETL module (BMC recommends you to make this selection first)||Select BMC - Atrium CMDB extractor.|
|Module description||A link in the user interface that points you to this technical document for the ETL.|
Enables you to select or deselect metric groups for which data will be populated from the Available datasets. The OpenStack connector allows you to choose only from the given list of datasets, and you cannot include additional datasets to the run configuration of the ETL.
|Sharing status|| Select any one:
|Associate new entities to||
Specify the domain where you want to add the entities created by the ETL. You can select an existing domain or create a new one.
By default, a new domain is created for each ETL, with the same name of the extractor module. As the ETL is created, a new hierarchy rule with the same name of the ETL task is automatically created, with an active status; if you update the ETL specifying a different domain, the hierarchy rule will be updated automatically. The hierarchy rule will be created with status ACTIVE.
Select any one of the following options:
If the domain is already used by any other hierarchy rule, a Domain conflict option is displayed. You can select one of the following solutions:
CMDB connection parameters
|CMDB server||The host name or IP address of the machine hosting the BMC Atrium server (for example: xenvm-w23-bpav7.bmc.com).|
Username having administrative privileges on the BMC Atrium server.
|Password||Password for the user.|
ETL task properties
|Task group||Select a task group to classify this ETL into. It is not necessary to group it into a task group.|
|Running on scheduler||Select the scheduler over which you want to run the ETL. The type of schedulers available are:
|Maximum execution time before warning||The number of hours, minutes, or days for which the ETL should be executed before generating warnings or alerts, if any.|
|Frequency|| Select the frequency for ETL execution. Available options are:
To view or configure Advanced properties, click Advanced. You do not need to set or modify these properties unless you want to change the way the ETL works. These properties are for advanced users and scenarios only.
|Metric profile selection||
Select any one:
For more information, see Metric profiles.
|Levels up to||
The metric level defines the amount of metric imported into the data warehouse. If you increase the level, additional load is added to the data warehouse while decreasing the metric level reduces the number of imported metrics.
Choose the metric level to apply on selected metrics:
For more information, see Aging Class mapping.
|Metric list <for selected dataset>||
Click Edit and select the metrics that will be loaded for each dataset that you selected under Run configuration > Datasets. If no metric is specified, all metrics will be loaded.
CMDB connection parameters
Specify the TCP port number that is used by BMC Atrium. The Atrium administrator can provide this port number.You need to specify this port number only if the BMC Remedy AR system server is not registered with a portmapper or if a Port 111 firewall blocks the portmapper port. Otherwise, you do not need to specify the port number because the portmapper automatically locates the port. For more information, see .
|Use UUID for VMware vms||Specify if the UUID should be used instead of the VM name to identify VMware guest machines.|
|Import VMware Data||Import VMware host and guest machines.|
|Whitelist file path||
|Blacklist file path||
|List of properties||
Additional properties can be specified for this ETL that act as user inputs during execution.
|Empty dataset behavior||Choose one of the following actions if the loader encounters an empty dataset:
|ETL log file name||Name of the file that contains the ETL execution log; the default value is:
|Maximum number of rows for CSV output||A number which limits the size of the output files.|
|CSV loader output file name||Name of the file generated by the CSV loader; the default value is:
|Capacity Optimization loader output file name||Name of the file generated by the BMC Capacity Optimization loader; the default value is:
|Detail mode|| Select the level of detail:
Select either Normal or High.
|Remove domain suffix from datasource name||(Only for systems) If set to True, the domain name is removed from the data source name. For example,
|Leave domain suffix to system name||(Only for systems) If set to True, the domain name is maintained in the system name. For example:
|Update grouping object definition||If set to True, the ETL will be allowed to update the grouping object definition for a metric loaded by an ETL.|
|Skip entity creation||(Only for ETL tasks sharing lookup with other tasks) If set to True, this ETL does not create an entity, and discards data from its data source for entities not found in BMC Capacity Optimization. It uses one of the other ETLs that share lookup to create the new entity.|
|Hour mask||Specify a value to execute the task only during particular hours within the day. For example, 0 – 23 or 1,3,5 – 12.|
|Day of week mask||Select the days so that the task can be executed only during the selected days of the week. To avoid setting this filter, do not select any option for this field.|
|Day of month mask||Specify a value to execute the task only during particular days within a month. For example, 5, 9, 18, 27 – 31.|
|Apply mask validation||By default this property is set to True. Set it to False if you want to disable the preceding Scheduling options that you specified. Setting it to False is useful if you want to temporarily turn off the mask validation without removing any values.|
|Execute after time||Specify a value in the hours:minutes format (for example, 05:00 or 16:00) to wait before the task must be executed. This means that once the task is scheduled, the task execution starts only after the specified time passes.|
|Enqueueable|| Select one of the following options:
The connector defines multiple lookup fields for coordinating with other connectors. The following table lists the sequence of field sets for strong lookup and weak lookup.
|Entity Type||Strong lookup fields||Weak lookup fields|
|Generic||RECONCILIATION_ID; INSTANCE_ID||HOSTNAME; NAME|
Virtual Host - AIX PowerVM, Virtual Host - Solaris, Virtual Host - VMware, Virtual Machine - AIX LPAR, Virtual Machine - Solaris LDOM, and Virtual Machine - Solaris Zone
Virtual Machine - VMware
HOSTNAME; UUID; NAME
Metrics supported by the SYSCNF dataset
|BMC TrueSight Capacity|
|CMDB Class Name||CMDB Attribute||Comment|
|Add number of Cores for all BMC_processor instances|
|Add MaxClockSpeed for all BMC_Processor instances|
|Get number of instances of BMC_DiskDrive|
|DriveSize||Add DriveSize for all BMC_DiskDrive instances|
Populated object relationships
|Relationship name||Source entity||Destination entity||Meaning|
LDOM contains zone
VMware Host contains a VM. This relationship is hidden in the UI.
|CONTAINS||Business service||Business service||Business service depends on the child business service.|
|CONTAINS||Business service||Computer System|
(Stand alone physical machine, LPAR, LDOM, ZONE, VMware Host, VM)
(Stand alone physical machine, LPAR, LDOM, ZONE, VMware Host, VM)
For more information on how to extract object relationships dataset; see: Writing an extractor for a CMDB - Object Relationships dataset
The hierarchy rule will be used to process object relationships, and will run automatically, as part of the daily run.
The configured Atrium user should have administrative privileges on the BMC Atrium server, so that BMC Atrium can be scanned to fetch information about computer systems, hardware configuration, and business service instances.
The ETL fetches only BMC_ComputerSystem CMDB Class Name instances. You can get BMC_ComputerSystem instances having following instance values:
The BMC Atrium CMDB connector discovers standalone machines and the following for different platforms:
It also discovers business services and related computer systems.
Computer systems related to business services will be discovered on the basis of their being final destinations, originating from a computer system as a source (in the figure below, see the arrow pointing upwards towards the business service from the Computer System).
Classes and relationships
When a CMDB model is created through a typical ADDM Computer systems – Application population, with the Computer system as the source and Application as the destination, (in the preceding figure, see the arrow pointing towards the Application from computer system) a user can typically extend the model by selecting a Business Service as a destination.
The output in BMC TrueSight Capacity Optimization is a hierarchy that displays a domain tree for each business service and related business services/technical services within that, if any, and the associated computer systems.
For sharing lookup of BMC Atrium CMDB connector with Gateway Server connector, ensure that the BMC Atrium CMDB connector removes the domain suffix from the data source name.
For more information, see Handling BMC TrueSight Capacity Optimization ETL lookup name. Also, ensure that Import VMware Data option as found in CMDB connection parameters inAdvanced configuration is False, as this is not currently supported, while sharing the lookup with Gateway Server connector.