Manual - SourceForge



Volume

1

Fullerton College

Academic Computing Technologies

TimeKeeper System

Version 5.1

academic Computing technologies

TimeKeeper System Version 5.1

( Fullerton College

321 E. Chapman Ave

Phone 714.992.7274

Table of Contents

Installation 1

TIMEKEEPER NETWORK SERVER 1

SYSTEM REQUIREMENTS 1

Required Files, and Placement 1

Startup and Running 2

TimeKeeper Station 3

SYSTEM RECOMMENDATION 3

Windows NT Workstation 4.0 Installation 3

Windows NT SP 5.0 3

Local User Account 3

Application and Data directory Setup 3

Java 1.3 Run Time Installation 4

Auto Login and Startup 4

TimerKeeper Management Console 5

SYSTEM REQUIREMENTS 5

Required Files, and Placement 5

Startup and Running 5

Configuration 6

TIMEKEEPER NETWORK SERVER 6

STORAGEBINS.PRP 6

TimeKeeper Station 6

STORAGEBINS.PRP 6

TKStation.ini 6

TKLabManager.ini 6

TKBinDumper.ini 6

TimerKeeper Management Console 7

TKLABMANAGER.INI 7

TimeKeeper Data 8

EXPORTING DATA 8

TKBINDUMPER 8

TKLabManager 8

Troubleshooting 10

TKSTATION 10

TIMEKEEPER USAGE 11

SHUTTING DOWN TKSTATION 11

START TKSTATION 11

CONFIGURING IBS 500 12

PRE-CHECK LIST: 12

CONFIGURATION STEPS 12

CHAPTER

1

Installation

I

nstallation of each of the TimeKeeper components is relatively straight forward. The TimeKeeper system is designed to be installed and run on a Windows NT platform, but should function on any platform that has a Java 1.3 or higher Runtime available from Sun Microsystems.

TimeKeeper Network Server

The TimeKeeper Network Server consists of a single Java application that is run without any command line arguments via the “StartServer.bat” file. In fact the “TimeKeeper Server” is really simply a generic Fail Safe Bin Server [FSBS] that allows Java objects to be mapped to database tables.

System Requirements

• Java 1.3 or higher Run Time

• 25-50MB free disk space, depending on the number of TimeKeeper Sites, and how much back data you wish to keep in the system.

• 25MB free [physical] memory

• TCP-IP Port 4848 free

Required Files, and Placement

Standard installation consists of creating a RTTK directory on the machine to host the FSBS. Within this directory create two subdirectories: “Jars” – to contain the actual compiled code for the application, and “Runtime_Server” – to contain any Runtime INI files, or accessory files needed by the FSBS Server.

Place the following files in the “Jars” directory:

• edu.jar

• FSBS.jar

• iDB.jar

Place the following files in the “Runtime_Server” directory:

• StartServer.bat

• StorageBins.prp

Startup and Running

To start the Server, simply change your current working directory to the “RunTime_Server” directory, and execute the “StartServer.bat” file.

The FSBS will then create a Java RMI registry on port 4848, on the host machine.

Also a “StorageBins” subdirectory will be created in the RunTime_Server directory to store the database tables currently storing Java Objects.

DO NOT DELETE THE STORAGEBINS FOLDER

This will cause the permanent loss of all TimeKeeper data that has not yet been exported out of the TimeKeeper System.

TimeKeeper Station

The TimeKeeper Station is generally a Stand Alone machine dedicated to the TimeKeeper Station application. Outlined below will be the Full installation procedure for Windows NT Workstation, Service Packs, Local User Accounts, Auto-Login, Java Run Time, and the TimeKeeper Station Application.

System Recommendation

• 1GB Hard Drive

• 32MB Ram [Minimum] / 64MB [Recommended]

• Video Display capable of displaying 256 colors with a resolution of 800x600 or higher

• Keyboard or Serial Port bar code scanning device

• If this is to be a Networked TKStation, a Static IP address in the same IP Subnet of the FSBS is recommended.

• [Optional] Mouse, and Standard PC keyboard.

Windows NT Workstation 4.0 Installation

Typical Install

U: Administrator

P: pass2tkstation

TKStation_#Location#[#a,b,c…#] ie. TKStation_611a

Windows NT SP 5.0

No Backup

Local User Account

U:TKStation

P:tk4act

Never Expires

Cannot Change

Add to Admin Group

Application and Data directory Setup

C:\Data

Data$ = c:\Data

Java 1.3 Run Time Installation

Auto Login and Startup

HEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Windows NT\WinLogon\

• Stand Alone

o DefaultDomain: #MachineName#

• Network

o DefaultDomain: FC

• Both Modes

o DefaultUser: TKStation

o AutoAdminLogon: 1

o DefaultPassword: tk4act

TimerKeeper Management Console

Assuming you see your paragraph marks, you’ll notice a paragraph mark attached to the bottom right corner of the picture. Click on the picture, and notice too, the name of the Style—not surprisingly, the Picture Style. Pictures “attached” to paragraph Styles make it possible for pictures to “act” like paragraphs.

System Requirements

• Java 1.3 or higher Run Time

• 25-50MB free disk space, depending on the number of TimeKeeper Sites, and how much back data you wish to keep in the system.

• 25MB free [physical] memory

• TCP-IP Port 4848 free

Required Files, and Placement

Standard installation consists of creating a RTTK directory on the machine to host the

Startup and Running

To start the Server, simply change your current working directory to the “RunTime_Server” directory, and execute the “StartServer.bat” file.

Chapter

2

Configuration

T

he Configuration and Customization of the TimeKeeper System is accomplished through the modification or the Internal Datbase System’s property file “StorageBins.prp” and through a number of INI settings files.

TimeKeeper Network Server

No Configuration Options available.

StorageBins.prp

• Don’t Touch

TimeKeeper Station

The INI properties files need to be carefully examined prior to using the TimeKeeper Station in a production environment. All TKStation options are set via the TKStation.ini file. The TKLabManger.ini & TKBinDumper.ini files must also be modified to account for StandAlone or Network setup of the TimeKeeper Station.

StorageBins.prp

• Don’t Touch

TKStation.ini

TKLabManager.ini

TKBinDumper.ini

TimerKeeper Management Console

The TKLabManager.ini file must be customized to specify the location of the FSBS to be accessed, to defined which Site, or Sites are to be accessed by this TKLabManager.

TKLabManager.ini

Chapter

3

TimeKeeper Data

D

ata retrieval and processing of the TimeKeeper System Data is relatively straight forward, so long as you follow the steps outlined below.

Exporting Data

No Configuration Options available.

TKBinDumper

Don’t Touch

TKLabManager

To export data from a StandAlone TKStation, start the TKLabManager by typing “manager”

When Exporting data from the Network Server, start the TKLabManager form a DOS box by changing into the RunTim_TKManager directory and typing “StartManager.bat”

Once the TKLabManager is running, select the TKSite you wish to export data for, by selecting it from the Drop Download at the lower edge of the program window.

Then, from the Data Menu, select Data Dump

Select the Path and filename that the TKData will be dumped to.

Then you must specify a Begin, and End date.

The data will then be exported to the specified file.

You will then be prompted to select if you wish to remove the data from the TKServer. If you select ‘Yes’ a backup copy of the data will be placed in your current working directory, and all TKLog entries within the specified date range will be deleted. *Caution, at this point the removal process is VERY slow – and takes about 10-15 seconds PER record.

Weekly Reports

The INI properties files need to be carefully examined prior to using the TimeKeeper Station in a production environment. All TKStation options are set via the TKStation.ini file. The TKLabManger.ini & TKBinDumper.ini files must also be modified to account for StandAlone or Network setup of the TimeKeeper Station.

Chapter

4

Troubleshooting

T

he TimeKeeper Station systems are often tampered with by non-technical people, often resulting in problems that appear major to the client, but are actually fairly mild to “fix”.

TKStation

1. First attempt a “Restart” of the TKStation.

a. Type ‘zaq’ followed by

b. Once the program has shutdown, click on the “StartClient.bat” shortcut on the desktop.

c. Check to see if the program is now functioning correctly

2. If the TKStation is still not functioning correctly

a. Shutdown the TKStation with ‘zaq’

b. Make a copy of the RunTime_Client directory located in c:\data\rttk

c. Rename the copy to include a date stamp

d. Attempt to restart client, by clicking on the “StartClient.bat” shortcut

3. If the client starts up, all people who were in the lab, will need to report the time they entered the lab and the time that they leave in writing – this is best done by having the lab attendant track the time on a pad of paper. All new clock ins to the lab should function normally from this point forward.

Chapter

5

TimeKeeper Usage

Shutting Down TKStation

1. Make sure that the Cursor is in the console area of the TKStation or in the DOS box the java application is running in.

2. Type “zaq” then press

3. Wait for all TKStation windows to close, including the originating DOS box

4. Click on the Start Button

5. Select ‘Shutdown’

6. When prompted, select ‘Shutdown the Computer’

7. When the computer displays ‘It is now safe to turn off your computer’ – press the power button on the machine, thus shutting it down.

Start TKStation

1. If the machine is off, you should be able to just turn the Machine & Monitor on. The TKStation program should start automatically.

2. If the machine fails to login, you should login with ‘TKStation” as the username and “tk4act” as the password.

a. If it still does not let you login, then you can use “Administrator” & “pass4tkstation”

3. If the workstation is logged in, but the TKStation program has not automatically started, you can start it by clicking on the “Shortcut to StartClient.bat” icon on the desk top.

4. If the short-cut is not present, the program is located at c:\data\rttk\runtime_client\startclient.bat

Configuring IBS 500

The IBS 500 a barcode reader compatible with the Timekeeper System. This section describes how to configure the scanner for seamless integration into the TimeKeeper System.

Pre-check list:

• Valid, unused COM port

• Access to HyperTerminal (or compatible software) to test but do not connect whilst programming scanner

• IBS 500 Setup Menu paper to configure

Configuration Steps

To set to default settings:

Scan [start setup], [default setup], [end setup]

To add preamble digit:

Scan [start setup], [preamble], [a barpad digit], [set], [end setup]

To enable host response (allows the sending of beeps):

Scan [start setup], [protocol], [barpad 7], [end setup]

To turn off internal beep tone:

Scan [start setup], [beep tone], [barpad 0], [end setup]

To verify that the Scanner is correctly working, run HyperTerminal and open a new connection to the correct COM port. When the scanner is used, data should display on HyperTerminal.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download