...

• Denodo VDP

  • human_resources

    • 01-base_layer

      • 01-connections

        • ds_eh_hr_feed_data_queue

        • ds_eh_hr_feed_session_id

      • 02-base_views

        • bv_eh_hr_feed_data_queue

        • bv_eh_hr_feed_session_id

    • 02-transformations

      • persons_health

      • persons_health_current_cache

      • persons_health_previous_cache

    • 03-integration

      • j_persons_health_country

      • persons_eh_hr_feed_data_queue_history

      • persons_health_current_previous_diff

      • persons_eh_hr_feed_data_queue_incremental

      • persons_eh_hr_feed_data_queue_manual

• Denodo Scheduler

  • eh_hr_feed_data_queue

  • eh_hr_feed_data_queue_failure_check

• Lambda

  • enterprise-health

How-To

...

Once the cache is invalidated, run the feed job in the scheduler.

Feed failures

The job eh_hr_feed_data_queue_failure_check will run after the feed job is complete to see if any records failed to send to EH by querying the cache for human_resources.persons_health_eh_hr_feed_data_queue_incremental. If any failures are found, a CSV is generated and sent out via e-mail to the Tufts Denodo team email address (denodo-devs@elist.tufts.edu). If the event of a job failure, a separate email will be sent from either job to the same email address.

Failures of status 500 typically mean there was an issue with the EH server, with 400 meaning there was an issue with the request/data. For 500 errors you can just re-send, however 400 errors should be investigated.

You can re-send failed emp_id’s by running the following two queries.

Store a fresh EH session ID

SELECT 
  * 
FROM human_resources.bv_eh_hr_feed_session_id 
CONTEXT('cache_wait_for_load' = 'true', 'cache_invalidate' = 'matching_rows', 'cache_preload' = 'true');

Send the records to EH

SELECT 
  * 
FROM human_resources.persons_health_eh_hr_feed_data_queue_manual
where emp_id in (/*EMP ID's go here*/)
CONTEXT('cache_wait_for_load' = 'true', 'cache_preload' = 'true');