SRVInstallSQL2005Win2003
From TrackerProducts Wiki
Tracker Products Install Guide for MS Windows Server and SQL Platform
This document will cover setting up both the SQL server and IIS server. It is NOT a requirement that both SQL and IIS be on the same machine. However, some of the instructions below may vary slightly based on the setup.
MS SQL Requirements
- SQL 2005 or 2008 Standard or Enterprise Server (If you are buying just get standard. We list enterprise in case you already have it.)
- Note: Do not use Express or Workgroup unless you are aware of the limitations and accept these limitations. The SQL software does NOT need to be on the same box as the IIS. The Tracker software does allow you to connect to a SQL box on a different machine.
This site from Microsoft explains licensing models http://www.microsoft.com/Sqlserver/2005/en/us/pricing-licensing-faq.aspx#pricing.
Minimum Server Requirements (Primary / Single Server)
- Windows 2003 or 2008 Server
- IIS 6.0 or better
- IE 6 / Firefox 3 or better
- It is recommended that you have at least 2 gig of ram on the server
- It is recommended that you have at least 100 gig of hard drive space available for the Tracker system. (The initial file and database structure are very small. File attachments are the primary use of hard drive space)
- Note: Virtual machines with minimum server requirements will work.
Minimum Server Requirements (Report / Secondary Server)
Some clients with a large amount of data in the primary database might need a secondary / report server. Tracker IT will be able to better determine the need for a report server. If it is determined that you need a report server you will need a server with specs pretty much in line with the primary server. The report server will use SQL data mirroring services to keep an exact copy of the primary database on the report server.
- If using the report server you will need the Enterprise version of SQL on this box. The primary server can still use SQL Standard. The Enterprise version is the only version that allows data mirroring and snapshots.
Desktop Requirements (Web Client)
Tracker requirements for desktop machines are very minimal. A machine that runs IE6 / Firefox / Safari will work. With that being said we recommend a machine with XP or better and 1 gig of ram.
ASPpdf Installation
All purchased clients need to have ASPpdf installed on the server. This software allows users to perform server side PDF document creation. Please contact Tracker support if you did not get a license for the ASPpdf product.
- Download the ASPpdf file: 32bit 64bit
- Run the executible on the server
- Apply the license code as part of your install
SQL Database Install
- Download your prepared copy of the SQL dbase. This will be done via a FTP process on the ftp.evidencetracker.com site. A username and password will be provided separately.
- Unzip the SQL dbase that you just downloaded into a directory of your choosing.
- Open SQL Management Studio
- Perform a dbase restore using the unzipped SQL file
- Dbase Name: You can name the dbase anything you like
- File Path: You can restore the files to any directory you like
- Create a new user account in the security area with permissions to the dbase that you just restored. This user should have Owner privileges to that dbase. The username and password will be up to you.
- Make sure you setup a backup job to backup the dbase.
- This completes all the necessary work for setting up the database.
Setup Job to build necessary cache file
- From within SQL Management Studio expand the SQL Server Agent
- Expand the Jobs option
- Right click on Jobs and select New Job.
- Name the Job anything you like
- Click Steps on the left panel
- Click New
- Step Name can be anything
- Database drop down should run against the Tracker dbase.
- In the command box type 'EXEC Custom_Field_Values_Cache'
- Click OK at bottom
- Click Schedules in the left panel
- Create a New schedule and setup to run every hour.
You are done with the dbase section.
IIS Setup Windows 2003
- Download and unzip your copy of the web files. This will be done via a FTP process on the ftp.evidencetracker.com site. A username and password will be provided separately.
- You need to make sure that your 2003 IIS install will allow you to run ASP files. To verify, open IIS, go to the Web Service Extensions on the left and make sure that Active Server Pages are allowed. By default these are disabled.
- Unzip all of the web files to a directory of your choosing. We recommend using something like C:\Tracker or D:\Tracker if you have a D: for data.
- Inside the directory of files you just unzipped is a directory called Connections. Open the connections folder. You need to modify the file called connEvidence.asp (This file can be modified with notepad). You need to change the name of the dbase, the location of the dbase and the username / password of the user you created with Owner privileges on the SQL server.
- If the SQL server and IIS server are on the same machine, you can leave the name as ‘localhost’
- If the SQL server is on a separate machine you need to use the IP # of the SQL machine
- Navigate back to the root of the folder directory. There is a folder called ‘userfiles’.
- Right click on top of the userfiles folder
- Select properties
- Select the security tab
- Click the add button
- Add the IUSR_??? account and give this account full permissions to that directory and all directories under it.
- Open IIS Server
- Create a new web site entry (this will initiate the IIS wizard)
- Click the next button
- In the description box type the name of the site. IE ‘EvidenceTracker.com’
- IP Address and Port Settings: (You may need to talk with your network admin to get settings that will work in this area). The site needs to either have an assigned IP address or use a host header name.
- Web Site Home Directory: Navigate to the directory where you unzipped the web files.
- Web Site Access Permissions: Make sure to select both Read and Run Scripts
- Click Finish
- After you click finish you will now have a new IIS entry in the menu
- Right click on that new entry and select properties
- Go to the home directory tab
- Click the configuration button
- Go to the Options Tab
- Change session timeout to 35
- Put a check box in ‘Enable parent paths’
- Change ASP script timeout to 120
- TEST: To test the configuration open your IE browser. Type the name of the host header name or the IP address of the site. If all is setup correctly, you should get the login screen to the program
- Login to site as the admin account.
- Change the URL to http://yoursite/connections (Note: my use of http in this example could actually be https if you are using a SSL. Also, my use of name yoursite would not be correct for your setup.)
- Click the update variables option
- Change 'File Path', 'Signature File Path', 'Archive File Path' & 'Userfiles_Path' to the correct file path for your server.
IIS Setup Windows 2008
By default classic ASP is not installed on Windows 2008. Follow these steps to enable.
- Click Start, point to Administrative Tools, and then click Server Manager.
- In the Server Manager hierarchy pane, expand Roles, and then click Web Server (IIS). [If Web IIS does not exist you will need to right click on Roles and add a role. Install Web Server]
- In the Web Server (IIS) pane, scroll to the Role Services section, and then click Add Role Services.
- On the Select Role Services page of the Add Role Services Wizard, select ASP.
- If the Add role services required by ASP dialog box appears, click Add Required Role Services. (This page appears only if you have not already installed the ISAPI Extensions role service on your server.)
- On the Select Role Services page, click Next.
- On the Confirm Installation Selections page, click Install.
- On the Results page, click Close.
Now you can move forward with the setup of the IIS.
- Unzip all of the web files to a directory of your choosing. We recommend using something like C:\Tracker or D:\Tracker if you have a D: for data.
- Inside the directory of files you just unzipped is a directory called Connections. Open the connections folder. You need to modify the file called connEvidence.asp (This file can be modified with notepad). You need to change the name of the dbase, the location of the dbase and the username / password of the user you created with Owner privileges on the SQL server.
- If the SQL server and IIS server are on the same machine, you can leave the name as ‘localhost’
- If the SQL server is on a separate machine you need to use the IP # of the SQL machine
- Navigate back to the root of the folder directory. There is a folder called ‘userfiles’.
- Right click on top of the userfiles folder
- Select properties
- Select the security tab
- Click the add button
- Add the IUSR_??? account and give this account full permissions to that directory and all directories under it.
- Open IIS Server
- Create a new web site entry (this will initiate the IIS wizard)
- Site Name: Tracker
- Physical Path: (Browse to the root of the Tracker folder you unzipped earlier)
- Type: http unless you need https and can setup a certificate.
- Click OK
- Click on the Tracker site that was just created in the previous step.
- In the center pane double click 'ASP' under the IIS section.
- Enable Parent Paths: True
- Expand the 'debugging properties' in this same area. set 'Send Errors to Browser': True
- Click OK
- Close IIS, you should be done.
Mail Server Relaying (For EAlerts)
The Tracker system does require a mail server that will allow relaying for the use of EAlerts. After logging in as admin click the System Setup icon. On this screen you will enter mail server that will allow relaying and a from address to show in the email.
Note: The Tracker system does not do email authentication at this point. Therefore the mail server will need to allow relaying from the Tracker server. If relaying is not allowed then the mail will fail
To test a mail server to see if relaying is allowed try this (this is for higher level tech users)
telnet mail server name 25
HELO Your Name or Computer Name
MAIL FROM: from email address (Use TrackerAlerts@yourdomain.com)
RCPT TO: to email address (Use email address of someone likely to get the Alert)
DATA then Enter
(Type something like this)
This is a test e-mail.
(Remember to type it all right. Backspace key doesn't work in Windows Telnet, though it does in Linux. If you make a mistake, try pressing CTRL-h. If it works, well and good.)
When your data line is complete hit the enter key and type in one more period and hit enter. This final period will complete the data section.
QUIT to leave
Setup for Pics and Docs upload
By default a windows server will only allow upload files of a certain size. By default this amount is like 20kb. Please complete these steps to change this to a greater size.
- Enable editing of the metabase.xml by following the instructions here: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/cdec2ac1-ae21-4a37-a818-13116224dcd0.mspx?mfr=true
- Open the metabase.xml file with notepad, located in c:\windows\system32\inetsrv\
- Search the text document for "AspMaxRequestEntityAllowed" (no quotes). Adjust the value of this property to the maximum file size you would like to allow uploaded (in bytes).
- Save the file and restart IIS.
Topaz USB Signature Pad
If you are using a Topaz signature pad at the desktop level you will need to download this file and install on the server. http://www.topazsystems.com/Software/sigplusse.exe
System Backup
There are two items that need to be backed up routinely.
- All web files especially the userfiles folder
- The database: We recommend setting up a backup routine within SQL server that will at least nightly create a .bak file of the dbase.
FTP Server Setup
Release v2 of the PDA software has done away with the requirement of a FTP Server for uploading of XML files. All XML file processing now takes place via a standard HTTP or HTTPS connection on the PDA. Make sure you have the most current release of the PDA software for this new functionality PDASoftware-CurrentRelease.msi.
