Training Manual for the

GridLock Access Management

(GLAM) System

Document : Training Manual

File Name : glam_tm.doc
Version : 1.00
Date : 07 May 2009

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 2 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Table of Contents
1 Introduction.........................................................................................................................5
2 Refrenced documents.......................................................................................................... 5
3 GLAM System overview, termS and definitions....................................................................6
4 WEBGLAM FRONTEND and Googleearth overview...............................................................8
4.1 WebGLAM.......................................................................................................................8
4.2 Googleearth.................................................................................................................... 9
5 Managing Keys and Keyholders...........................................................................................9
5.1 Adding Keys.................................................................................................................... 9
5.2 Adding Keyholders........................................................................................................12
5.3 Assigning Keys to Keyholders.......................................................................................14
6 Lock Management.............................................................................................................. 16
6.1 Lock Discovery............................................................................................................. 16
6.2 Lock Maintenance.........................................................................................................29
7 Overview of events............................................................................................................ 29
8 System administration.......................................................................................................31
8.1 User and Group management......................................................................................31
8.1.1 Overview.................................................................................................................31
8.1.2 Group Permissions..................................................................................................32
8.1.3 User management..................................................................................................32
8.1.3.1 Creating new user......................................................................................34
8.1.3.2 Updating user details.................................................................................36
8.1.3.3 Assigning user to a group..........................................................................37
8.1.3.4 Register user for notification.....................................................................39
8.2 Reporting......................................................................................................................40
8.2.1 Lock status reporting .............................................................................................40
8.2.2 Key status reports...................................................................................................41
8.2.3 Key activity report..................................................................................................41
8.2.4 System user lock changes......................................................................................44
8.2.5 System user key changes.......................................................................................45
8.2.6 System user schedule changes...............................................................................47
8.3 System administration................................................................................................. 48
8.3.1 General system administration...............................................................................48
8.3.2 Linux system administration...................................................................................50
8.3.2.1 Services.....................................................................................................50
8.3.2.2 Logs...........................................................................................................51
8.3.2.3 Configuration.............................................................................................51
9 glossary............................................................................................................................. 52
10 Revision Information........................................................................................................52

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 3 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Table of Figures
Figure 1: GLAM System Components............................................................................................6
Figure 2 GLAM Login Page............................................................................................................8
Figure 3: GLAM Front Page...........................................................................................................9
Figure 4: New Key Discovered Event...........................................................................................10
Figure 5: Key edit page................................................................................................................11
Figure 6: Key GE Overlay.............................................................................................................12
Figure 7: Keyholder List View.......................................................................................................13
Figure 8: Keyholder edit page......................................................................................................14
Figure 9: Key / Keyholder assignment.........................................................................................15
Figure 10: Keyholder GE Label....................................................................................................16
Figure 11: Lock discovery event...................................................................................................17
Figure 12: Discovered Lock Icon Figure 13: Discovery event icon............................................18
Figure 12: Discovered Lock Icon Figure 13: Discovery event icon............................................18
Figure 14: Lock search page........................................................................................................19
Figure 15: Lock Edit General........................................................................................................20
Figure 16: Lock Edit location........................................................................................................21
Figure 17: Lock Edit Additional Comments..................................................................................22
Figure 18: Update Uncommissioned lock in GE..........................................................................23
Figure 19: Schedule Page............................................................................................................24
Figure 20: Schedule create date..................................................................................................25
Figure 21: Schedule select key....................................................................................................26
Figure 22: Schedule Lock assign.................................................................................................27
Figure 23: Key list.........................................................................................................................28
Figure 24: Key with pending update and transaction schedule...................................................28
Figure 25: System user view........................................................................................................33
Figure 26: Personal details...........................................................................................................34
Figure 27: New user form.............................................................................................................35
Figure 28: New user details..........................................................................................................36
Figure 29: Update user password................................................................................................37
Figure 30: Groups available.........................................................................................................38
Figure 31: Assign user to new group............................................................................................38
Figure 32: Register for event notification......................................................................................39
Figure 33: View all system locks..................................................................................................40
Figure 34: Report on key status...................................................................................................41
Figure 35: Key activity view..........................................................................................................42
Figure 36: Lock changes view......................................................................................................44
Figure 37: Key activity window.....................................................................................................46
Figure 38: Transaction history......................................................................................................47
Figure 39: System status view......................................................................................................49
Figure 40: Confirm stopping service.............................................................................................49

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 4 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 5 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

1 INTRODUCTION
This document serves as a training aid for the GLAM System. It is not to be used as a reference
document as to the functionality of the GLAM system but merely as a guideline to aid with the operation
thereof. Please refer to Ref[1], User Manual for the GridLock Access Management (GLAM) System, for a
complete reference of the GLAM system functionality.

2 REFRENCED DOCUMENTS
Ref. Number Document Name Document Number
Ref[1] User Manual for the GridLock Access Management (GLAM) UM01
System
Ref[2] User Manual for the GridLock Key UM02

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 6 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

