MondoSoft's BehaviorTracking

Setting Up Shop

I installed BT on a test server with dual 1,400-MHz Intel Pentium IIIs, with 1,024 MB of RAM, in our Syracuse University Real-World Labs. The product requires Windows 2000 or 2003 Server with at least a 1,000-MHz Intel Pentium Processor, 512 MB of RAM and 500 MB of disk space; Microsoft IIS (Internet Information Server) with .Net Framework 1.0 or 1.1 to drive the user interface; and Microsoft SQL Server 2000 (SP3a) to store search information. I installed Ultraseek 5.2.1 search engine and indexed our production Web site (www.nwc.com).

The BT installer identified my running copy of IIS and installed a virtual directory linking the Web server's root file system to BT's application folder. Once all the files were in place, I used the configuration wizards to finish the setup. I created a database for BT using Microsoft SQL 2000 Server, then identified the URL path to BT's log files, and defined an administrative user ID and password. I could create other users with individual settings from here as well. Unfortunately, the product does not integrate with LDAP or Active Directory.

The BT Connector installed on the same server as BT and Ultraseek. The installer placed the Connector and its support files in a subdirectory under the same file structure as BT, then mapped the subdirectory to a new virtual directory in IIS.

The Connector (BTCLog.dll) is an ISAPI program that works with IIS. It accepts log data from the Web server that runs the search-engine interface and writes the information in a format BT understands. By default, the Connector runs as the Internet Guest Account (IUSR_ ). If users authenticate to access the Web and the search engine, the Connector runs under their flag, so they'll need read and execute permissions to the Connector and full access to the directory where the logs are written.