System Architecture
From TrackerProducts Wiki
Contents |
System Architecture
The target audience of this document is users with a more advanced technical background who have chosen the purchased version of the Tracker system. A basic understanding of some technical aspects of the system will allow you to maximize performance through use. This document is not intended to serve as an install guide for the system. Install information is available within another support document.
Tracker is a 100% web based client / server application.
Database Environment
- Tracker software is designed for use with the MS SQL Server platform. Future releases will include support for Oracle and MySQL server
- Supported with MS SQL 2000 and 2005 Server
- The initial install of the database will be roughly 10mb
- In most cases, we will provide a properly formatted backup of a database that you will restore to your server
- There are several hundred tables that are used by many views and stored procs
- Web site will communicate with the dbase via a ODBC formatted ASP file
- Web site will need a SQL user that has at lead read and write permissions to the dbase. This user information will be based in a scripted ASP file that communicates with the dbase. We recommend that you give this new user Owner privileges to the Tracker database
- We highly recommend a daily backup of the database. The site is not set to perform any type of automated backup routine
- The only part of the database that is encrypted are the user passwords,which use MD5 for hashing
- Please contact Tracker support if you plan to work directly with the database in either reading or writing mode
System Files
- The current version of Tracker software uses an assortment of ASP, VBscript, Java and .Net files.
- The file structure on a new install is roughly 5mb. However, all picture files are stored in the file structure and this can put a heavy payload on the file structure size.
Browsers
- The current version of Tracker software supports Internet Explorer 5.5 / Firefix / Safari
IIS
- ET was designed for use with the Microsoft IIS platform that is v5.0 or better
- You will need to enable ASP file permissions on IIS 6.0 or better
- You will need to setup a new web entry for user interaction. This site can use any support IP address, port number or host header name
FTP Server
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.
Desktop Software
- Traker desktop software will receive and restore XML files with the main system. The receive XML file will contain system settings that define the environment for the software. The restore XML file with contain file information that is being put in the dbase. More info on Desktop Application
PDA Software
- Tracker PDA (handheld) software will receive and restore XML files with the main system. The receive XML file will contain system settings that define the environment for the software. The restore XML file will contain item transaction information that is being put in the database.
Hosted Application
Most of this document has covered details related to the purchased (installed) version of Tracker. If you are using the hosted version of Tracker software, all previous information applies except that we are hosting the database and all files at our NOC in Texas.
- All hosted sites use SSL 128 bit encryption
- All hosted sites have their own site link. Example: http://mypd.trackerproducts.com
- When you type in the link listed above your are redirected to more secure link like https://mypdsecure.trackerproducts.com
- When you are redirected to a more secure site you are also redirected to a non-standard Internet port like port 44433.
- Your final destination will look like https://mypdsecure.trackerproducts.com:44433
- All customer databases are backed up daily and stored on a local backup drive and an off-site backup system located 20 miles from the original backup.
