we are going live with our new site and uploaded 10k+ images to our staging environment , we need to move these images to production for go live.
we tried copying 5 images using vlt rcp from stage to production environment. as per the vault log the copy is success . but the images are broken in the production environment.
how do we copy huge dam content between environments?
using package manager takes lot of time to build and install these packages. can some one please provide us steps to handle huge dam content to be exported accross environments.
Solved! Go to Solution.
Views
Replies
Total Likes
I would recommend you reading:-mRe: Bulk Import Assets in AEM DAM
// The reason for using MongoMK should be based on your scalability/HA requirements[0].
By default, you would use TarMK, and the assets would be included in the repository files. However, for large DAM installations we recommend using an external data store which can be done with TarMK or MongoMK.[1]
Either way, you should batch your uploads to reduce the strain on the system, consider doing this during this when user activity is at it's lowest. Another option is to stop the DAM Upload Asset workflow, during uploads and have a script that is run after the uploads. Have a look at the comments section of [2]
You can always write your own java application that uploads content to AEM calling the slingpostservlet passing in the correct parameters location, properties etc
Whatever you do, you must test out your full upload on a test system, to determine the best approach, e.g. batch size, and any optimizations that should be configured such as [3]
[1] Configuring node stores and data stores in AEM 6
[2] https://edivad.wordpress.com/2013/01/07/installing-big-packages-in-cq5crx/
[3] http://cq-ops.tumblr.com/post/122108616399/the-importance-of-javaiotmpdir-in-dam-asset
Views
Replies
Total Likes
I would recommend you reading:-mRe: Bulk Import Assets in AEM DAM
// The reason for using MongoMK should be based on your scalability/HA requirements[0].
By default, you would use TarMK, and the assets would be included in the repository files. However, for large DAM installations we recommend using an external data store which can be done with TarMK or MongoMK.[1]
Either way, you should batch your uploads to reduce the strain on the system, consider doing this during this when user activity is at it's lowest. Another option is to stop the DAM Upload Asset workflow, during uploads and have a script that is run after the uploads. Have a look at the comments section of [2]
You can always write your own java application that uploads content to AEM calling the slingpostservlet passing in the correct parameters location, properties etc
Whatever you do, you must test out your full upload on a test system, to determine the best approach, e.g. batch size, and any optimizations that should be configured such as [3]
[1] Configuring node stores and data stores in AEM 6
[2] https://edivad.wordpress.com/2013/01/07/installing-big-packages-in-cq5crx/
[3] http://cq-ops.tumblr.com/post/122108616399/the-importance-of-javaiotmpdir-in-dam-asset
Views
Replies
Total Likes
Nice answer!
Views
Replies
Total Likes
Views
Likes
Replies