BMC - TrueSight Operations Management 9.0/9.5/9.6/10.0 extractor

Integrating TrueSight Capacity Optimization with TrueSight Operations Management enables you to view capacity-related events in ProactiveNet from TrueSight Capacity Optimization, and allows you to launch TrueSight Capacity Optimization from ProactiveNet. This ETL extracts performance and configuration data from a TrueSight Operations Management Sybase or Oracle database. Use this extractor to load data collected by the Windows and UNIX Knowledge Modules.


Best Practice

ProactiveNet Performance Management or TrueSight Infrastructure Management has a scheduled refresh of its data once a day. By default, the refresh starts at 3:30 A.M. Ensure that the ETL run is scheduled after this refresh completes.

This topic contains the following sections:

Integration requirements

The following table lists the requirements for this integration.

Supported version of data source

Supported platforms

  • BMC ProactiveNet 9.0
  • BMC ProactiveNet 9.5
  • BMC ProactiveNet 9.6
  • BMC TrueSight Infrastructure Management 10.0

For details, see Integrating with BMC TrueSight Capacity Optimization with BMC ProactiveNet.

  • Supported virtualization platforms:
    • IBM AIX (AIX Host, LPARs, SPLPARs, DLPARs, POOL, WPARs).
    • Oracle Solaris (LDOM Host, Zone Host, LDOMs, Zones)
    • Stand-alone hosts are supported for Microsoft Windows, Linux, AIX, HP-UX, and Solaris platforms.
  • Supported databases:
    • Sybase (Standalone UNIX and Windows, and Solaris/AIX virtualization)
    • Oracle (Standalone UNIX and Windows, and Solaris/AIX virtualization)
  • Versions of the PATROL Agents, Windows/UNIX KMs, and databases compatible with this integration:
    • Windows KM: Versions 4.5.00 and 4.6.00 of the BMC ProactiveNet Microsoft Windows Server Monitoring KM. Works with BMC PATROL Agent versions 3.9.00 and 9.0.00.
    • Unix KM: Version 9.11.00 of the BMC ProactiveNet UNIX and Linux - Solaris and AIX Monitoring KM and works with BMC PATROL Agent versions 3.9.00 and 9.0.00. For more information, see Integrating with TrueSight Operations Management.

This integration is supported only for systems that are locally monitored by the PATROL KMs, except for Standalone Linux platform (which supports systems that are remotely monitored).

Note

This integration provides additional metrics and relationships that allow a proper management of partitioned UNIX systems, now supported in this version.

Specific versions of PATROL Agents, and Windows/UNIX KMs are required to ensure that these additional metrics and relationships are collected and published to the BMC ProactiveNet database.

Integration steps

