CIF Processing: Difference between revisions

From acumen Wiki
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
Application servers connect to the NR PPTE (Network Rail - Pre Production Test Environment) to download the POINTA CIF.
Application servers connect to the NR PPTE (Network Rail - Pre Production Test Environment) to download the POINTA CIF.
<b>What to look for</b>
Throughout these CIF logs we are looking for an entry for the previous day's date to ensure the most recent CIF has been processed.
<b>Note:</b> Here the host name in PuTTY is likely to be acumen.tms-uk-rail.co.uk. (Rather than gateway.tms)


=== Container Logs ===
=== Container Logs ===
Line 45: Line 51:


::3. <code>Enter password: <password></code>
::3. <code>Enter password: <password></code>
<b> Note: </b> This is a long password! Shift + Insert will paste into PuTTY. As will a right-click + Enter.


::At the database prompt, enter the following commands:
::At the database prompt, enter the following commands:
Line 50: Line 58:
::4. <code>MariaDB [(none)]> USE cif_record;</code>
::4. <code>MariaDB [(none)]> USE cif_record;</code>


::5. <code>MariaDB [(none)]> SELECT * FROM tbl_header;</code>
::5. <code>MariaDB [cif_record]> SELECT * FROM tbl_header;</code>


::The contents of the table will be printed to the terminal thus:
::The contents of the table will be printed to the terminal thus:
::[[File:Cif record screenshot.png]]
::[[File:Cif record screenshot.png]]
::Administrators can check that each CIF has been downloaded and processed.
::Administrators can check that each CIF has been downloaded and processed. The last letter in the txt_current_file_ref and txt_last_file_ref entries should be alphabetical.


::6. Type the following to exit the database command line facility: <code>MariaDB [(none)]> exit</code>
::6. Type the following to exit the database command line facility: <code>MariaDB [(none)]> exit</code>

Latest revision as of 09:38, 25 August 2020

Application servers connect to the NR PPTE (Network Rail - Pre Production Test Environment) to download the POINTA CIF.

What to look for

Throughout these CIF logs we are looking for an entry for the previous day's date to ensure the most recent CIF has been processed.

Note: Here the host name in PuTTY is likely to be acumen.tms-uk-rail.co.uk. (Rather than gateway.tms)

Container Logs[edit]

As described in the Data Feeds section, the full CIF is taken and processed at initialisation and an incremental CIF is taken and processed at 01:00 Hrs each morning.

The service that obtains and processes the CIF is ran via a cron job and once the CIF is processed, the container stops running; despite this, Administrators can view the last container log entry thus:

  • Start an ssh session to the relevant application server;
  • At the prompt, enter the following commands:
  1. <user>@acumen-app-server:~$ cd ~/dockerise/
  2. <user>@acumen-app-server:~$ docker-compose logs download_cif

If there were any issues in downloading and processing the CIF, there would be a corresponding entry in the container logs.

Application Logs[edit]

To browse the application logs, follow the following steps:

  1. Identify the ip address of the server in the Administration page;
  2. Browse to the following url: http://<ip address>:8080/logs/download_cif/

There are numerous logs available that are of interest - the main ones being:

  • download_pointa_cif.log;
  • extract_cif.log;
  • post_processing.log;
  • assoc_post_processing.log.

Should any error messages or other log entries of concern be identified, Administrators are requested to update the support ticket with the details.

Check CIF Records in Database[edit]

Administrators are required to access the Database CLI (Command Line Interface) to check the status of the CIF downloads.

  • Start an ssh session to the relevant application server;
  • At the prompt, enter the following commands:
1. <user>@acumen-app-server:~$ cd ~/dockerise/
2. <user>@acumen-app-server:~$ docker exec -ti dockerise_mysql_1 mysql -u tms_user -p
When prompted, enter the password:
3. Enter password: <password>

Note: This is a long password! Shift + Insert will paste into PuTTY. As will a right-click + Enter.

At the database prompt, enter the following commands:
4. MariaDB [(none)]> USE cif_record;
5. MariaDB [cif_record]> SELECT * FROM tbl_header;
The contents of the table will be printed to the terminal thus:
Cif record screenshot.png
Administrators can check that each CIF has been downloaded and processed. The last letter in the txt_current_file_ref and txt_last_file_ref entries should be alphabetical.
6. Type the following to exit the database command line facility: MariaDB [(none)]> exit