Skip to main content
Version: 10.2

Shared Software Assets Directory (SSAD)

The Open iT Shared Software Assets Directory (SSAD) is a cloud-hosted centralized repository that maintains a normalized catalog of software information. It automatically matches and standardizes software data collected from customer environments, enabling consistent reporting and analytics across multiple Open iT solutions.

SSAD is a key component in Open iT’s integration with ServiceNow, as it ensures accurate reporting in the ServiceNow for Engineering Dashboard by distributing a standardized software catalog for data normalization.

How SSAD Works

SSAD is hosted in the Open iT Customer Portal and operates as a cloud service integrated with the customer’s Open iT environment. The Core Server communicates with SSAD through the SSAD connector application, which manages data exchange securely and efficiently.

  1. Establishing Secure Cloud Communication

    The Core Server authenticates with SSAD using its credentials and obtains an access token to establish a secure connection.

  2. Collecting Data from the Core Server

    The Core Server collects software data from LicPoll, application, and inventory sources. This data is packaged into the following standard data types, which are used to query SSAD:


    note

    These data types are generated every five (5) hours when the scheduled job to process all data runs. You can manually trigger the Process All Data job on the Core Server's Job Runner interface.

  3. Querying the SSAD

    The Core Server sends the generated queries to SSAD, which matches the customer's data against its normalized catalog. Once the matching process is complete, SSAD returns the latest mapping files and catalog for use in data normalization.

  4. Downloading and Using the Mapping Files

    The following files are downloaded from SSAD and stored in the Core Server’s configuration directory:

    • featureset.map. These files are saved in the Catalog folder of the Core Server's configuration directory following the format, $CONFIG_DIR/Catalog/<License Manager>/<Vendor Daemon>/featureset.map.

      note

      If no vendor daemon exists, the license manager name will also be used as the daemon name in the directory format.

    • feature-to-software-catalog-id.map. This defines one-to-one feature mappings.

    • application-to-software-catalog-id.map. This defines mappings for Windows applications.

    • SSAD.json. The Analysis Server uses this file to match Open iT software names with ServiceNow catalog definitions (when integrated).

    • unmatched.json. This records unmatched customer data to the SSAD catalog.

    The mapping files allow the Core Server to translate software data into standardized, normalized data that is consistently reported and integrated across Open iT solutions.

  5. Generating Normalized Data

    Core Server uses the mapping files from SSAD to produce the following normalized data types:

    These data types are reported under the LicenseAnalyzer – Level 1 (Runtime Usage) module and are automatically loaded into the Open iT Analysis Server.

Why SSAD is a Strategic Asset

The Open iT Shared Software Assets Directory (SSAD) is a core enabler of accuracy, scalability, and efficiency across Open iT solutions. Its value extends beyond current integrations:

Always Up-to-Date Normalization

SSAD delivers the latest mappings and software definitions without requiring manual updates, ensuring reports remain accurate over time.

Accurate Reporting Across Platforms

The same standardized catalog ensures consistency in reports generated by the Core Server, Analysis Server, and integrated platforms like ServiceNow.

Vendor-Agnostic and Scalable

SSAD works across various license managers and applications, accommodating growth and changes without rework or additional configuration.

By centralizing normalization in the cloud, SSAD strengthens data quality, reduces complexity, and provides a scalable foundation for both existing and upcoming Open iT capabilities.