Overview

JetPatch Software Discovery enables you to identify and track installed software and applications across all connected endpoints in your environment. 

By collecting real-time data on deployment status, operational state, and configuration details, JetPatch provides full visibility into your software landscape - covering both patch management and agent management environments.

Discovery is performed using a JSON-based configuration file that defines which tools and applications to search for, and how to identify them across Windows and Linux systems. 

Once discovered, the data is surfaced in the Agents Catalog and the Servers tab, allowing you to monitor unmanaged tools and take action accordingly.

This article contains the following topics:

1. Collect Software and Applications data on connected endpoints
2. Creating and uploading the discovery JSON
3. Managing Discovery Behavior

JetPatch enables the discovery of installed software and applications to identify deployment, operational status, and configuration details. This functionality is available in both patch and agent management environments.

Tools Discovery Overview

JetPatch Tools Discovery operates through two key methods:

• Collecting Data on Connected Endpoints
• Uploading a Discovery File to View Environment Status

1. Collect Software and Applications Data on Connected Endpoints

You can discover data on installed software and applications running in your environment. The data discovered is in JSON format and includes the agent Name, OS family, and agent version. To collect and download the data, please follow the next steps:

• SSH JetPatch Application Server

For versions before 5.0:

• Stop Tomcat

• Edit the intigua.properties file

Post 5.0:

• Stop intigua-main

• Edit the intigua.properties file

• Add the following settings:

• Save and Exit
• Restart Tomcat / intigua-main

For versions before 5.0:

After saving the changes to the file, restart Tomcat:

Post 5.0:

After saving the changes to the file, restart intigua-main:

After enabling the above, please wait at least 20 minutes, then:

1. Log in to the JetPatch platform
2. Go to Agents & Tools > Tools Catalog
3. Click on the Tools Discovery button > 'Download suggested discovery file'

2. Creating and Uploading the Discovery JSON

JetAgent can also discover agents based on agent configurations and parameters. 

To do so, a JSON file with specific properties is required. 

Follow the next steps to discover installed software using a discovery file:

The JSON file should include the following fields:

• "name" (mandatory) - The name of the software.
• "searchBy" (mandatory) - must include at least one "searchBy" parameter:
  • packageName (valid for Linux) - searching for DEB/RPM packages installed with the same name
  • upgradeCode (valid for Windows):
    • "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Installer\\UpgradeCodes"
  • productID (valid for Windows) - searching equivalent names in keys under:
    • "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Installer\\UserData\\S-1-5-18\\Products"
    • "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall"
    • "SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall"
  • services (valid for Windows and Linux) - list of services
  • registry (valid for Windows) - list of registry keys
• "configParams" (optional) - configure to extract the software configuration. This field should include:
  • "name" (mandatory if configParams exists) - The name of the requested configuration
  • "type" (mandatory if configParams exists) - The type of the parameter
  • "fromFile" (mandatory if "fromRegistry" is missing):
    • "filename" - the file name to extract the configuration
    • "linePrefix" - the prefix of the line to extract the configuration value from (all strings after the prefix will be extracted)
  • "fromRegistry" (mandatory if "fromFile" is missing):
    • "key"
    • "value"

1. Go to Agents & Tools > Tools Catalog
2. Click on the Tools Discovery button > 'Upload discovery file.'

3. Managing Discovery Behavior

Disabling Native Agent Discovery

To stop agent discovery while keeping the property enabled:

1. Create and upload an empty JSON file ({}) through Tools Discovery > Upload Discovery File
2. Disable ep.data.collection.enabled in intigua.properties and restart the service:

• For versions before 5.0: restart Tomcat
• Post 5.0: restart Docker

To Verify Current Configuration

Run the following SQL query to confirm the content of the uploaded discovery file:

Re-enabling Discovery

Upload a valid JSON file with desired configurations to reactivate native agent discovery.

Reviewing and Managing Discovered Data

After the JSON discovery file is uploaded, the data should appear in the system in several places (please wait at least ten minutes):

Agents Catalog

New Applications and Agents should appear in the Agents Catalog with an 'unmanaged icon'. 

You can drill down to see how many servers in your environment are running unmanaged tools.

Servers Tab

Data on specific servers appears in the Servers tab:

• Log in to the JetPatch server
• Go to Servers tab > Table Settings

• Select the 'unmanaged' columns
• You will now be able to see the servers that are running the software agents you selected
• Hover on the Tool icon to view the discovery date & time

• To collect more statistics, you can generate a CSV report 

Additional Configuration Properties

The following files are attached for reference:

• full_discovery.json - Complete discovery file example
• empty_obj.json - Empty JSON object for clearing discovery results