3 GLAM SYSTEM OVERVIEW, TERMS AND DEFINITIONS

Figure 1: GLAM System Components

The term Lock refers to the physical GridLock Lock that is installed in GridLock access points. No locks
exist in the system when they are installed; they are only discovered in the network when they are first
accessed with a GridLock Key. When in this state, the locks are referred to as Uncommissioned locks
and is accessible and discoverable by all Keys. In order to secure the Lock a fuse is blown in the Lock
through the Key when it is command so by the GLAM Server. This fuse prevents random acces to the
lock and the lock is now only accessible through the use of its internal password. Locks with their fuses
blown are referred to as Commisioned locks.

All Locks have a public identification number that is provided by an RFID tag moulded in the access
point latch. This number is unique and is used by the GLAM system to identify a specific lock. The Lock
also has a secret number that is programmed into the lock. This secret number is used as part of the
password to access the lock in future. The secret number and the public RFID number as well as the
location of the lock is extracted from the lock and the latch and is then sent to the GLAM Server in order
to add the lock to the GLAM system.

The term Keyholder refers to a specific party that is responsible for a specific Key at a point in time. Keys
are assigned to a Keyholder, and all actions performed with the Key are logged against the Keyholder’s
name while the Key is assigned to the Keyholder. This provides traceability and accountability with
regards to the actions of a Keyholder whilst responsible for a Key. The binding is not permanent and a
Key can be assigned to any other Keyholder at any point in time.

The term Key refers to the GridLock Key. The Key is used to access and operate GridLock Locks. Every
GridLock Key is equipped with a GPS receiver in order to continuously track the global position of the
This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 7 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Key. All Keys are also equipped with a GSM-GPRS modem that is used to communicate with the GLAM
Server. In order for the Key to communicate with a Lock, the Key must be preloaded with the password
for the specific Lock. The Key also store all a log of all the actions that has been performed by it. The
Key is not permanently connected to the GLAM Server. The Key connects to the server only when an
event happens, i.e. Power On or Lock access, and the GSM network is available. When a connection to
the server is made, a list of passwords for the Locks that this Key is granted access for, are downloaded
to the Key for storage whilst, at the same time, the event log stored on the Key is uploaded to the GLAM
Server.

The list of passwords is referred to as a Key authorisation schedule and is built specifically for each Key.
Each entry in the Authorisation schedule is referred to as an authorisation transaction and contains the
public RFID number for a Lock as well as the password for the Lock. Each authorisation also has an
expiry time at which time the transaction is no longer valid and cannot be used to access a lock
anymore.

The events uploaded to the GLAM Server from the Key are all time stamped and contains a position
marker if possible in order to determine the time and location at which the event occurred. These events
are used by the GLAM server to keep the Lock and Key data up to date in the GLAM System.

The GLAM System Users are the operators that make use of the GLAM system to manage and monitor
the GridLock Access system. This is achieved through the use of a web interface, WebGLAM and
Googleearth overlays for visual representation of the GLAM data.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 8 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

4 WEBGLAM FRONTEND AND GOOGLEEARTH OVERVIEW

4.1 WebGLAM

The GLAM web frontend, WebGLAM, can be found by pointing a web browser to the glam server at the
following address: http://<glam-server-address>/glam/ where <glam-server-address> should be replaced
with the actual address of the GLAM server.

All users first have to log in at the GLAM login screen.

Figure 2 GLAM Login Page

A newly installed GLAM server is shipped with two default Users i.e an administator user with the user
name “admin” and password “admin” belonging to the admin user group with unrestricted access rights
and another user with the username “user” and password “user” belonging to a general user group with
access rights restricted to the Managing and Monitoring of Locks Keys and Keyholders.

It is advised that the default user either be changed or replaced with other user with similar rights as to
protect the security of the system.

All users are directed to the GLAM front page, also referred to as the Logs tab, after logon.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 9 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 3: GLAM Front Page

The tab bar at the top of the page is used to navigate to the different functional areas of the application.

4.2 Googleearth

In order to utilise the GLAM Googleearth overlays, Googleearth needs to be downloaded and installed
from the Google website at http://earth.google.com . Once installed the GLAM overlays are accessible
any page of the WebGLAM application. Simply click on the Googleearth icon to and instruct the
browser to open the file in Googleearth. This will cause a whole tree of overlays to be added to the
Googleearth view under temporary places. All the overlays are not enabled by default but all can be
either enabled or disabled in order to be set up to the user’s requirements.

5 MANAGING KEYS AND KEYHOLDERS

5.1 Adding Keys

Keys can be added to the system in one of two ways, firstly through the WebGLAM frontend, or with the
use of a GridLock Keypod and the GridLock GPOD application. This doucument will only discuss the
web interface method.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 10 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 4: New Key Discovered Event

A “New key discovered” event is logged when a new key communicates with the GLAM server for the
first time. This new key can then be added to the system by clicking on the event. This will cause the Key
edit page to be displayed with the Key serial number pre-entered into the mandatory field.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 11 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 5: Key edit page

