Details:
BrowserHawk consists of two main parts - the BrowserHawk Editor and the BrowserHawk component itself.

The BrowserHawk Editor is required to download browser definition files (either manually or automatically), view/edit browser definitions, and to set various preferences and options. Installation of the BrowserHawk Editor on each machine you run the BH component on is highly recommended for a number of reasons.

If you wish to minimize what you install on your production servers, however, it is possible to install just the BrowserHawk component without the BrowserHawk Editor. When you run the BrowserHawk installation program you can choose not to install the BrowserHawk Editor.

See the Installation Guide in the BrowserHawk documentation for a full discussion on whether installation of the BH Editor is right for you.

In some special cases developers may want to install BrowserHawk manually - by registering the ActiveX DLL themselves, or manually copying the .NET DLL to their bin directory etc, instead of running the installation program. Some of these cases include:

• wanting total control of which files are copied/modified on their system
• automating the BH install into a custom deployment script for organizations that license several copies of BrowserHawk
• having the ability to use components on their ISP's server but not the ability to run an installation program (only can copy files and register DLLs).

Important note: It is not possible to install the BH Editor manually - only the component. If you want the BH Editor you must run the installation program.

The BH Editor is required in order to receive automatic updates to the BDF files. If you cannot install the BH Editor on the same machine where you will run the BH component from, see this article on how to update your BDF remotely.

Instructions for installing the BrowserHawk component manually differ depending on whether you are installing the ActiveX/COM, native .NET, or Java version of BrowserHawk.

Manual installation of BrowserHawk for ActiveX/COM

1. create a new subdirectory (name of your choice) in a directory on your web server configured to run ASP scripts.
2. find the following files from a local installation of BrowserHawk:
   • cyscapesvr.dll
   • bhawk_sp.dat
   • bhawk_bb.dat
   • maindefs.bdd
   • jvmdetector.class

3. copy the above files to the subdirectory you create in step 1
4. If you plan to use the JavaVendor, JavaVersion, MSJVMBuild, OSName, OSVersion, or OSArch properties, copy the JVMDetector.class file from your local installation to the web directory on your remote server where your script using BrowserHawk will be located (i.e. \inetpub\wwwroot\mysite on the remote server)

5. unless you purchased a license for the local server you installed BrowserHawk on to get the above files, remove the local copy installed
6. register the cycapesvr.dll using regsvr32 or suitable alternative that may be provided by your hosting provider
7. rename your purchased license key to BrowserHawk.lic and place it in the same directory with all the other files. Then create or try a test page which uses the BrowserHawk component to verify a successful installation. If the page complains about inadequate permissions when trying to use the object, consulting the BrowserHawk documentation under the Required Permissions topic.

Licensing: Please remember that BrowserHawk is licensed on a per server basis. If you plan to install BrowserHawk on any new servers using the techniques described in this document you will need additional licenses for those servers.

Manual installation of BrowserHawk for .NET

1. Install a copy of BrowserHawk on your local system using the automated installer.
2. Copy the following files from your local installation of BrowserHawk to the \bin directory on your remote server:
   • BrowserHawk.dll
   • your license key** (format is "your name.lic" or bh_evalkey.lic for evals)
   • browserhawk.properties
   • maindefs.bdd
   • bhawk_sp.dat
   • bhawk_bb.dat

3. If you plan to use the JavaVendor, JavaVersion, MSJVMBuild, OSName, OSVersion, or OSArch properties, copy the JVMDetector.class file from your local installation to the web directory on your remote server where your script using BrowserHawk will be located (i.e. \inetpub\wwwroot\mysite on the remote server)

4. On the remote server, edit the browserhawk.properties file to change the value of the "license.file" entry to match the name of your license key file. For example: "license.file=Bob_Smith.lic". If you are using an evaluation license key named bh_evalkey.lic you can skip this step, since the file defaults to this file name for evaluations.
5. Optional: To verify a successful installation, copy one of the ASP.NET samples from your local installation to a web directory/application associated with the bin directory you copied the above files to on the remote server and run the sample.

** Attention ISPs / Hosting companies: In accordance with the license agreement you may not place a copy of your license file in a directory that is readable/accessible by your customers, such as their bin directory, unless the customer owns the license and provided it to you. See the note in the browserhawk.properties file near the license.key attribute for detailed instructions on how to install the key in an alternate location (a location other than their bin dir) that is not accessible to your customers.

Licensing: Please remember that BrowserHawk is licensed on a per server basis. If you plan to install BrowserHawk on any new servers using the techniques described in this document you will need additional licenses for those servers.

Manual installation of BrowserHawk for Java (BrowserHawk4J)