Software Product Specific Discovery

The following list specifies which software products should be discovered and reported by SysInfo™ in addition to all products registered with the native OS software registry.

Table 4.1. Software Product Specific Supported Products

Product VendorProduct NameMust Be Running?Requires Root?Discovery Process
ApacheHTTP Web ServerNoNo
  1. Look for httpd program as: /usr/apache/bin/httpd, /sbin/httpd, /usr/sbin/httpd, /usr/local/sbin/httpd, /usr/local/bin/httpd, /bin/httpd, /usr/bin/httpd
  2. Run httpd -v and parse output.
BEA SoftwareWebLogic ServerYesNo
  1. Look for a running weblogic process to determine directory where product is installed.
  2. If no running weblogic process was found, search directories: /opt, /var/local, /usr/local, /root.
  3. If the weblogic directory was found in the previous steps, then look for the weblogic XML registry file and parse it.
IBMWebSphere Application ServerYesNo
  1. Look for a running WebSphere process to determine directory where product is installed.
  2. If no running WebSphere process was found, search directories: /opt, /var/local, /usr/local, /root.
  3. If the product directory was found in the previous steps, then look for the product XML registry file and parse it.
OracleApplication ServerNoNo
  1. Look for the /etc/oraInst.loc file to determine the inventory directory.
  2. If no inventory directory was previosuly discovered, look at running processes to find the product directory.
  3. If the inventory directory was found in the previous steps, parse each CompID.properties file found for each package.
OracleDatabaseNoYes
  1. Look for a system user named oracle.
  2. Invoke a shell as user oracle and search the user's environment variables for Oracle variables indicating directory where product is installed.
  3. If the previous step failed, search the oracle user's $PATH for the sqlplus command.
  4. If the previous step failed, search the oracle user's home directory for the sqlplus command.
  5. If sqlplus was found run it with the -? argument and parse the output.
SybaseAdaptive Server EnterpriseYesNo
  1. Look for a running ASE process to determine directory where product is installed.
  2. If no running ASE process was found, search directories: /opt, /var/local, /usr/local, /root.
  3. If the product directory was found in the previous steps, then look for the product XML or VPD registry file and parse it.
TibcoEnterprise Message ServiceNoNo
  1. Look for tibemsd in directories: /opt, /var/local, /usr/local, /root, /usr/tibco
  2. If tibemsd was found run tibemsd --version and parse the output.

Any application which has "Yes" indicated or "Must Be Running?" will likely be undetected if the application is not running when SysInfo is run. For these applications, SysInfo looks at the system process table using the ps(1) command. If the process is not running, in some cases SysInfo will attempt to discover the application by searching standard directory locations such as /opt and /usr/local.

Any application which has "Yes" indicated for "Requires Root?" will not be detected if SysInfo is not run as root (either by being installed by root or being run as root). However, if "No" is indicated the application may still not be detected in some cases where file access permissions of the user running SysInfo are insufficient to open the applications files. Running SysInfo without root privileges is not supported, nor recommended.