In TrueSight Capacity Optimization (TSCO): license.xml file does not breakdown the entities in the audit count. How to get the entities for the license? - INCLUDES VIDEO

Version 3
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Capacity Optimization


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    TrueSight Capacity Optimization (All versions)



    PROBLEM:

    The TrueSight TrueSight Capacity Optimization (TSCO) license.xml file does not breakdown the entities in the audit count. How to get the entities for the license?


    SOLUTION:

    You can watch this video to understand how to generate managed servers report for license count:



    TSCO 10.7 and later

     

      In TrueSight Capacity Optimization (TSCO) 10.7 and later the template is a part of the product you can use it in this way:  
     
    - Go to "All Domains" in Workspace > All Domains   
     
      User-added image 
     
    - Click Add works and select Add report   
     
     
      User-added image 
     
    - select  Advanced Report - based on an Advanced Report Template  
     
      User-added image 
     
    - Select Template Group Diagnostic and Template 'Auditing - Managed Servers'.  
     
      User-added image 
     
    - Run the Report.  
     
      User-added image
      
    TSCO 10.3 and TSCO 10.5
       
      There is a new report available to get the license information from TSCO. The report is called "BCO_AllManagedServers". The rptdesign file is attached to this article. Below are the installation and the run details:  
     
      Import rptdesign file:  
     
    - go to Administration > TEMPLATE MANAGEMENT > Report templates   
    - select "Add a new advanced report template"   
    - Add name of report "BCO_AllManagedServers" (remaining fields can stay as the default)   
    - in the Template file click the upload and select the BCO_AllManagedServers_xls_All.rptdesign file   
    - Click Save   
     
      Run Report:  
     
    - Go to "All Domains" in Workspace > All Domains   
    - Click Add works and select Add report   
    - Select "Advanced Report - based on an Advanced Report Template"   
    - Select Template group 'Custom' in dropdown   
    - In Template select the template name 'BCO_AllManagedServers'  
     
    Once you run the report you can click the refresh for  the report output until the data is available. Then open the XLS file with Excel to look at the breakdown of systems for the license count. The breakdown of the Audit count listed in the license.xml will be available in the new report.   
     
    The report is valid for Oracle and Postgres databases in TSCO 10.3. 
      

    Additional Information

    Some key points in relation to licensing are: 
      (A) Each "licensed end-point" is only counted once from a licensing perspective regardless of how many different ETLs are reporting data for that entity.  This is even true if different ETLs are reporting data to separate entities (multilple sysids in TSCO).  The licensing will automatically collapse multiple entities of the same name together and count them as a single licensed entity. 
      (B) Each entity defined in TSCO uses a "license" regardless of the last time that entity reported data. 
      (C) The count used for licensing from the "Auditing - Managed Servers" report is the "Sheet 1: Overall number of managed servers - distinct by name" value 
      (D) Business Driver entities defined in TSCO will not be counted as licensed entities 
      (E) Using the "Auditing - Managed Servers" output an adjusted license count can be proposed as the correct count (adjusting what the license report suggests) as long as each removed entity is justified.  For example, if there were a lot of entities where there was an entity called 'hostname' and another called 'hostname - old' and these were shown to be duplicates those could be manually adjusted out of the licensed entity count (or they could be reconciled within TSCO itself to collapse them back to a single entity).  Technical Support can assist with that discussion. 
      

     


    Article Number:

    000340812


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles