Optimizing the volume of scanned file data
The Scanned File Data report provides information about files with particular extensions that were discovered on the computers in your infrastructure, and the files that are associated with the processes detected on these computers regardless of the extension. The information is typically used for creating custom discovery and use signatures. To optimize the volume of the monitored data, narrow down the list of file extensions that are collected to only those extensions that are typically used for creating signatures. It reduces the workload on the BigFix Inventory server and improves the application performance.
Before you begin
Important:
- Changing the list of discovered extensions does not change the scope of the discovered software.
- Scanning shared disks significantly affects the number of scanned files that are reported by BigFix Inventory.
- Changing the list of extensions of the files that are reported by BigFix Inventory might result in detailed versions not being reported.
- Starting from application update 9.2.8, the file system scan reports files that are based on processes that have been run on the computers in your infrastructure, regardless of their extension. Thus, you can narrow down the list of file extensions to only those extensions that are typically used for creating signatures unless you use the external tools that retrieve the scanned file data.
- If you use disconnected scans, and you change the list of discovered extensions, distribute the new catalog to disconnected computers. For more information, see: Preparing installation files for disconnected scans on Windows and UNIX or Preparing installation files for disconnected scans for IBM i.
Procedure
-
To stop the BigFix Inventory server, run
the following command.
-
/etc/init.d/BFIserver stop
-
installation_directory\cli\srvstop.bat
-
-
To optimize the volume of scanned file data, remove extensions that are not typically used for
creating signatures from file_names_all.txt,
file_names_unix.txt, and file_names_win.txt files.
The files are in one of the following directories:
- installation_directory/wlp/usr/servers/server1/apps/tema.war/WEB-INF/domains/sam/config
- installation_directory\wlp\usr\servers\server1\apps\tema.war\WEB-INF\domains\sam\config
Important: If you remove an extension which is a base for a signature that is currently used for software discovery, after the import of data the affected component is marked as uninstalled. The component will be reported back after you run the next software scan and import of data with a new software catalog. To check whether the extension is currently used to detect software, go to the Scanned File Data report and use the following filter:File Name; ends with; <.extension>
Recognized; equal to; Yes
- The following files are defined in the file_names_all.txt to be reported by
default:
\.ear$
- The following files are defined in the file_names_unix.txt to be reported
by default:
\.sh$ \.bin$ \.pl$ \.ear$ \.SH$ \.BIN$ \.PL$ \.EAR$
- The following files are defined in the file_names_win.txt to be reported by
default:
\.exe$ \.sys$ \.com$ \.ear$ \.ocx$
-
To start the BigFix Inventory server,
run the following command.
-
/etc/init.d/BFIserver start
installation_directory\cli\srvstart.bat
-
- If a new software catalog is available, upload it. Otherwise, re-upload the current software catalog.
-
Wait for the scheduled import or run it manually.
During this import, performance might be lower because the software catalog is re-imported.
- Wait for the scheduled software scan. Alternatively, if
you have infrequent software scans, stop the current scan and start
a new one. It will allow you for using the optimized list of file
extensions in a shorter time.
- Log in to the BigFix console and in the left navigation tree, click Actions.
- In the upper-right pane, click Initiate Software Scan and then click Stop.
- Initiate a new software scan.
- Wait for the scheduled import or run it manually. From now on, the optimized list of file extensions is used.