Submit the historical PolicyCenter batch jobs

About this task

These tasks show details about submitting and monitoring the historical batch job that's described in the following topic: PolicyCenter export to Canvas.

Procedure

Ensure that Secrets Manager on Guidewire Cloud Platform contains a canvas.user key that represents a valid PolicyCenter user.
At the Batch Process Info screen in PolicyCenter, run the Canvas Historical Record batch job.
To monitor the progress of the Canvas Historical Record batch job, monitor the corresponding CanvasHistoricalRecord_Ext work queue on the Work Queue Info page.
Specifically:
- Monitor the Failed column to ensure that all records process successfully.
- Watch for the Available and Checked Out column values to drop to 0.
After the Canvas Historical Record batch job completes, return to the Batch Process Info page and run the Canvas Outbound File batch job.

The effect is to write out the historical records to a single extract file on AWS S3. The writing takes only a few seconds.
To verify successful completion:
- Ensure that no work items are in Failed status for the CanvasHistoricalRecord_Ext work queue. If the Count value isn't 0, review the cause of each failure.
- Request that someone with access to the AWS S3 bucket for the region verify that the policy extract file was generated and placed in the S3 bucket canvas directory and that the content looks correct on visual inspection.
- Verify that Canvas has consumed the policy extract file from S3 and that the output looks correct in Canvas.