Asset Ingestion to AEM and workflows

[georhe6]

Hi Team,

We are planning to ingest assets from GCP into AEM. The total size of the assets will be around 1.5 GB. Should we disable any asset-related workflows, such as Batch Update or DAM Update Asset workflows, during this process?

We will initially ingest 30% of the assets into the AEM development environment, and then move the complete set of assets to the Stage and Production environments.

AEM as Cloud service version of AEM

Thanks,
Geo

[Saravanan_Dharmaraj]

@georhe6  Please check this Adobe's solution on offloading the WF run for bulk upload

https://helpx.adobe.com/experience-manager/kb/comon-aem-assets-ingestion-issues.html

Either you can switch off the WFs and import and then you have to run the WF for those imported assets. Or you can import into another AEM instance(with WF running) and bring the processed assets into the main author instance(w/o WF running during import) and then enabled the WF back. 

[RiteshY18]

considering network bandwidth to handle large amounts of file and size 

-  optimized/dedup assets 

- disable workflow

- if disabling is not an option customized to keep only required steps 

- if disabled, rerun using the profile for specific folders/files

- increase CQBufferedImageCache consumes heap during Asset uploads

- Use asset bulk importer for chunk upload

[Shashi_Mulugu]

@georhe6 can you please elaborate your ask? Is you AEM on-prem? AMS? Cloud?

Process might differ based on type of deployment.

[georhe6]

We are on AEM as Cloud service

[kautuk_sahni]

@georhe6 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!