Page Comparison

There are 5 jobs in sync service:

...

Sequence Diagram for sync jobs:

...

The processing flows of PersonPlacementTrainingBodyTrustJob, PostEmployingBodyTrustJob, PostTrainingBodyTrustJob are similar to PersonPlacementEmployingBodyTrustJob, so there's no need to repeat the diagram.

Time scheduled

00:05 PersonOwnerRebuildJob

00:09 PersonPlacementEmployingBodyTrustJob

...

01:29 PersonElasticSearchSyncJob

01:45 PostFundingStatusSyncJob

02:00 PersonRecordStatusJob

If the container is restarted in a pre-defined time range (00:00:00+00:00 to 07:00:00+00:00) then the jobs are run sequentially.

Job Execution Order

Image Removed

Summary of what to run:

...

PersonPlacementEmployingBodyTrustJob

...

Re-run PersonPlacementTrainingBodyTrustJob

  and PersonElasticSearchSyncJob

...

Run jobs out of schedule

Instructions taken from Refresh Elasticsearch cache page.

Note: All the time are here in UTC

Run jobs out of schedule

Where possible; it is easiest to use the web interface at the root of the application (https://<host IP/domain name here>/sync/.).

DEPRECATED:

If a job needs to be run manually, e.g. after a database has been re-imported to stagefrom the server, the instructions taken from Refresh Elasticsearch cache page can be used:

1. Copy the commands below into your favorite text editor.
2. Replace the $bean_name and $job_method with the ones for the job you are re-running.
3. ssh into either the blue or green server and paste the modified commands in a single chunk and it will go through the process of:
   1. downloading the JDK and the JMX client
   2. copy them to the container
   3. extract the compressed JDK
   4. launch the JMX client and
   5. restart the sync job.

...