It is also good practice to enter the box number, the number affixed to the outside of the key enclosure,
as this is the only way to recognise a specific key.

The SIM details are also useful for future maintenance is available. The key is added to the system by
clicking the Save button and will now be visible in the list of keys displayed in the Keys page and will also
be visible in Google earth by enabling the GLAM Key Transactions overlay.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 12 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 6: Key GE Overlay

The label shown with the key icon will either be the key serial number or the box number, if available.

5.2 Adding Keyholders

A Keyholder can be created by clicking the Add Keyholder button from the Keyholder list view.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 13 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 7: Keyholder List View

This navigates to the Keyholder Edit Page. Here the details of a Keyholder can be entered and be added
to the system with the Save Button.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 14 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 8: Keyholder edit page

After hitting the save button, this Keyholder will be visible from the Keyholder list view page.

Key and Keyholder details can always be edited from their respective edit pages by dopuble clicking the
selected Key or Keyholder in the list view. System users with advanced access rights will also be able to
delete Keys and Keyholders from the system from the list view.

5.3 Assigning Keys to Keyholders

A Key can now be assigned to a Keyholder from either the Keyholder page or the Key page. If assigning
a Key to a Keyholder from the Key page, the Key is selected by highlighting it in the list and clicking the
Assign Keyholder button. If assigning from the Keyholder page, the appropriate Keyholder is selected
and the Assign Key button is clicked.

This will navigate to the Key/Keyholder assignment page. Here the pre-selected Key or Keyholder will be
highlighted in the lefthand pane and a list of Key or Keyholder assignment options will be displayed in
right hand pane.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 15 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 9: Key / Keyholder assignment

The assignment is completed by selecting the correct value from the list on the right and clicking the
Save Assigment button. The Keyholder’s name is used to identify a Key in the system once a Key is
paired with a Keyholder. The Key / Keyholder pairing can be changed at any point in time through the
assignment page.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 16 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 10: Keyholder GE Label

Every time a Key now logs onto the system it updates its own last known position which will cause the
Key icon to track the last known position of the Key.

6 LOCK MANAGEMENT
6.1 Lock Discovery

All locks are added into the system through the lock discovery process. When a newly installed lock is
accessed by a Key, the Key automatically retrieves all the Lock’s credentials as well as its physical
location. A “New Uncomissioned Lock Discovered” event is then logged on the GLAM system by the
Key.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 17 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 11: Lock discovery event

As soon as the event is logged the lock is created in the Discovered state on the GLAM system. The
newly discovered lock will now be visible and searchable from the Locks page.

The Google Earth overlay is also updated to show the lock as well as indicate the discovery event for the
lock.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 18 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 12: Discovered Lock Icon Figure 13: Discovery event icon
The discovered Lock needs to be validated before it is completely added to the GLAM system. The
Validation process is used to ensure that the Lock is part and has been discovered in the correct
location. The process is also used to enter relevant detail for the Lock.

The Lock is validated from the Lock edit page, which is either reach by clicking on the Discovery event in
the Logs view or by searching for the Lock and double clicking on it from the Lock search page, which is
found from the Locks tab.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 19 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 14: Lock search page.

All the necessary lock details can now be edited and added from the Lock edit page.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 20 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 15: Lock Edit General

The physical location of the Lock needs to be verified using Google Earth. The Location of the Lock may
be adjusted in the Geospatial tab by editing the coordinates of the Lock. This will in turn cause the
Google Earth icon to be moved in the overlay.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 21 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 16: Lock Edit location

An additional free form text comment field can be found at the Additional tab. This field can contain any
additional information regarding the Lock.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 22 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 17: Lock Edit Additional Comments

The Lock is now validated and saved by clicking the Validate an Save button, which causes the Lock
status to be updated from Discovered to Uncommisioned. The newly added lock description is also now
used as the label for the lock in the GLAM system as well as the Google Earth overlays. The Discovery
event icon is also removed from the Google Earth view once the Lock has been validated.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 23 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 18: Update Uncommissioned lock in GE

GLAM can merely monitor access to a Lock whilst a lock is in the Uncommisioned state, it cannot
perform any form of access control. Thus all Keys in the GLAM system will have access to the Lock at all
times. GLAM can only perform access control on Locks that have been commissioned.

A Key needs to be instructed to commission a specific Lock by scheduling a Commission transaction for
the Key. Schedules are created from the Schedule page which can be found by clicking the Schedule
tab.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 24 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 19: Schedule Page

The schedule page lists all the transaction schedules for the day as selected on the calendar on right.
The Create Transaction button is clicked in order to create a new transaction schedule.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 25 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 20: Schedule create date

The start and end date of the transaction schedule is entered first. This will determine the time window
during which this schedule is active. A description for the schedule can also be added in order to identify
the schedule in the schedule list. The information is saved by clicking the Save button.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 26 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 21: Schedule select key

