Non-UUID to UUID content migration id226TI0U20XA

Install the pre-migration package com.adobe.guides.pre-uuid-migration-1.2.27.zip over version 4.3.1.

If there are more than 100,000 DITA files in the system, update the query limit configs for the script to work:

• Navigate to /system/console/configMgr and increase both the configs to more than number of assets - queryLimitInMemory and queryLimitReads under org.apache.jackrabbit.oak.query.QueryEngineSettingsService

Launch http://<server-name>/libs/fmdita/clientlibs/xmleditor_uuid_upgrade/page.html.

Select Compatibility Assessment from the left panel and browse the /content/dam folder path for all assets.

Check the compatibility to list the following information:

• Total files
• Estimated time for migration
• Number of files with errors
• Files with GUID filename

If the error appears, then analyze the logs and fix those errors. You can re-run the compatibility matrix after fixing the errors.

Select Configure Validations from the left panel. Then, Select map and Select preset of the map to configure them. The current output validation list displays the output files present before migration and can be validated against the output files generated post-migration later.

By selecting multiple and large DITA maps, you can validate that all the content has been successfully migrated without issues. Selecting presets with baselines in them, also ensures that baselines and versions are migrated successfully.

(Optional) Perform version purging on the content to remove unnecessary versions and speed up the migration process. To perform version purging, select the option Version Purge from the migration screen and go to the user interface using the URL http://<server- name>/libs/fmdita/clientlibs/xmleditor_uuid_upgrade/page.html.

Execute UUID migration only on an Author instance.

Ensure the following infrastructure readiness:

• Author instance is upsized in terms of CPU and memory to support faster processing and additional memory needed for bulk activity. for example, if the current allocated CPU and memory are 8 vCPU and 24 GB heap, then use double the size for this activity.
• The overall disk space and temporary disk space (crx-quickstart directory) should have a buffer of 10 times what is already consumed. Once you complete the migration, you can reclaim most of the disk space by running compaction.
• Do run Offline Tar compaction before starting this activity.
• Make sure that no indexing or system maintenance is planned during the window of this migration.

Install the UUID version of the supported release over the non-UUID version. For example, if you’re using 4.3.1 non-UUID build, you need to install UUID version 4.3.2 com.adobe.fmdita-6.5-uuid-4.3.2.1977.zip) and run the migration.

Install the uuid migration upgrade package com.adobe.guides.uuid-upgrade-1.2.110.zip.

Disable launchers for the following workflows using the URL: http://<server-name>/libs/cq/workflow/content/console.html.

• DAM Update Asset workflow
• DAM Metadata Writeback workflow

Update the following configurations as per the suggested changes:

Add a separate logger for:

• com.adobe.fmdita.uuid
• com.adobe.guides.uuid.

(If not done earlier) If there are more than 100,000 DITA files in the system, update the queryLimitReads under org.apache.jackrabbit.oak.query.QueryEngineSettingsService to a larger value (any value greater than the number of assets present, for example 200,000).

Launch http://<server-name>/libs/fmdita/clientlibs/xmleditor_uuid_upgrade/page.html.

Select System upgrade from the left panel to run the migration. It’s recommended to migrate all the data at once, as the system optimally handles batching internally. Only files that are not DITA assets and are not used in any DITA assets can be skipped for migration.

(Optional) Select the folders for which you want to skip the migration. Use this option to migrate these folders later or skip migrating them. Ensure that these folders don’t have any DITA assets and aren’t referred by (and in the future won’t be referred by) any DITA assets. For example, content/dam/projects.

Select Enable dita asset backup to create a backup of asset before migration. This backup is used to rollback in case there is an error in migrating a file. The backup is deleted, if the migration is successful. However, this slows down the migration process.

Start the migration.

Once the migration is complete, the report is available to download and entire logs can also be downloaded.

Select Download Report while the migration is running to check whether all files in the folder are upgraded correctly and whether all features work only for that folder.

Also, it’s important to make sure that the content migration is done for all the media assets, such as images and graphics you have used in the DITA content.

Once all the files are migrated, select Baseline/Review Upgrade from the left panel to migrate the baselines and review at the folder level.

Once the migration is completed, select Validate system upgrade from the left panel and validate the output files before and after the migration to ensure that the migration is successful.

After migrating the server successfully enable the following workflows and configurations (including all the other workflows that were disabled initially during the migration) to continue working on the server:

• DAM Update Asset workflow
• DAM Metadata workflow

Enable the following configurations:

Assets properties to review post migration:

After the validation is done, most of the disk space can be reclaimed by running compaction (refer to https://experienceleague.adobe.com/docs/experience-manager-65/deploying/deploying/revision-cleanup.html?lang=en).