To integrate TrueSight Capacity Optimization with the ProactiveNet Database Extractor, perform the following task:

  1. Navigate to Administration > ETL & SYSTEM TASKS > ETL tasks.
  2. In the ETL tasks page, click Add > Add ETL under the Last run tab.
  3. In the Add ETL page, set values for the following properties under each expandable tab.

    Note

    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.

    Basic properties

    Property Description
    Run configuration
    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.
    Deploy status 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.
    • 1 - Light: Add bare minimum activity logs to the log file.
    • 5 - Medium: Add medium-detailed activity logs to the log file.
    • 10 - Verbose: Add detailed activity logs to the log file. Info,

    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.
    Module selection

    Ensure that the Based on datasource option is selected.

    Note

    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 - TrueSight Operations Management 9.0/9.5/9.6/10.0 extractor.
    Module description A link in the user interface that points you to this technical document for the ETL.
    Platform Select any one of the following platforms:
    • Standalone (any OS)
    • AIX Power VM/WPAR
    • Solaris LDOM/Zone/DSD
    • KVM
    Data type Default performance data type is enabled.
    Extraction days Enter the number of extraction days.
    Entity catalog
    Sharing status Select any one:
    • Shared entity catalog: Select this option if, for the same entities, data is coming from multiple sources. For example, BPA ETL.
      • Sharing with Entity Catalog: Select an entity catalog from the drop-down list.
    • Private entity catalog: Select this option if, for the same entity, data is coming from a single source.
    Object relationships
    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.

    Additional Information

     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.

    Select any one of the following options:

    • New domain: Create a new domain. Specify the following properties under New domain:
      • Parent: Select a parent domain for your new domain from the domain selector control.
      • Name: Specify a name for your new domain.
    • Existing domain: Select an existing domain. Make a selection for the following property:
      • Domain: Select an existing domain from the domain selector control.
    Connection parameters
    Datasource type Select any one:
    • Select existing datasource
      • Datasource: Select a datasource from the drop down list.
    • Custom datasource
      • Database type: Select a database type from the drop down list. 

      • Database user: Type in the database user name.

      • Database password: Enter the database password.

      • Database TNS name (Applies to Oracle): Type in the Database TNS name.

      • Data source name (Applies to Microsoft SQL Server/Sybase): Type in the data source name.

      • Database name (Applies to Microsoft SQL Server/Sybase): Type in the database name.

      • Connection URL (Applies to Other database): Enter the connection URL.

    ETL task properties
    Task group Select a task group to classify this ETL into.
    Running on scheduler Select the scheduler you want to run the ETL on.
    Maximum execution time before warning The number of hours, minutes or days to to execute the ETL for before generating warnings, if any.
    Frequency Select the frequency of ETL execution. Available options are:
    • Predefined: Select a Predefined frequency from Each Day, Each Week or Each Month.
    • Custom: Enter a Custom frequency (time interval) as the number of minutes, hours, days or weeks to run the ETL in.
    Start timestamp: hour\minute (Applies to Predefined frequency) The HH:MM start timestamp to add to the ETL execution running on a Predefined frequency.
    Custom start timestamp Select a YYYY-MM-DD HH:MM timestamp to add to the ETL execution running on a Custom frequency.

    Note

    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.

    Advanced properties

    Property Description
    Run configuration
    Datasets

    Enables you to select or deselect metric groups for which data will be populated 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.

    1. Click Edit.
    2. Select one (click) or more (shift+click) datasets that you want to exclude from Available datasets and click >> to move them to Selected datasets.
    3. Click Apply.
    Extraction days Specify the number of days.
    Default last counter Set the default last counter in dd/mm/yyy hh:mm:ss format.
    Collection level
    Metric profile selection

    Select any one:

    • Use Global metric profile: Select this to use an out-of-the-box global profile, that is available on the Adding and managing metric profiles page. By default, all ETL modules use this profile.
    • Select a custom metric profile: Any metric profiles you add in the Add metric profile page (Administration > DATAWAREHOUSE > Metric profiles).

    For more information, see Adding and managing 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:

    • [1] Essential
    • [2] Basic
    • [3] Standard
    • [4] Extended

    For more information, see Aging Class mapping.

    Metric filter
    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.

    Additional properties
    List of properties

    Additional properties can be specified for this ETL that act as user inputs during execution. You can specify values for these properties either at this time, or from the "You can manually edit ETL properties from this page" link that is displayed for the ETL in view mode.

      1. Click Add.
      2. Add an additional property in the etl.additional.prop.n box.
      3. Click Apply.
        Repeat this task to add more properties.
    Loader configuration
    Empty dataset behavior Choose one of the following actions if the loader encounters an empty dataset:
    • Warn: Abort the loader.
    • Ignore: Ignore the empty dataset and continue parsing.
    ETL log file name Name of the file that contains the ETL execution log; the default value is: %BASE/log/%AYEAR%AMONTH%ADAY%AHOUR%MINUTE%TASKID
    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: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID.
    BCO loader output file name Name of the file generated by the BMC TrueSight Capacity Optimization loader; the default value is: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID.
    Detail mode Select the level of detail:
    • Standard: Data will be stored on the database in different tables at the following time granularities: Detail (configurable, by default: 5 minutes), Hourly, Daily, Monthly.
    • Raw also: Data will be stored on the database in different tables at the following time granularities: Raw (as available from the original data source), Detail (configurable, by default: 5 minutes), Hourly, Daily, Monthly.
    • Raw only: Data will be stored on the database in a table only at Raw granularity (as available from the original data source).

    For more information on granularities, see Accessing data using public views and Sizing and scalability considerations.

    Reduce priority
    • Normal:
    • 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, server.domain.com will be saved as server.
    Leave domain suffix to system name (Only for systems) If set to True, the domain name is maintained in the system name. For example: server.domain.com will be saved as such.
    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 TrueSight Capacity Optimization. It uses one of the other ETLs that share lookup to create the new entity.
    Scheduling options
    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:
    • False(Default): While a particular task is already running, if the next execution command arises – it is ignored.
    • True: While a particular task is already running, if the next execution command arises – it is placed in a queue and is executed as soon as the current execution ends.
  4. Click Save.
    You return to the Last run tab under the ETL tasks page.
  5. Validate the results in simulation mode: In the ETL tasks table under ETL tasks > Last run, locate your ETL (ETL task name), click  to run the ETL.
    After you run the ETL, the Last exit column in the ETL tasks table will display one of the following values:
    • OK: The ETL executed without any error in simulation mode.
    • WARNING: The ETL execution returned some warnings in simulation mode. Check the ETL log.
    • ERROR: The ETL execution returned errors and was unsuccessful. Edit the active Run configuration and try again.
  6. Switch the ETL to production mode: To do this, perform the following task:
    1. In the ETL tasks table under ETL tasks > Last run, click the ETL under the Name column.
    2. In the Run configurations table in the ETL details page, click  to edit the active run configuration.
    3. In the Edit run configuration page, navigate to the Run configuration expandable tab and set Execute in simulation mode to No.
    4. Click Save.
  7. Locate the ETL in the ETL tasks table and click  to Run it, or schedule an ETL run.
    After you run the ETL, or schedule the ETL for a run, it will extract the data form the source and transfer it to the BMC TrueSight Capacity Optimization database.

This ETL needs to be configured in BMC TrueSight Capacity Optimization pointing to the BMC ProactiveNet repository database, with one of the following account configurations:

  • For sybase database: dba account
  • For Oracle database: proact account or any user having access to the BMC ProactiveNet database schema.

Setting up the connection to the Sybase database

On your BMC TrueSight Capacity Optimization ETL engine server, edit the file /opt/cpit/etl/freetds/etc/freetds.conf to configure the connectivity to your BMC ProactiveNet Sybase database. For example:

[BPPMSYBASESERV]
    host=<your_server_ip>
    port = 2638
    tds version=5.0

For additional detail on data source configuration, see Configuring database connection using Perl or Java ETLs.

Lookup details

  • Strong fields:
    1. TOKEN_ID
    2. HOSTNAME
  • Weak fields
    1. NAME
    2. _COMPATIBILITY_

TrueSight Infrastructure Management integration mapping parameters

The following table lists all mapping parameters for the integration of TrueSight Capacity Optimization with BMC ProactiveNet.

Note

Download the attached PDF files to view the complete list of parameter mappings. Empty cells in the BMC ProactiveNet column represent derived TrueSight Capacity Optimization metrics that do not have a corresponding BMC ProactiveNet metric mapping.

TrueSight Capacity Optimization version →
Platform ↓
9.09.510.010.3
AIXDownloadDownloadDownloadDownload
SolarisDownloadDownloadDownloadDownload
Standalone

Download

DownloadDownloadDownload
KVM---Download

Additional debugging information for BMC ProactiveNet Sybase database

The connector performs data extraction in two stages:

  • Discovering the entities in the BMC ProactiveNet Sybase database.
  • Extracting performance, configuration, and relationship data about these entities.