Next the Key for which this Schedule is intended should be selected from the list of Keys. The Key is
selected by highlighting it in the list. The locks to which this schedule applies to should be selected next
by clicking the Assisgn Locks button.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 27 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 22: Schedule Lock assign

Locks are selected from the list of available locks on the left by checking the box and clicking the Add
Selected button. All locks are added to the schedule with the Access operation as default. The operation
needs to be changed to “Access/Commission” in order for the Lock to be commissioned. The schedule is
saved by clicking the Finish button.

The schedule has now been created on the GLAM system but will only be downloaded to the actual Key
when the Key next communicates with the GLAM server. Thus the Key is deemed to have a pending
update. Keys with a pending update are shown as such in the Key page with their status indicated as
pending.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 28 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 23: Key list

In the Google Earth view the transaction schedule is indicated with lines drawn from the relevant Keys to
all the Lock that it has transactions for. Keys that have Pending transaction updates are indicated with a
red Key icon instead of the usual blue for updated Keys.

Figure 24: Key with pending update and transaction schedule

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 29 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

The commissioning of the lock is confirmed by the Key when it logs a “Successful Commissioning of
Lock” event. The status of the Lock will also be updated to Commisioned. From this point onwards the
Lock is only accessible by scheduling an Access transaction for it. This is done in the same manner as
the scheduling of the Access/Commision schedule discussed previously.

6.2 Lock Maintenance

From time to it may be necessary to replace a lock, latch or both. In the case where both parts are being
replaced the Lock will be discovered by the Key in the same manner as previously discussed. The
validation process should be started as previously, but instead of clicking the “validate and save” button,
the “Replace Complete Lock” button should be clicked.

This will bring up the Lock search page. The correct lock to be replaced should be selected and the
Replace button be clicked. This will cause the discovered lock to completely replace the old Lock. All
data and events previously associated with the replaced Lock will now be associated with the new Lock,
thus keeping continuity in the system with regards to event history and configuration data.

The Key will recognise a replacement Lock in the case where only a Lock is replaced (the Latch is left
intact) and log a possible Lock replacement event. The action is completed by clicking on the event. This
will navigate to the Lock edit page. Here the Replace Lock button is clicked to complete the Lock
replacement. It is important to note that the new Lock will be in the Uncommisioned state again and must
be commissioned again using the method discussed previously.

The replacement of a Latch is a bit more involved. A Latch replacement transaction needs to be
scheduled for the Lock needing the Latch replacement. Once updated, the Key will then automatically
detect and verify the new latch and Log a possible Latch replacement event. The transaction is
completed by clicking on the event in the event log and clicking the Replace Latch button on the Lock
edit Page.

7 OVERVIEW OF EVENTS
The events that get logged by the key and the system are described in the following table.

Event Description Event Meaning

UnComissioned Lock Discovered This event signifies the discovery of an Un-Commissioned newly
installed lock. The lock will be be added to the GLAM system as
a discovered lock if it does not exist in the system yet
Successful Authorised Opening Indicates the successful Authorised opening of a lock. This is
either a scheduled access for Commissioned locks or an un-
scheduled opening for Discovered and Un-Commissioned locks.
Successful Authorised Locking Indicates the successful Authorised locking of a lock. This is
either a scheduled access for Commissioned locks or an un-
scheduled opening for Discovered and Un-Commissioned locks.
Successful Late Authorised Locking Indicates the successful locking of an lock after the authorised
access time has expired. The access time for a lock is extended
after the expiry time, in order to allow for the closing of open
locks by the key that was authorised to open the lock. The expiry

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 30 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Event Description Event Meaning

time is not extended for the opening of locks
Failed Authorised Opening - Lock in Indicates a failed authorised attempted opening of a lock with the
Locked State lock left in the locked state. Normally indicates some kind of
mechanical problem with the lock mechanism, blockage etc.
Failed Authorised Locking - Lock in Indicates a failed authorised attempted locking of a lock with the
Opened State lock left in the locked state. Normally indicates some kind of
mechanical problem with the lock mechanism, blockage etc.
Failed Authorised Opening - Lock in Indicates a failed authorised attempted opening of a lock with the
Unknown State lock left in an unknown state, i.e. could not be confirmed as
either locked or open by the key. Normally indicates some kind of
mechanical problem with the lock mechanism, blockage etc.
Failed Authorised Locking - Lock in Indicates a failed authorised attempted locking of a lock with the
Unknown State lock left in an unknown state, i.e. could not be confirmed as
either locked or open by the key. Normally indicates some kind of
mechanical problem with the lock mechanism, blockage etc.
UnAuthorised Attempted Opening Indicates the attempted opening of a commissioned lock without
the necessary authorisation transaction. The lock is left in the
locked state.
UnAuthorised Attempted Locking Indicates the attempted locking of a commissioned lock without
the necessary authorisation transaction. The lock is left in the
opened state.
Successful Commissioning of Lock Indicates the successful commissioning of an Un-Commissioned
lock. The status of the lock on the GLAM system is updated from
Un-Commissioned to Commissioned upon the reception of this
event.
Failed Commissioning of Lock Indicates the failed commissioning of a lock. The lock is left as
Un-Commissioned on the GLAM system.
No RF Tag Found During Opening Indicates that the key could not communicate with the RF tag on
the latch before opening the lock. This normally indicates a
misaligned latch with the locking mechanism possibly in an
unlocked state
No RF Tag Found During Locking Indicates that the key could not communicate with the RF tag on
the latch before locking the lock. This normally indicates a
misaligned latch, or an attempt at closing the lock without the
latch being in place.
Recheck of RF Tag before Closing When locking a lock the key rechecks the RF tag of the latch
Failed during the locking command sequence as to ensure that the
latch was not moved after the initial check for the latch at the
start of the sequence. This event indicates that the later check of
the RF tag on the latch has failed and normally indicates to the
latch being moved after the initial check for the RF tag.
Duress Alarm - Keyholder Panic The duress alarm is activated by pressing all three of the buttons
on the key for a certain amount of time. This mechanism is used
by the Keyholder to indicate some abnormal condition either
onsite or en route such as accessing locks under duress or other
emergency situations.
Tamper Alarm - Key enclosure has Indicates that the key enclosure has been opened and should be

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 31 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Event Description Event Meaning

