How File based discovery can be used to populate software record running on Linux host.SummarySteps to be followed on how file based discovery to work successfully and create software record. Running discovery for the linux machine, we are seeing jboss details on the related items and under running processes but not under Installed softwares list of CI. Need to confirm from the customer if software ( JBOSS ) is showing when we run " rpm -qa " on the linux server. In Situations where rpm commands would not be possible to execute on customer setup as they will be using custom shell scripts and rpm would not work then File based discovery is the best option. Need to confirm the path from the linux team where they were able to find the Jboss software on the host. ( example: "sftw/jboss-as directory" )File based discovery will be running as a background process without a terminal hence if "requiretty" is configured in sudoers file then, sudo will only run when the user is logged in to a real tty which will not be successful in case of file based discovery since its running without a terminal.After confirming the above enable File based discovery plugin and configure the details from the configuration console Enable FBD feature from Discovery configuration console. Update the path of the software for FBD to scan and get the details ( example: "sftw/jboss-as directory" ) For few Customer where the software is only visible when sudo command is used we need to make below changes to the below script file to add sudo There's a table named "discovery_private_properties" that contains the script used for FBD. It's split into two parts: file_discovery.probe_prefix.unix and file_discovery.probe_suffix.unix. When the probe executes it concatenates prefix + config options + suffix to get the script to execute. We need to add sudo to this code: FINDCMD="find $paths $excludeSyntax -type f 2>/dev/null"if [ "$skipHiddenFolders" = true ]thenFINDCMD="find $paths -type d -name '.?*' -prune -o $excludeSyntax -type f -print 2>/dev/null"fi in the prefix, i.e. make it as below FINDCMD="sudo find $paths $excludeSyntax -type f 2>/dev/null"if [ "$skipHiddenFolders" = true ]thenFINDCMD="sudo find $paths -type d -name '.?*' -prune -o $excludeSyntax -type f -print 2>/dev/null"fi To know which file FBD need to searching for, we need to update the jboss jar file details on the " samp_custom_file_name" table. ( Example : "jbosssx-client.jar" )cmdb_unidentified_file_set table needs to be updated with the Product and Publisher name in order for the software records to be created.Need to make sure below with customer before running discovery after following above steps File based discovery plugin is enabled and also feature from Discovery configuration console has to be enabled. requiretty is disabled Discovery credentials can run the command "wc" with sudo privileges. Update the Publisher and Product values for the jboss-client.jar filename Running discovery after making sure all the above steps are followed we should see the jboss details under cmdb_file_information table, if the table is empty then file based discovery did not run correctly.Once we have followed all the above steps we should see the software record created under the installed software list with the details.ReleaseALL