This guide aims to help our customers understand the Xray Preload Attachment and Its Status.

JCMA Preload Status Interpretation:

During the attachment preload process, Xray looks for each attachment listed in the AO_8B1069_ATTACHMENT table and attempts to locate the corresponding files in the local filesystem. It then exports the available files and sends them to JCMA. When files are missing from the disk, Xray logs a warning and reports this to JCMA, which then sets the preload status for each project as follows:

  • Failed Status: JCMA marks the preload as failed only when no attachments for a given project (or projects) can be found. In this case, the preload status is failed.

  • Incomplete Status: If some attachments are found and exported, but others are missing, JCMA marks the preload as incomplete, and all available files are successfully migrated.

  • Success Status: This status means all project(s) attachments were found on disk and successfully migrated to the Cloud.

Note:
A status of Failed does not indicate a failure in the preload process itself. It simply means the required files were not present on disk and therefore could not be exported.

Handling Missing Attachments During Xray Preload:

Xray logs a warning when files are missing and reports this to JCMA. However, this will not cause the migration to fail. Instead, the migration will be marked as incomplete because some attachments could not be migrated. If a new preload is performed for the same project, the same warning will appear unless the missing files are restored on disk.

In most migrations, missing attachment files are expected. Therefore, missing attachments should not cause the preload process to fail. This behavior has been consistently observed in JCMA since Xray implemented support for attachment preloading.

How the Xray Preload Attachments Work

Xray Data Center receives a trigger to start uploading the attachments. When the export is completed, JCMA sends a trigger to Xray Cloud, which copies all these files and stores them in Xray’s S3 in a special folder, waiting to start the actual migration so it can then use the attachments and place them in the correct entities.

If you have any questions or doubts, please contact the Xray Support team! 


 

  • No labels