been opened checked for possible tampering.
Unsafe Lock in expired schedule Indicates that a lock has been left in the opened or unknown
state after the authorised access transaction has expired
Unsafe Lock now scheduled Indicate that a lock that was previously left in the opened or
unknown state after an expired access transaction, has now
been added to a new current access transaction.
Possible latch replacement Glam detected an inconsistency with the lock’s latch and logged
the event so that the latch can be replaced by the system user.
This event will only be logged on Un-commissioned locks and
commissioned locks that have been scheduled for latch
replacement.
Possible lock replacement A lock has been replaced but the old tag still remains. This is
event is logged when an existing lock is replaced by an Un-
commissioned locks with the old latch.
Latch replaced successfully The latch for a lock has been replaced and updated throughout
the system
Lock replaced successfully The lock has been replaced with the old latch and the details
have been updated throughout the system.
Lock comms error The key is unable to communicate with the lock after it has polled
it successfully. The lock is placed in an unknown state.
New key discovered A new key has been found on the system. Navigating from this
event will allow the new key to be added.

Key login The key has powered up and connected to the server.

Key Init comms failure The key cannot start to communicate with the lock.

Table 1: Glam event description

8 SYSTEM ADMINISTRATION
8.1 User and Group management

8.1.1 Overview

System users are the heart of the network; they manage the locks in the field. It is such that they will be
the ones granting access to locks and doing general GLAM management.

Users are allowed certain actions based on the group that they are assigned to. GLAM only has a set
number of groups. This allows for easier management of users and their assignment to groups. When
the user logs into the system they will only see what they are allowed to see based on the group they are
assigned to, similar they will only be able to perform actions as allowed by the group. The following
section gives an overview of groups.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 32 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

8.1.2 Group Permissions

The groups are listed along with their allowed permission. When a group can ‘manage’ a part of GLAM it
is meant that they can add, update and delete certain details. The following table list a description of
allowed actions for each of the four groups.

Group Permissions

Users registered under the administrator group are allowed to perform any action on
Admin the system. This is the only group where users are allowed to delete locks, manage
system users and halt/restart system processes.

Similar rights as the admin group but users assigned to this group are not allowed to
General-Admin delete locks, manage system user or system processes. Members of this group can
manage keys and keyholders.

Users assigned to this group perform daily activities such as creating schedules and
Operator assigning keys to keyholders for scheduling This is the last group that can update lock
details and validate newly discovered locks.

Users assigned to this group can only create schedules. They are allowed to assign
Scheduler
keys to keyholders for this purpose.

Table 2: GLAM Groups

8.1.3 User management

By default GLAM has two system users registered in the system.

 Admin: this user belongs to the admin group and can administrate every aspect of the
system. The username and password are the same by default.

 User: This user belongs to the scheduler group and can only schedule access to locks.
The username and password are the same by default.

The default view when accessing the system user option in the menu is as depicted in Figure 11.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 33 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 25: System user view

On the left hand we have a table that list all the registered users in GLAM. As can be seen we
have the default admin and user, along with an additional user.

The right hand side shows the currently logged user details. The only group that can manage
system users is Admin, the rest will have the menu option but this is only to view their details
and to update their password. Figure 12 shows a user from a group other than admin.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 34 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 26: Personal details

8.1.3.1 Creating new user

More system user can easily be added to GLAM. It is important to note that when a user is added they
will NOT be assigned to a group. The user will thus not be able to log on until he/she has been assigned
to a group.

To add a new system user click on the “Add SystemUser” button. This will navigate the browser to a
page as show in Figure 13.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 35 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 27: New user form

