Jump to main content
HCL Logo Product Documentation
Customer Support HCLSoftware U Community Forums Customer Idea Portal
  • BigFix Documentation Homepage
  • BigFix 10 Inventory Documentation
  • Overview
  • Installing
  • Configuring
  • Upgrading
  • Managing the infrastructure
  • Software inventory and license utilization
  • Managing security threats
  • Tutorials
  • Security
  • Troubleshooting and support
  • Tuning performance
  • Integrating with REST API
  • Glossary
  • Guide in PDF format
  1. Home
  2. Software inventory and license utilization

    You can classify the discovered software so that reports in BigFix Inventory reflect your entitlements and properly show utilization of license metrics by particular products.

  3. Server Software Catalog

    To correctly identify components of software products in your infrastructure, ensure that your server software catalog is always up-to-date. Periodically import a new server software catalog that contains the most recent software products. Also, manually add products that are installed in your infrastructure but do not have corresponding entries in the catalog.

  4. Expanding the custom software catalog

    To ensure that all software items that are installed in your infrastructure are discovered, create custom signatures. You can create them from scratch or directly from the Package Data and Scanned File Data reports. You can also create extended signatures to discover software that is not detected by using file or package signatures.

  5. Creating signatures

    You can use the built-in functionality to extend your custom catalog with the software products that are installed in your infrastructure but are not present in the HCL® catalog.

  6. Testing extended signatures

    You can test signatures on endpoints and verify if they discover any software. There are two methods to test signatures.

 Go to Feedback
  • Software inventory and license utilization

    You can classify the discovered software so that reports in BigFix Inventory reflect your entitlements and properly show utilization of license metrics by particular products.

    • Collecting Oracle Measurements Data

      Starting from version 10.0.15, BigFix Inventory extends its capability to collect Oracle Java SE measurements data. Since version 10.0.16, BigFix Inventory also collects Oracle Database options and measurements data.

    • Vendor-specific predefined reports available in dashboard Inventory Reports

      Vendor-specific predefined reports available in dashboard Inventory Reports provide software discovery and licensing information for specific software vendors of BigFix Inventory customers. These reports help Software Asset Managers manage software for their vendors and prepare for contract negotiations and license audits. To view the reports, click on a vendor in the vendor-specific dashboard.

    • Reported license metrics

      BigFix Inventory reports utilization for a number of license metrics for IBM and non-IBM products. It also shows products that are assigned any BigFix metric even if calculating utilization is not yet supported for this metric. It gives you an overview of all IBM metrics for which you should have licenses.

    • Software classification

      After new components are discovered, they are assigned to products based on bundling rules. If the initial assignment does not reflect your entitlements, work with the software inventory until it matches the entitlements. To make metric calculation accurate, assign each component to a product, exclude, or suppress the instances that should not be included in the calculation, and confirm your actions. After you confirm the actions, the classification is complete, and the metric calculation is accurate.

    • Server Software Catalog

      To correctly identify components of software products in your infrastructure, ensure that your server software catalog is always up-to-date. Periodically import a new server software catalog that contains the most recent software products. Also, manually add products that are installed in your infrastructure but do not have corresponding entries in the catalog.

      • Updating server software catalog

        The server software catalog is automatically updated during every upgrade of BigFix Inventory. BigFix Inventory Server Software Catalog is refreshed more often than server and you can benefit from the newly connected by updating the server software catalog.

      • Checking product components and their signatures

        You can browse the software catalog to check what components belong to a particular product and what signatures cause that these components are detected.

      • Expanding the custom software catalog

        To ensure that all software items that are installed in your infrastructure are discovered, create custom signatures. You can create them from scratch or directly from the Package Data and Scanned File Data reports. You can also create extended signatures to discover software that is not detected by using file or package signatures.

        • Catalog customization process

          The process of adding custom signatures to the software catalog requires careful planning and consideration. It starts with identifying products that you expect to discover but are not reported or are missing from the software catalog. To correctly identify components of software products in your infrastructure, ensure that your software catalog is always up-to-date. ​Next, you should organize your work to ensure that the most important products are given the highest priority. Then, you determine what files or packages can be used to detect the software and report its usage. Finally, you can create the signatures.

        • Creating signatures

          You can use the built-in functionality to extend your custom catalog with the software products that are installed in your infrastructure but are not present in the HCL® catalog.

          • Extended signature templates

            Available from 9.2.2. Extended signatures are flexible signatures that are used for software recognition. They consist of a number of exported variables and the declaration of the operations that are required to assign a value to these variables. Update BigFix Server and Software Catalog to allow the Extended Signature capability to report the detailed versions of installed software.

          • Extended signature operators

            Available from 9.2.2. The scan operations during which extended XML signature definitions are used are performed based on the processing instructions that are contained in the signature catalog. In computer languages, expressions consist of two types of components: operands and operators. Operands are the objects that are manipulated and operators are the symbols that represent specific actions. Operands and operators can be either scalar or vector.

          • Testing extended signatures

            You can test signatures on endpoints and verify if they discover any software. There are two methods to test signatures.

            • Testing using BigFix Console

              The 'Test CIT Signature fixlet' allows you test custom signatures on selected endpoints, to discover if there is any match. For creating custom signatures refer to Inventory/softinv/r_extended_signatures.html.

            • Testing manually

              9.2.22 Available from 9.2.2. You can test the extended signatures that you create by using a BigFix client that is installed on the platform for which a signature is defined.

        • Creating signatures from package data

          You can use package data to expand your custom catalog. You can add signatures for software products that are installed in your infrastructure but are not present in the HCL® catalog.

        • Creating signatures from scanned file data

          You can use scanned file data to expand your custom catalog. You can add signatures for software products that are installed in your infrastructure but are not present in the HCL catalog. You identify the file name, or another item of information that can be used to identify the software and add the signature.

        • Adding a new product to software catalog

          The software catalog consists of a list of standard software products. Use the Add Product feature to define a custom product with the accompanying information, such as a publisher name, license metric and release.

        • Assigning an additional metric to a product

          Available from 9.2.8. The pricing calculations are based on the relation between a product and a metric. The software catalog consists of an inventory of standard relations. To define a custom relation, assign one of available metrics to an existing product.

        • 10.0.5 Managing license metrics through the UI

          BigFix Inventory allows you to add, modify, and delete metrics through the UI (user interface). You can also perform the same using the REST API, api/sam/v2/metrics as described under Inventory/integration/r_rest_api_for_managing_license_metrics.html.

        • Changing end of support date

          9.2.11 Available from 9.2.11. Set or change the end of support date for your software components to have a comprehensive overview of your software inventory.

        • Software discovery process after customizing the catalog

          Software matching your catalog customizations can be identified in one of the below ways depending on the custom signature.

      • Exporting and importing custom signatures

        You can export custom signatures to an XML file and import them to a different instance of BigFix Inventory to augment you software catalog. It is useful if you maintain separate instances of BigFix Inventory for test and production sites. In such case, you can reuse the custom catalog content instead of creating the new one. You can also import signatures that are published on the signature community or export your custom signatures and contribute them to the community.

    • Reports

      Reports provide detailed information about the computers in your infrastructure and the software items that are installed on these computers. By viewing the reports regularly, you can check whether actual installations reflect the software inventory information and ensure that the capacity values are assigned to products correctly. You can decide what type of information you want to display by choosing the appropriate type of report. You can also customize the type and amount of information that is displayed in a report and save the report settings to reuse them.

    • Enterprise applications inventory

      Software components are discovered during software scans. The scans correlate data that is collected from the computers with the content of the software catalog, and thus determine whether a component is installed. However, software scans do not discover details of some enterprise applications, for example licensable options of Oracle Database or editions of Microsoft Exchange. The details are discovered by dedicated fixlets. If you are interested in discovering additional details of enterprise applications, run the dedicated fixlets apart from scheduling software scans. Otherwise, running the fixlets is not required.

    • License metrics

      BigFix Inventory provides two types of information about license metrics utilization: aggregated utilization and raw utilization. The former shows utilization of the assigned license metric by all instances of a particular product within the reporting period. However, it is limited to a subset of license metrics. The latter shows data that is collected from .slmtag files. It shows raw utilization of all license metrics that can be used by a particular product. The data is not aggregated and requires further processing.

    • 10.0.5 Contracts management

      The contracts management group shows all contract-related reports in one place. This allows you to easily manage all your contracts.

    • 10.0.7 Software discovery in containers

      BigFix Inventory supports discovery of software in container images through standard discovery methods that includes catalog signatures, template signatures, installation registry and ISO SWID tags to cover traditional model of software deployment.

    • 10.0.8 Software data harvesting tool

Testing extended signatures

You can test signatures on endpoints and verify if they discover any software. There are two methods to test signatures.

Using a fixlet in BigFix Console

Testing manually on the endpoint

  • Testing using BigFix Console
    The 'Test CIT Signature fixlet' allows you test custom signatures on selected endpoints, to discover if there is any match. For creating custom signatures refer to Extended signature templates.
  • Testing manually
    9.2.22 Available from 9.2.2. You can test the extended signatures that you create by using a BigFix client that is installed on the platform for which a signature is defined.
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences