This page (revision-22) was last changed on 26-Nov-2021 10:22 by lurtan

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
22 26-Nov-2021 10:22 14 KB lurtan to previous
21 26-Nov-2021 10:22 14 KB rforbes to previous | to last

Page References

Incoming links Outgoing links
GENUS CLOCK APPLICATIONS
GENUS CLOCK APPLICATIONS

Version management

Difference between version and

At line 5 changed 46 lines
This paper is to explain all aspects of the High Line Genus Clock Application for both developers and consultants.
!!Developer Information
!Source Code
*The source code for both G1 and G2 applications is kept in a package as part of the standard product code\\com.highlinecorp.timeclock
*Copies of the source each release are kept on\\pandora\dfs\ePersonality\Time_Clock_Software\From PD
*For each release zip files are kept:
*#a built G1 app, G2 app and zipped with the configuration files (These are the zip files which may be released to clients)
*#The current build scripts used to generate the apps
*#A copy of the Genus clock app source which keeps track of the eP version in the zip file names.
!Batch Files
*Deploying Genus class libraries ( from CMI ), deploying genus system file ( from CMI ), Compiling HL code, building jar files, deploying the App.jar and configuration file, retrieving - Existing App.jar, config files and genus classes and libraries are all accomplished through DOS batch files.
*They are all located in:\\C:\HLApplication\HLApplication\dd\timeclock\bat
*They are organized to work with G1 and G2 types separately. Each clock type requires different class libraries and different java files to build different App.jar files although they are named the same.
*The App.jar created for each clock type G1 or G2 will support Biometric, Mifare and proximity readers.
!Compiling
*For ease of development the clock applications may be developed from within JDeveloper. Although development is done here, it is important that compilation of the code be compiled on a java version no newer than 1.05.0.11 and compiler set to 1.4. The code must be written and compiled to be compatible with the J2ME Personal Profile 1.1
*The application must be compile outside JDeveloper before a built and may be done using the cmd file located in:\\C:\HLApplication\HLApplication\dd\timeclock\bat
*The batch files with naming of either G1 .... or G2 ..... have been developed. The purposes of each are:
*#Deploy clock library and system files (provided from CMI)
*#Compile application code outside JDeveloper required before a build.
*#Build the jar file.
*#Deploy configuration and application to a clock.
*#Are "gets" for getting the above files off an existing clock.
*These files are configured via the ~setvars.cmd file.
!Configuration
*The configuration file is located in:\\c:\HLApplication\HLApplication\dd\timeclock\config
*The file name is app.conf
*This file is used for both the G1 and G2 clock types of all readers. It contains all supported clock feature attributes and some attributes in the database configuration that have been planned for but not developed or supported.
*Each attribute has an example with explanation line and the actual attribute and value. The example line is remarked by placing a # at the beginning of the line, so it will not be loaded into the clock.\\Example:\\#TITLE = High Line Time Clock - main screen title\\TITLE = HL (Devel) Time Clock
*Extra unused lines may also be remarked for reference and not used.\\Example:\\#HOST_URL = http://<host>:<port>/<webapp>/<process> - server connection string\\#HOST_URL = http://localhost:8988/selfService/clock.process - example\\#HOST_URL = http://192.168.97.165:8988/selfService/clock.process\\#HOST_URL = http://192.168.97.47/selfService/clock.process\\HOST_URL = http://192.168.97.165:8988/selfService/clock.process
*This config file needs to be loaded before the application in order for it to be read by the application at start up. (see the "G2 4 Deploy file" described above. )
!Java Libraries and System Files
*The supporting java libraries are provided to High Line from Control Module Incorporated. The current supported versions as of May 13, 2010 for the G2 are:\\Java class files : 1.0.91\\Clock system files: 4.03.04
!Available Memory
*G1 available memory:\\32 MB dynamic memory, 2MB of non-volatile memory for data retention, 32MB of flash memory for program storage.
*G2 available memory:\\32MB dynamic memory, 2 MB of non-volatile memory for data retention, 40 MB of flash memory for program storage.
%%information These values have been provided by the CMI G1 and G2 users manual.%%
!!Consultant Information
!Clock Types and Applications
!!Clock Types and Applications
At line 61 changed one line
!Configuration Attributes
!!Configuration Attributes
At line 66 changed one line
__Application Configuration__
!Application Configuration
At line 85 changed one line
__Terminal Configuration__
!Terminal Configuration
At line 96 changed one line
__Web Configuration__
!Web Configuration
At line 104 changed one line
__Database Configuration - NOT USED__
!Database Configuration - NOT USED!
At line 120 changed one line
!Loading Clock Software
!!Loading Clock Software
At line 139 changed one line
!Clock Rebooting
!!Clock Rebooting
At line 143 changed one line
!Usability Configuration
!!Usability Configuration
At line 151 changed one line
!Functionality
!!Functionality
At line 213 removed one line
This page (revision-22) was last changed on 26-Nov-2021 10:22 by lurtanTop