All the fields denoted by a star are required. The username is the name that the user will use to
log into the system. The password is their keep safe and can be changed as will be explained in
Section 8.1.3.2. The rest is personal details for the system user. When the data is entered it can
be saved to the system by clicking “Save”. The browser will navigate to the details for the newly
added user as shown in Figure 14.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 36 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 28: New user details

Note that the User group at this state is none. The user needs to be assigned to a group to be
able to log into the system. This will be explained in Section 8.1.3.3. The user can also be
registered for notifications; this is explained in Section 9.

8.1.3.2 Updating user details

The user details can be updated and changed from their details window, from here they can also be
assigned to a group and be registered for event notification. To navigate to a user’s details double click
his/her name from the list of system users. This will show a window as can be seen in Figure 14.

The user details can be saved and stored back into the system after clicking the “Save” button. To
update the user’s password check the “Change Password” box. This will show two additional fields
requesting the new desired password and a re-entry of the same password to confirm unity.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 37 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 29: Update user password

When all the details have been entered to change click the submit button. The user will be
indicated when the passwords do not match, this will require them to be entered and submitted
again.

8.1.3.3 Assigning user to a group

In the details window for a user they can be assigned to a group. As previously mentioned new users are
assigned to no group while the admin user is assigned to the Admin group. To assign a user to another
group click on the “Assigned Group” listing box and select the desired group, then submit the request by
clicking on the “Assign to Group” button. The user will now be assigned to the group and have the
corresponding permissions when they log on next time. Figure 16 shows the window with options of
available groups.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 38 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 30: Groups available

To assign our training user to the Operator group we select it and click on the “Assign to Group”
button. The user now has privileges associated with the Operator group and will be activated
next time he/she logs into the system. Figure 17 shows that the Operator has been selected
and assigned to the user.

Figure 31: Assign user to new group

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 39 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

8.1.3.4 Register user for notification

Users can be registered for certain event notification via email. The user will receive an email containing
information on the registered event. To register select the desired checkbox and click the “Update
Registered Notifications”, similarly un-check the box to remove event notification. Table X describes the
events available for notification; a more in depth description is made in Section X.

Notification Description

The event lists the lock/locks that are in an

Unsafe Lock Unknown/Open state and not in any schedule. It
shows the last person who operated on the lock.

In the event of a duress alarm from a key users are

Duress Event
notified with the last known location for the key.

Tamper Event This event indicates that the key has been opened.

Table 3: System user events

To register the training user for the tamer event we select the event in the right-hand side box and click
“Update Registered Notifications”. Once this event occurs the user will be notified via email. It is
important to note that the user needs a valid email address to register for event notification. The
registrations will not update if the user has no or an invalid email address. Figure 18 shows that the
training user has been registered for the tamper event notification.

Figure 32: Register for event notification

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 40 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

8.2 Reporting

Reporting allows you to extract certain details on the current state of GLAM or the events that lead it
there. Each of the following reports have an option to only view the data in a table, to export it in a PDF
format or to export it as a CSV – this can be opened and view in spreadsheet applications like Excel.

8.2.1 Lock status reporting

Report on the system registered locks filter by their status – Open, Closed or Unknown – and/or their
commissioned status – Commissioned, Uncommissioned or Discovered. When navigating to the window
from the menu the default state is that all the locks will be displayed, Figure 19 shows this.

Figure 33: View all system locks

If you wanted a list of all the current locks that are commissioned but still open set the options
as follow:

Option Value
Status: Open
Commissioned Status: Commissioned
Table 4: Show commissioned open locks
This will now show all the commissioned locks that are open in this point of time. If we wanted to
pull out all the discovered locks in any state we would set the following:

Option Value
Status: All
Commissioned Status: Discovered
Table 5: Show all discovered locks

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 41 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

8.2.2 Key status reports

The key status reports list all the system keys and the keyholders to whom they are currently assigned.
The can be filtered according to assigned or unassigned but by default all the keys will be listed. Figure
20 shows the report window and its available options for keys.

Figure 34: Report on key status

8.2.3 Key activity report

The key activity report might seem a bit tedious but it allows for a lot of filtering on the logged events.
The activity report can be used to see what a key did in a certain period of time and in the same sense it
can be used to see what happened on a particular lock. The default report has some predefined event
checked that are desired in the report and will report on all the events that occurred in the system. Figure
21 shows the default window state.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 42 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 35: Key activity view

From this view we see a bunch of options available to us; Table 5 describes each options
capabilities and meaning.

Available option Description

Start time This is when we want to start looking at the
logged events
End time This is the time up until we want to view logged
events
Name & Surname Allows you to filter on a specific keyholder and
see what he/she has done in the timeframe.
Key The key can be filtered according to its
assigned serial number or the box number that
is printed on the outside of the key. This allows
us to view certain events that a key reported.
Lock The locks can be filtered according to a
matching RF tag or the descriptions that has
been assigned to them.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 43 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Notifications Each of the notifications can be checked or

unchecked and combined to view different
ranges of logged events. Events are shown in
the description and are explained in details in
Section X.
Table 6: Available key activity options

