This page outlines the process to generate a Full Notification File (DNF) for a Deanery/Local Office. This is a manual process and is required on Day 1 of a new Local Office switching on the TIS-ESR interface where they've previously been using the Intrepid-ESR interface.
...
- Take a backup of table EsrNotification in tcs database.
- Take a backup of table EsrNotificationDetailsRecord in ESR database.
- The full notification should be triggered after the daily applicant and notification jobs are finished. The last one starts at 5.30 p.m. Ideally this should be carried out over the weekend as there is not much of user interactions with the TIS application.
- The implication of running full notification results in duplicate high volume of applicant records generated during applicant export.
- Run the job https://build.tis.nhs.uk/jenkins/job/tis-esr-etl-full-notification/ with the below options selected:
- PLATFORM: prod
- whichever environment you want the full load to run
- OFFICE: Select the name of the deanery code you want to run the full load against.
- ESR_APP_LOG_LEVEL: Change it to DEBUG if you want to monitor the logs. Otherwise leave it as INFO.
The Jenkins job finishes after triggering the esr-etl load. ssh to the environment and grep the esr-etl log to see the progress of the load.
Code Block theme FadeToGrey heetis@HEE-TIS-VM-STAGE-APPS-GREEN:~$ docker ps -a|grep esr-etl 83729acdb151 repository.tis.nhs.uk:5000/hee/esr-etl:1.0.22.Final "java -XX:+UnlockE..." 7 minutes ago Exited (0) 6 minutes ago esretl_esr-etl_1 heetis@HEE-TIS-VM-STAGE-APPS-GREEN:~$ docker logs esretl_esr-etl_1
- Once the job finishes you should see a DNF file generated and uploaded to the corresponding Azure account inside the <currentDate>-outbound folder.
...