Skip to Content

Generic - Tag CSV file parser

The Generic - Tag CSV file parser ETL enables you to manage the tags for entities that are imported by other ETLs. You can use the Generic - Tag CSV file parser to perform the following tasks:

  • Automatically apply tags to the entities that are imported by other ETLs in the shared entity catalog
  • Remove tags from the required entities

The ETL uses lookup fields to identify the required entities from the shared entity catalog and the TAGDAT dataset to manage tags. To configure the ETL, use an input CSV file that is structured according to the dataset and share the entity catalog of the ETL that is collecting the required entities. When you run the Generic - Tag CSV file parser, depending on the Tag type (single value or multiple value) and operation (ADD or DELETE), tags are automatically updated in the required entities. If the Tag type or Tag is not available, this ETL creates the required Tag type or Tag and updates the required entities.  If there are new entities that are not available in the entity catalog, the ETL enables you to add or manage (includes option to skip entity creation) the new entities.

For more information, refer to the following sections:

Related topics

Dataset-reference-for-ETL-tasks

Using-ETL-datasets

Generic-CSV-file-parser

Horizontal and Vertical datasets

Viewing-datasets-and-metrics-by-dataset-and-ETL-module

Workflow


Generic Tag CSV.png

Before you integrate

Configuration steps

To integrate BMC Helix Continuous Optimization with the Generic - Tag CSV file parser, 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.

    Warning

    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

    Warning

    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


  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 run_etl.png 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 edit_button.gif 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 run_etl.png 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 Helix Continuous Optimization database.

Input file format

The input file follows the open ETL structure. You cannot use the following characters in the input file for a tag type or tag:

"[", "]", "%", "<", ">", "\\", "^", "'", ",", ";", ":", "|", "*", "&", "\"", "!", "?", "&", "$", "£", "{", "}", ")", "(", " ", "~"

Following are the sample input files that use different type of lookup fields:

  • Input file that uses single lookup (DS_ENTNM):

    ENTCATNM,DS_ENTNM,ENTNM,TAG,TAGTYPE,ENTTYPENM
    SYS,vmsingle1,vmsingle1,Production,MailSubsystem,Env,gm:vmw
    SYS,vmsingle2,vmsingle2,QA,Env;gm:vmw

  • Input file that uses multiple lookup (STRONGLOOKUPFIELDS and WEAKLOOKUPFIELDS):

    ENTCATNM,DS_ENTNM,ENTNM,TAG,TAGTYPE,ENTTYPENM,STRONGLOOKUPFIELDS,WEAKLOOKUPFIELDS,OPERATION
    SYS,HOSTNAME#vm888.bmc.com##NAME#vm888,vm888,Production;MailSubsystem,Env,gm:vmw,HOSTNAME,NAME,
    SYS,HOSTNAME#vm888.bmc.com##NAME#vm888,vm888,MailSubsystem,Env,gm:vmw,HOSTNAME,NAME,DELETE
    SYS,HOSTNAME#vm999.bmc.com##NAME#vm999,vm999,QA,Env,gm:vmw,HOSTNAME,NAME,

    The above mentioned sample also provides an example for adding multiple tags (separated by ;) and deleting a tag (by specifying the operation type) from the required entity.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix Continuous Optimization 22.3