We are going to run a few case scenarios to view some of the settings needed for the
requirements.

To view what a certain keyholder did for today set the following:

Option Value
Start time Select today’s date
End time Select today’s date
Name/Surname Enter the keyholder’s name/surname or both
Notifications *Select all the notifications
*You can select and clear all the notifications with the “Select All” and “Clear All” buttons
Table 7: Options for keyholder

To view the lifetime events on a certain lock we set the following:

Option Value
Start time Leave empty
End time Leave empty
Lock Enter the RF tag number or the description
and select the appropriate selection of the two.
Notifications *Select all the notifications
Table 8: Lifetime events on lock

To view all the locks that was commissioned for a specified time range:

Option Value
Start time Select the desired start date
End time Select the desired end date
Notifications Select the commissioned notification
Table 9: View locks that were commissioned

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 44 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

8.2.4 System user lock changes

The lock changes allow us to view changes made to locks. These are changes made by the system
users such as validating and updating details as well as deleting a lock.

Figure 36: Lock changes view

The options that are available are explained in the following section.

Available Option Description

Lock RF This is the RF tag for the lock. It can be used
to filter to a specific lock and view its changes
Description The lock description that can be used as an
alternative to the RF tag.
Start date Start time when the lock changes occurred
End date End time when last lock changes occurred
Name & Surname System user name and/or surname that made
the changes
Operation This is the specific change made to the lock
which can be one of the following created,
deleted, updated, validated, lock replaced,
latch replaced or lock swapped.

Table 10: Lock changes options

We are going to run through a few test scenarios and see what options need to be selected.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 45 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

To see who validated a certain lock set as follows:

Option Value
Lock RF Set the lock RF to see who validated it
Operation Validated
Table 11: Report who validated lock

To see what locks a user validated set the following:

Option Value
Name/Surname Name or surname of the user in question
Operation Validated
Table 12: Report what locks user validated

To see all the updates made to a lock in a timeframe set the following:

Option Value
Lock RF RF tag for the lock to identify it
Description Lock description as alternative to RF tag
Start/End date Timeframe of changes made to lock
Table 13: Report updated made to lock

8.2.5 System user key changes

Similar to lock changes but only for changes made to keys. These are changes such as updating details
on a key, assigning a key and deleting a key.

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 46 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Figure 37: Key activity window

The available options are described in the following section.

Available Option Description

Key serial The serial number for the desired key
Key box number The box number that is linked to the desired
key
Name & Surname Name/surname of the system user that made
the changes to a/all the keys
Operation The operation performed on the key which can
be created, updated, deleted, assigned or
unassigned.
Start date Start time that the event took place
End date End time when last the operation was
performed.
Table 14: Report key option description

A few test examples are presented to show the different options selected.

To view who added the key to the system set the following:

Option Value
Key serial Enter the sought after key serial
Key box number Enter the box number if one exists instead of
the key serial
Operation Created
Table 15: Report user added key

To view who updated key details in a specific timeframe set the following:

Option Value
Key serial Key in question serial number
Key box number Key box number instead of serial
Operation Updated
Start and end date Timeframe that this occured
Table 16: Report user update key in timeframe

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 47 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

8.2.6 System user schedule changes

These reports allow us to view what changes have been made to schedules by the system users.

Figure 38: Transaction history

The transaction history can be used to filter out who made changes to a transaction for a key or
lock.

Available option Description

Key serial no Show the transactions created for a certain key
using its serial number.
Key box number Same as with the key serial but use the keys
box number instead
Lock RF Filter on a lock’s RF tag
Description Filter on the lock’s description
Start and end date Timeframe when the transaction details
changed or were updated
Name & Surname System user that made the change
Operation Operation performed on the schedule which
can be created, updated or deleted
Schedule Operation Filter on the type of schedule that was made
Table 17: Transaction history options

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 48 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Lists of possible scenarios are presented.

List the user that created a schedule for a specific lock

Option Value
Lock RF RF tag for the lock
Description Fill in the lock description if known
Operation Created
Table 18: Report user created schedule

List the user that removed a lock from a transaction in a specified timeframe.

Option Value
Lock RF RF tag for the lock
Description Fill in the lock description if known
Operation Deleted
Start and end time Timeframe that the schedule for the lock was
deleted.
Table 19: Report user deleted lock transaction

8.3 System administration

8.3.1 General system administration

GLAM consists of a few different applications that work together as a whole. Table 19 lists the main
processes and a description of each.

Process Description

Database The database stores all the information used by other processes. It is must be
running at all times and never requires to be restarted. It is recommended not to
start/stop this process.

Webserver The web server hosts the application that is used to maintain GLAM. As with the
database this service hardly ever needs to be shut down. Note that if the service
is shut down it can still be started from the web interface as long as the page is
not refreshed.

GLAM This is the core of GLAM. This service communicates directly to the keys out in
the field. As with the above listed processes it maintains itself and rarely needs
to be halted. Note that when this service is halted none of the keys out in the
field will be able to communicate.

