BrowserHawk provides the ability to detect details about the user's Java Virtual Machine configuration and operating system details and architecture, as well as other additional information detected by using Java. This information is provided through the JavaVendor, JavaVersion, MSJVMBuild, OSArch, the extended property version of OSName, OSVersion and OSDetails, and BrowserBitSize (under some conditions).
Note: If you will not be testing any of the above listed properties, then BrowserHawk does not use any applets in its testing, and this manual step should be skipped entirely.
To detect any of the above listed properties, BrowserHawk uses a tiny signed applet as part of its testing. If you are interested in detecting any of these properties, or may be interested in these tests in the future, you must manually copy the applet into the same web directory where the script that runs BrowserHawk will reside.
This applet used by BrowserHawk is named JVMDetector.jar and is installed by default to \Program Files\cyScape\BrowserHawk\JVM. After installing BrowserHawk you must copy this file into your web site directory where the BrowserHawk script that tests any of these properties will reside.
For example, let's say your web site root is located at \inetpub\wwwroot\mysite and you have a page called listing.aspx located in this directory in which you plan to check the JavaVendor and JavaVersion properties. You must copy the JVMDetector.jar file to this directory. See the JVMCodeBase (ActiveX / .NET) property for information on how you can place the applet into one common web site directory and share it across multiple pages on your site if those pages will reside in different subdirectories within your site.
If you are not interested in testing any of these properties that require the JVMDetector.jar applet, leave this option disabled. In this case the applet is not used and therefore the installation program will not prompt you for a location to save the file.
See Also: