Software Product Specific Discovery

Software Product Specific Discovery
Prev	Chapter 4. Software Discovery Support	Next

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 Vendor	Product Name	Must Be Running?	Requires Root?	Interface	Discovery Process
Apache	HTTP Web Server	No	No	SPS	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 Run httpd -v and parse output.
Apache	Tomcat	No	No	SDL	Look for dtomcat and tomcat program in: /usr/local/bin /var/local/bin /usr/bin /bin /usr/sbin /sbin Run dtomcat version and parse output.
BEA Software	WebLogic Server	Yes	No	SPS	Look for a running weblogic process to determine directory where product is installed. If no running weblogic process was found, search directories: /opt /var/local /usr/local /root If the weblogic directory was found in the previous steps, then look for the weblogic XML registry file and parse it.
CA	BrightStor (ARCserver) Server	No	No	SDL	Look for installed directory as: /opt/CA /usr/local/CA /var/local/CA Look for a file under the install directory called `RELNAME` and parse output.
HP	OpenView Data Protector	No	No	SDL	Look for installed directory as: /opt/omni Look for a program under the install directory called omnimver, execute program, and parse output.
IBM	DB2	No	No	SDL	Look for program db2ls in directories: /usr/local/bin /usr/local /opt Execute program and parse output.
IBM	Informix C-ISAM	No	No	SDL	Look for program bcheck in directories: /usr/bin /bin /usr/local/bin Parse strings from binary program.
IBM	Informix Enterprise Gateway Manager	No	No	SDL	Look for file `EGM-cr` under user "informix" home directory. If that fails, look for file in directories: /opt/IBM /opt/ibm /opt/informix /opt /usr/opt /usr/local Parse file `EGM-cr`.
IBM	Informix I-SPY	No	No	SDL	Look for file `opt.conf` under user "informix" home directory. If that fails, look for file in directories: /opt/IBM /opt/ibm /opt/informix /opt /usr/opt /usr/local Parse file `opt.conf`.
IBM	Informix MaxConnect	No	No	SDL	Look for file `IMC-cr` under user "informix" home directory. If that fails, look for file in directories: /opt/IBM /opt/ibm /opt/informix /opt /usr/opt /usr/local Parse file `IMC-cr`.
IBM	Informix Extended Parallel Server	No	No	SDL	Look for file `XPS-cr` under user "informix" home directory. If that fails, look for file in directories: /opt/IBM /opt/ibm /opt/informix /opt /usr/opt /usr/local Parse file `XPS-cr`.
IBM	Tivoli Application Dependency Discovery Manager	No	No	SDL	Look for file `/etc/init.d/collation`. Parse file if found.
IBM	Tivoli Composite App Manager for WebSphere Data Collector	No	No	SDL	Look for file `version.properties` in directories: /opt/IBM /opt/tivoli /usr/local/IBM /usr/local/tivoli /var/local/IBM /var/local/tivoli Parse file if found.
IBM	Tivoli Configuration Discovery and Tracking	No	No	SDL	Look for file `/etc/init.d/collation`. Parse file if found.
IBM	Tivoli Configuration Manager	Yes	No	SDL	Look for running process that matches pattern */oserv.-k**. Determine product install directory from process path. Look for file `Contents.xml` in the install directory and parse if found.
IBM	Tivoli Enterprise Console	No	No	SDL	Look for program tec_console in directories: /opt /usr/local /var/local /apps If program is found, look for file `console.version` in the same directory as program. Parse file if found.
IBM	Tivoli Netcool	No	No	SDL	Look for file `RELEASE_ID` in directories: /opt /usr/local /var/local /apps Parse file if found.
IBM	Tivoli Provisioning Manager for OS Deployments	No	No	SDL	Look for file `rembo` in directories: /etc/init.d /sbin/init.d /etc/rc2.d /etc/rc3.d /etc/rc5.d Parse strings from binary if found.
IBM	WebSphere Application Server	Yes	No	SPS	Look for a running WebSphere process to determine directory where product is installed. If no running WebSphere process was found, search directories: /opt /var/local /usr/local /root If the product directory was found in the previous steps, then look for the product XML registry file and parse it.
Oracle	Application Server	No	No	SPS	Look for the /etc/oraInst.loc file to determine the inventory directory. If no inventory directory was previosuly discovered, look at running processes to find the product directory. If the inventory directory was found in the previous steps, parse each `CompID.properties` file found for each package.
Oracle	Database	No	Yes	SPS	Look for a system user named oracle. Invoke a shell as user oracle and search the user's environment variables for Oracle variables indicating directory where product is installed. If the previous step failed, search the oracle user's $PATH for the sqlplus command. If the previous step failed, search the oracle user's home directory for the sqlplus command. If sqlplus was found run it with the -? argument and parse the output.
Sybase	Adaptive Server Enterprise	Yes	No	SPS	Look for a running ASE process to determine directory where product is installed. If no running ASE process was found, search directories: /opt /var/local /usr/local /root If the product directory was found in the previous steps, then look for the product XML or VPD registry file and parse it.
Sun	Java Runtime Environment	No	No	SDL	Look for program java in directories: /usr/java /usr/jre /usr/bin Run java -version and parse output.
Tibco	Enterprise Message Service	No	No	SPS	Look for `tibemsd` in directories: /opt, /var/local, /usr/local, /root, /usr/tibco 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.