Geoserver The geoserver serves all of the geospatial data for lock positioning in Google

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 49 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

Earth. It doesn’t need to be restarted that often but of all the processes this
process will cause the least amount of problems if it is halted.

Table 20: GLAM manageable processes

GLAM services can be managed from the web interface; processes can be halted or started. Upon
navigating to the system window you are presented with a view similar in Figure 25.

Figure 39: System status view

As can be seen all the system processes are running and the system is fully functional. The service is
running when its status is ‘Running’.

To stop a process click the corresponding button that says ‘Stop Process’ where process is the name of
the service to halt. A window will appear confirming the request as indicated in Figure 26.

Figure 40: Confirm stopping service

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 50 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

When the request is confirmed the system halts the process and updates the status accordingly. The
process is stopped when its status changes to ‘Stopped’ and the button now appears activate able.
Figure 27 shows that the key process has been halted.

Figure 41: Key service halted

8.3.2 Linux system administration

This section gives a more in depth explanation on how to manage GLAM from the server itself.
Breakdowns on the service management on the server along with some general configuration option are
explained in the following section.

8.3.2.1 Services
GLAM runs on a Mandriva distribution of Linux. All the service can be halted or executed through the
service scripts. Each of the services that make up GLAM can be managed this way.

You need to be the root user to perform these tasks. To become root enter 'su' and press Enter, enter
the root password; by default 'lockandroll'. You should be root user and this is denoted by the console
displaying root@hostname.

The general syntax to execute a script is as follows:

service <service-name> start

service <service-name> stop

service <service-name> status

Given the syntax to manage service you only need to specify the service name. Table X shows each
service name and a description of the service.

Service Name Description

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 51 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

glam-jgprsd Main service that communicates to the keys.

glam-jmonit Monitors system services and notifies connected clients of events.
glam-jmail Mailer service that notifies registered users of the events.
glam-jnotifier Logs when a lock is not scheduled but in an Open/Unknown state.
Jini Jini architecture used in the remote interface.
Remote interface running on Jini. The jini service needs to be running for this service
glam-jini-core
to run.
Mysqld Database service used to store all the data.
Httpd Apache web server .
Geospatial server that renders the data into a viewable format for Google Earth and
geoserver
other varies formats.
Table 21: GLAM services
8.3.2.2 Logs
Each of the above mentioned services store their output to log files on the system. The log file is used to
display behind the scenes actions and to store information when something goes wrong. Each of the
services has their own log files and it is sometimes use full to read the log in 'real-time'. This can be
accomplished by using the following command:

tailf <location-to-log-file>

By default all the services log their files to '/var/log/glam' and are distinguished by their respective file
names.

Service Log
glam-jgprsd Information log: glam-jgprsd.log
Errors log: glam-jgprsd.err
glam-jmonit Information log: glam-jmonit.log
Error log: glam-jmonit.err
glam-jnotifier Information log: glam-jnotifier.log
Error log: glam-jnotifier.log
glam-jmail Information log: glam-jmail.log
Error log: glam-jmail.err
glam-jini-core Information log: glam-jini-core.log
Error log: glam-jini-core.log

8.3.2.3 Configuration
All the services share the common configuration file that is located under '/etc/glam/glam.properties'. The
following table gives an overview of the different properties available.

Configuration Description Default

property
db.type Type of database we are using mysql
db.port Port on which database works 3306
db.user User to connect to database
db.password Password for the user

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.
 Document Title Docume Version Date Page:
Training Manual for the GridLock Access nt No
TM01 1.00 07 May 2009 52 / 52
Management (GLAM) System
Author File name
Keystone Electronic Solutions - KSES glam_tm.doc

db.host Location for the database

rmi.host RMI service hostname
rmi.port RMI service port 1099
sys.debug Debug details logged
glam.port Port which key service communicated 7777
email.host Host of email services
email.username Username for email
email.password Password for account
email.protocol Transport protocol to use SMTP
email.authenticate Authenticate with different user details false
email.auth.username Authentication username
email.auth.password Authentication password
email.from Email address that GLAM is using [email protected]
mail.client.server Mail uses this port to RMI server 40000
mail.server.client Mailer received events on this port 30000
monit.client.server Monitor user this port to RMI server 40001
time.pattern Pattern used to set start time yyyy-MM-dd HH:mm:ss
event.starttime Time we want to start receiving events system
jini.config Jini service configuration file location /usr/local/glam/glam-jini-
core/config/remote-glam.config
session.timespan Amount of seconds before log out user 300
debug.level Debug level to print messages 10
Table 22: GLAM configuration

9 GLOSSARY
Abbreviation Description
ACL Access Control List
CSV Comma Seperated Values
GLAM GridLock Access Management
KML Keyhole Markup Language
PDF Portable Document Format
RF Radio Frequency

10 REVISION INFORMATION
Date Version Comments
07 May 2009 1.00 Initial Document

This document contains confidential information, and may not be copied, circulated, or distributed without prior written consent of KSES.