8/6/2019 GNS Training

1/6

GNS Meeting: Bangalore Chennai

Meeting Date : 24th December, 2010

Documented By: Himanshu Kumar

Copyright 2008 Bally Technologies Inc. All Rights Reserved.

This documentation contains confidential and proprietary information of Bally Technologies Inc. Noportion of this document may be reproduced or transmitted in any form or by any means, electronic ormechanical, for any purpose, without the express written permission of Bally Technologies Inc.

Please ensure that you are using the latest version of this document.

8/6/2019 GNS Training

2/6

DIFFERENT THREADS IN GNS

GN2

ISeries

GNS

thiWrite

Process

Thread

thiRead

iWrite Q

iRead Q

thAlarm

Alarm

thgRead1

thgRead2

thgWrite

thgWrite

Process Q

gWrite Q1

gWrite Q2

thBackup thACK

Backup HAS

thAudit

GN1

thEventLog

eWrite Q

8/6/2019 GNS Training

3/6

8/6/2019 GNS Training

4/6

6. Process Thread is the main thread which communicates with other threads for different purposeusing Queues.

For functioning of threads, every thread has its own Queue for reading or writing data respectively.

NOTE: All the Transaction is done through Queue

Number of Queues in GNS/HAS [LOOKOUT IN FIGUREFORORANGE COLOR]

1. One Process Queue for Process Thread.2. One Alarm Queue for Alarm Thread ( thAlarm ).3. One each Write Queue for each Write Thread ( thgWrite )of corresponding GN in Casino.4. One Write Queue for Write Thread ( thiwrite ) for sending data to iSeries.5. One Read Queue for Read Thread( thiRead ) for reading data from iSeries.

1). Alarm Thread ( thAlarm ) :

1. This Thread has its own Queue (Alarm Q) to interact with Process Thread.2. Responsible for handling all the alarms in the system (catastrophic error, file access

error, connection error, etc) and logging.3. Responsible for checking whether all the others servers are connected or not (validates

the integrity of the connections by pinging every 10 secs).4. It will queue up the corresponding alarm message for interactive announcement.

2

). Ev

ent Log Thread ( thEv

entlog ) :1. This Thread has its own write Queue (eWrite Q) for writing to Backup HAS and use

process Queue for reading any Log Events.2. Responsible for logging the events (what we do in the system) at different levels

(information or error or anything else).3. We have two database one stores all kind of events and other is used to store patron

information (primarily database).4. All the events in the main thread in the queue and this thread will read it from the

queue and log it into the database (Non blocking call).

3.) Process Thread

1. This is the main thread which communicates with every thread in GNS via differentQueues as shown in above figure. It has its own Queue called Process Queue which isbeing read by EventLog Thread ( thEvenetLog) and Read Thread (thgRead forGNS_GN communication ). Look out in Figure.

8/6/2019 GNS Training

5/6

8/6/2019 GNS Training

6/6

8). Write Thread ( thgWrite ) [GNS GN]

This thread is used to write data back to GN which is processed by Process Thread via a writeQueue (gWrite Q) as shown in Figure.

9). Read Thread ( thgRead ) [GNS GN]

This thread is used to read data coming from GN directly into the Process Queue. It doesnthave any its own Queuelike (thgWrite).