Below we describe in more detail the discovery stage for top level entities for each platform, for help in diagnosis, for Sybase database. In below queries, <schemaOwner> should be replaced by the schema owner, as the prefix for table or view name. For example, dba."_PATROL__UNIX_OS_CFG_VIEW" or dba.autodiscovery_inst_cfg

  • Standalone UNIX systems

    BMC ProactiveNet 9.0
    select DISTINCT DEVICENAME from <schemaOwner>."_PATROL__UNIX_OS_CFG_VIEW" where upper(ENTITYTYPE) like '%STANDALONE%' AND MOINSTID in (select instid from <schemaOwner>.autodiscovery_inst_cfg where flag=0)
    BMC ProactiveNet 9.5
    select DISTINCT DEVICENAME from <schemaOwner>."_PATROL__UNIX_OS_CFG_VIEW" where upper(ENTITYTYPE) like '%STANDALONE%' AND MOINSTID in (select itemid from <schemaOwner>.item_cfg where mfd=0)
  • Standalone Windows systems

    BMC ProactiveNet 9.0
    select DISTINCT DEVICENAME from <schemaOwner>."_PATROL__NT_OS_CFG_VIEW" where upper(ENTITYTYPE) like '%STANDALONE%' AND MOINSTID in (select instid from <schemaOwner>.autodiscovery_inst_cfg where flag=0)
    BMC ProactiveNet 9.5
    select DISTINCT DEVICENAME from <schemaOwner>."_PATROL__NT_OS_CFG_VIEW" where upper(ENTITYTYPE) like '%STANDALONE%' AND MOINSTID in (select itemid from <schemaOwner>.item_cfg where mfd=0)
  • AIX (IBM PowerVM) hosts

    BMC ProactiveNet 9.0/9.5
    select DISTINCT USERNAME from <schemaOwner>.DEVICE_CNTL where DEVICETYPE = 31
  • Solaris LDOM hosts

    BMC ProactiveNet 9.0
    SELECT DISTINCT DEVICENAME from <schemaOwner>."_PATROL__UNIX_OS_CFG_VIEW" where upper(ENTITYTYPE) like '%SUN.LDOM.PRIMARY%' AND MOINSTID in (select instid from <schemaOwner>.autodiscovery_inst_cfg where flag=0)
    BMC ProactiveNet 9.5
    SELECT DISTINCT DEVICENAME from <schemaOwner>."_PATROL__UNIX_OS_CFG_VIEW" where upper(ENTITYTYPE) like '%SUN.LDOM.PRIMARY%' AND MOINSTID in (select itemid from <schemaOwner>.item_cfg where mfd=0)
  • Solaris Zone hosts

    BMC ProactiveNet 9.0
    SELECT DISTINCT DEVICENAME from  <schemaOwner>."_PATROL__UNIX_OS_CFG_VIEW"  where upper(ENTITYTYPE) like '%SUN.ZONE.HOST%' AND MOINSTID in (select instid from <schemaOwner>.autodiscovery_inst_cfg where flag=0)
    BMC ProactiveNet 9.5
    SELECT DISTINCT DEVICENAME from  <schemaOwner>."_PATROL__UNIX_OS_CFG_VIEW"  where upper(ENTITYTYPE) like '%SUN.ZONE.HOST%' AND MOINSTID in (select itemid from <schemaOwner>.item_cfg where mfd=0)
  • KVM hosts

    BMC TrueSight Infrastructure Management 10.0
    SELECT DISTINCT DEVICENAME from <schemaOwner>."_PATROL__UNIX_OS_CFG_VIEW" where upper(ENTITYTYPE) like '%KVM.HOST%' AND MOINSTID in (select itemid from <schemaOwner>.item_cfg where mfd=0)

Related topics

Integrating with TrueSight Operations Management

Using ETL datasets

Developing custom ETLs

Dataset reference for ETL tasks

Horizontal and Vertical datasets

Viewing datasets and metrics by dataset and ETL module

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

Comments