Preparation for Installing Tracker Version 6.7.0
Overview
Tracker requires that a supported web server, database drivers, and (optionally) SQL Server or Oracle software is installed prior to running the Tracker Setup (installation) program. Most or all of this software may already be installed. The sections below describe what is required, how to verify that the appropriate software is installed, and how to download and install the software, if necessary.
Web Server Software
Microsoft IIS 7.0, 7.5, 8.0 and 8.5
Microsoft Internet Information Server (IIS) is not installed by default on Windows Server 2008/2012.
The IIS version included in each Windows Server version is as follows:
Windows Server 2008, IIS 7.0
Windows Server 2008 R2, IIS 7.5
Windows Server 2012, IIS 8.0
Windows Server 2012 R2, IIS 8.5
If IIS has been installed, the following item should be in your Start menu.
Start > Programs > Administrative Tools > Internet Information Services (IIS) Manager.
In the Server Manager, select Roles. Scroll down to Role Services. Click Add Role Services. On the Select Role Services page, enable the following role services in addition to the defaults:
- All options except WebDAV Publishing under Common HTTP Features.
- All options except CGI and Server Side Includes under Application Development.
- Only HTTP Logging and Request Monitor under Health and Diagnostics.
- All options except Digest Authentication, Client Certificate Mapping Authentication and URL Authorization under Security.
- All options under Performance.
- All options under Management Tools, including all of IIS 6 Management Compatibility.
If IIS has not been installed, you can install it by running the Server Manager.
Start > Administrative Tools > Server Manager.
In the Server Manager, select Roles. Click Add Roles. If the "Before You Begin" page is displayed, click Next. Check the box for "Web Server (IIS)". A pop up will be displayed to mention any dependent roles. Click on the Add Required Role Services button. Click Next. Click Next again. On the Select Role Services page, enable the following role services in addition to the defaults:
- All options except WebDAV Publishing under Common HTTP Features.
- All options except CGI and Server Side Includes under Application Development.
- Only HTTP Logging and Request Monitor under Health and Diagnostics.
- All options except Digest Authentication, Client Certificate Mapping Authentication and URL Authorization under Security.
- All options under Performance.
- All options under Management Tools.
Microsoft IIS 6.0
Microsoft Internet Information Server (IIS) is not installed by default on Windows Server 2003.
IIS 6.0 is included with Windows Server 2003.
As Window Server 2003 will reach end-of-life in 2015, we recommend that you do not use it for a new NetResults Tracker installation (only use it for upgrading an existing installation). While you can continue to use Tracker 6.x versions with Windows Server 2003 until end-of-life next year, installation of the upcoming Tracker 7.0 release will require a newer operating system.
If IIS 6.0 has been installed, the following item should be in your Start menu. Start > Programs > Administrative Tools > Internet Information Services (IIS) Manager
If IIS 6.0 has not been installed, you can install it by running Add/Remove Programs from the Control Panel.
After starting Add/Remove programs, click on the Add/Remove Windows Components box, click on the box for "Application Server" and click Details. Check the box for Internet Information Services (IIS), then click Details. If you would like to install the minimum necessary components, select Common Files, Internet Information Services Manager, and World Wide Web Service. Click OK twice, click Next to install the selected components, then click Finish to complete the operation.
If you are using the 64-bit version of Windows Server 2003, IIS 6.0 has to be configured such that the application pools will be run as 32-bit worker processes. This setting applies to all application pools. In other words, if you need to run Tracker and another web application that requires a 64-bit ASP.NET worker process on the same server, you cannot use the 64-bit version of Windows Server 2003. Windows Server 2008 (with IIS 7.0) or Windows Server 2008 R2 (with IIS 7.5) are recommended instead as they do not have this limitation. To configure IIS 6.0 such that the application pools will be run as 32-bit worker processes:
Launch a command window. Change the directory to C:\Inetpub\AdminScripts. Run the following command "cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true". After the command has been run successfully, reboot the server.
Sun Java Runtime Environment (JRE) 5.0
Tracker uses Java to send and receive email messages (from the web server machine on which Tracker is installed). As such, it is required that the Sun Java Runtime Environment (JRE) version 5.0 is installed on the Tracker server. Sun Java Version 5.0 can be downloaded from the Tracker Support Downloads page. Sun JRE Version 6.0 does not currently work with the Sun JavaMail software that we use for sending and receiving emails, so it cannot be used. Another version of Java (e.g. Version 6.0) can be installed on the Tracker server as long as version 5.0 is also installed (before or after version 6.0 is installed).
Microsoft JScript 5.5 or Greater
Tracker requires JScript 5.5 or greater. It should already be installed on your web server as it is included with Internet Explorer version 5.5 or greater.
Database Driver Software on Web Server Machine
Tracker requires Microsoft Data Access Components (MDAC) 2.5 or greater and JET 4.0 Service Pack 5 (JET 4.0 SP5) or greater on the web server machine (this is true even if you are going to use SQL Server or Oracle for your workgroup database(s)). If you are using SQL Server or Oracle, you will also need to install additional (client) software (described in detail below) on the web server machine.
MDAC 2.5 or Greater
MDAC 2.5 or greater should already be installed on your web server (it is installed with the operating system). You can verify the MDAC version on your machine by running regedit (Start > Run..., enter regedit.exe) and check the "FullInstallVer" value under the key "HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess". It should be 2.50.x or greater.
JET 4.0 Service Pack 5 or Greater
JET 4.0 with Service Pack 5 (or greater) should already be installed on your web server (it is installed with the operating system). You can verify whether you have JET 4.0 SP5 (or greater), by finding the file msjetoledb40.dll (typically in C:\Windows\System32) in Windows Explorer, right-clicking on the file, selecting Properties, clicking on the Version tab and verifying that the File Version is 4.00.4331.4 or greater.
SQL Server (2005, 2008, 2012 and 2014)
If you are using SQL Server (2005, 2008, 2012 or 2014) as your database server for one or more Tracker workgroups and SQL Server is not already installed on the web server (Tracker will be connecting to a remote SQL Server system), you must have the SQL Server client connectivity software (e.g. SQL Server client drivers, SQL Server Client Network Utility, etc.) installed on the web server machine. Information about installing this software:
SQL Server 2014 (scroll to section "Using SQL Server with Client/Server Applications")
SQL Server 2012 (scroll to section "Using SQL Server with Client/Server Applications")
SQL Server 2008 (scroll to last sub-section of "Specialized Editions of SQL Server 2008")
SQL Server 2005 (scroll to bottom of "Deciding Among SQL Server 2005 Editions")
Please consult the SQL Server documentation or contact Microsoft Technical Support for further information on installing the SQL Server client software.
Note: If SQL Server is installed on a different machine than Tracker (it is not installed on the web server machine), you must ensure that (a) there is no firewall software or hardware that prohibits a TCP/IP connection from the web server to the database server and (b) the client software configuration (in the SQL Server Client Network Utility) for the TCP port matches that of the server (by default port 1433 is used; however, unless you have just installed the software, someone may have changed the default configuration at the server and/or the client).
Oracle Database 10g
If you are using Oracle 10g as your database server for Tracker, you must have the Oracle Database 10g Client software installed on the web server machine. The Oracle Client software must be version 10.1.0.2 or greater. It is required that you install the full Oracle client. The Instant Client that is available for Oracle 10g is not sufficient for use with Tracker. Browse to Oracle Metalink or contact Oracle Technical Support for further details on how to install Oracle Database 10g software.
Oracle Database 11g
If you are using Oracle 11g as your database server for Tracker, you must have the Oracle Database 11g Client software installed on the web server machine. It is required that you install the full Oracle client. The Instant Client that is available for Oracle 11g is not sufficient for use with Tracker. Browse to Oracle Metalink or contact Oracle Technical Support for further details on how to install Oracle Database 11g software.
Database Server Software
If you plan to use Microsoft Access as your database, there is no separate database server machine (the web server does all the database processing). For information on maintenance of your Access database(s), please review the Database Administration section of the Workgroup Management Guide.
SQL Server 2005, 2008, 2012 or 2014
If you plan to use Microsoft SQL Server as your database, you need to install SQL Server prior to installing Tracker. It should either be installed on the web server machine or on a machine that can be accessed over the network from the web server machine (via TCP/IP). It is generally easier to configure if it is installed on the web server machine (no possible firewall or network issues); however, a remote database may have better performance (because it won't use resources on your web server machine, although, that must be weighed against network delays in communicating with the database server machine). If you are using SQL Server 2005, you must apply Service Pack 1 (or greater) prior to installation of Tracker. SQL Server 2005 is not supported unless Service Pack 1 (or greater) has been applied. After you install SQL Server and prior to installing Tracker, you must configure it to use SQL Server Authentication. This type of authentication is used by Tracker when communicating with SQL Server. Instructions on how to do this are below.
For SQL Server 2005 - 2014:
- Start Microsoft SQL Server Management Studio.
- Right click on the server entry in the left pane and select "Properties...".
- Click on the "Security" entry in the top left pane ("Select a page" section).
- Select "SQL Server and Windows Authentication mode".
- Click on OK.
Oracle Database 10g or 11g
If you plan to use Oracle as your database, you need to install the database software prior to installing Tracker. It should either be installed on the web server machine or on a machine that can be accessed over the network from the web server machine (via TCP/IP). It is generally easier to configure if it is installed on the web server machine (no possible firewall or network issues); however, a remote database may have better performance (because it won't use resources on your web server machine, although, that must be weighed against network delays in communicating with the database server machine).
If you are using Oracle Database 10g, you must be using version 10.1.0.2 or greater.
SQL Server and Oracle Backup
After you have installed Tracker, please schedule regular SQL Server or Oracle backups of your Tracker database(s) and their associated transaction logs. Unlike a standard windows application (or Microsoft Access database file), SQL Server and Oracle database files are not standard files and can not be backed up by a simple file copy or simple file backup. If you do not schedule backups via SQL Server, Oracle or via backup software that connects with SQL Server / Oracle to perform a backup, you will not be able to restore your data in the event of a hard disk failure or other hardware/software failure. Please consult your SQL Server / Oracle manuals for directions on how to backup your database. Please review the Database Administration section of this Help document for details on the name(s) of the Tracker database(s). If you do not understand how to schedule database (and transaction log) backups, then we strongly recommend that you use Microsoft Access as your database (or switch to using the NetResults Tracker Online service where we manage the database and web servers for you). With Microsoft Access, simple file backup will work and, while a lot of factors can affect performance, if you are using a server with our recommended hardware configuration, an Access database should be able to handle five thousand problem records per Tracker workgroup (perhaps more if you have a newer server).
Anti-Virus Software
Temporarily disable any anti-virus software while you run the installation program and perform configuration steps in the Workgroup Management System (WMS). This is recommended so that your anti-virus software will not prevent the installation program or WMS from performing operations such as copying files, running scripts, configuring your web server, setting file permissions and registry entries. Your anti-virus software can be reactivated safely after you have completed the installation steps and any necessary WMS configuration.
End User Browsers
All an end user needs to access Tracker is a supported browser. This is true for all interfaces (workgroup, workgroup Admin section, Workgroup Management System, User Management System). If an unsupported browser (or unsupported version of a browser) is used to access Tracker, a warning will be displayed to let them know the browser they are using is not supported. Use of an unsupported browser is not recommended as it can result in data loss or corruption. For workgroup operations, you can click continue in the warning message to continue using the unsupported browser at your own risk, but an unsupported browser cannot be used at all for the Workgroup Management System or User Management System. Unsupported browsers include any browser or browser version not specifically listed in the System Requirements (pre-release, alpha or beta versions are also considered unsupported). The warning message will not be displayed when accessing the external Knowledge Base pages since these pages are only used to view content rather than submit or modify.