831 Daily Hash Check Reports
Background: Under Italian Regulation we are required to send MD5 Checksums of critical errors of the system to the regulator daily. If we send an 831-game message containing game hashes after 8am Italian time, it will not be processed until following day.
Hashes are automatically sent to meet this timing requirement at 04:30am and a report is run afterwards to confirm what responses are received back from Sogei.
Any non-Successful codes will be sent to helpdesk every day which will need to be actioned by the person on the early shift. Service desk must maintain ownership of the ticket(s) throughout the ticket lifecycle by everyone placing a watch on the master ticket.
High Level Overview of Response Codes
Response Code 2340 - Pass straight to Devs and let PM know.
Response Code 2456 - Incorrect number of modules
Response Code 2497 - The name of the critical module is incorrect
Response Code 2498 - Hash value is incorrect, and the module name is correct.
Response Code 2460 - Critical module names & hashes are missing
Actions to be taken against each response code:
Response Code 2340 - Service Desk pass straight to the Development queue and cc in PM Elena/Aine
Response Code 2456 - These types are the most common and are relating to Incorrect number of modules (Identifiers)
Service Desk Action:
- Service Desk to send the data to Giorgio and request to review the Module Name, Hash, Sogei Game Version (and any sub-version) is correct.
- Once the information has been reviewed from compliance if feedback is received that a version or hash needs to be added or removed pass to DBA.
- DBA could close the script at this point as the ADM report the next day will return either a success or a 2497 or 2498.
Note, module name may have version name and can be ignored.
Response Codes 2497 – ADM are reporting that the name of the critical module is incorrect.
- Service Desk to email Service Provider with the 2497 template
- If the provider respond "yes" they are correct ask Compliance (Giorgio) what the latest version (and subversion) was declared as to ADM in the private portal.
- If the provider reports the game is at its EOL (end of life) a request to remove the games should be sent to Umberto Facciolla which should be done from within OTRS
- In Parallel to step 3 critical modules should also be removed. Game ID to be set to negative (DBA)
- If the provider responds with different module/hash names. Service Desk to pass back to DBA to update the list of Modules so they match with the game providers.
- DBA will run a script to correct the data, 831 hash report will run the next day and the cycle will begin again. The reported module should be correct the next day.
- Pending DBA direction this may then go to App Support to re-run the 831’s
Response code 2498 - Hash value is incorrect, and the module name is correct.
- Service Desk to email Compliance (Giorgio) with the 2498 template
- Compliance will respond with the hash in the ADM reserved area
- If hash is the same, service desk to email the provider using the 2498 template
- When provider provides the correct hash, pass the information to DBA team.
Response Code 2460 - Critical module names & hashes are missing
- Service Desk send data to the relevant provider to ask them to share the critical module names & the hashes,
- When response is received confirm with Giorgio if the data is accurate and the same in the ADM area as the providers.
- When critical modules and hash is confirmed correct assign to DBA to add to the database
- If the provider reports the game is at its EOL (end of life) a request to remove the games should be sent to Umberto Facciolla which should be done from within OTRS
- In Parallel to step 4 critical modules should also be removed. Game ID to be set to negative (rob)
Contacts:
Name |
Dept |
|
Giorgio Ranieri |
Compliance |
|
Umberto Facciolla |
Retention Marketing Manager |
|
Robert McGregor |
DBA |
|
Filip Nastasie |
DBA |
|
Dave Robertson |
Java Dev |
|
NetEnt |
3rd Party Provider |
|
Tuko |
3rd Party Provider |
|
Habanero |
3rd Party Provider |
|
BetGames |
3rd Party Provider |
|
RedRake |
3rd Party Provider |
|
BetSoft |
3rd Party Provider |
|
Triage Link
https://stanleybetagile.atlassian.net/wiki/spaces/PGDA/pages/1385070593/How+to+triage+fix+PGDA+831
Note: Identifiers are also known as critical modules.