Moving DAM Assets | Community
Skip to main content
G
Gunars_V
Level 3
March 9, 2016
Solved

Moving DAM Assets

  • March 9, 2016
  • 1 reply
  • 1443 views

I have a large amount of DAM assets (mostly PDFs) to move from our Production environment down to our development environments. I have been packaging all of this up via Package Manager and manually installing each package to each environment. I also disable the WorkflowLauncher when installing as described in the Adobe documentation.

I noticed that two workflows get kicked off when installing the packages: DAM Update Asset and DAM MetaData Writeback that eat up a lot of memory/processing time. Since I am only moving assets from one AEM environment to another, is it OK to disable these two workflows when installing content packages?

Thanks in advance!

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Jitendra_S_Toma

    Here is a very good tool developed by TWC. I have been part of this project so i can say. it worth trying it. It is designed for large data transfer from one system to another.

    https://github.com/TWCable/grabbit

    FYI: CRX Packaging will not help at all in large assets.

    ---Jitendra

    1 reply

    Jitendra_S_Toma
    Jitendra_S_TomaAccepted solution
    Level 10
    March 10, 2016

    Here is a very good tool developed by TWC. I have been part of this project so i can say. it worth trying it. It is designed for large data transfer from one system to another.

    https://github.com/TWCable/grabbit

    FYI: CRX Packaging will not help at all in large assets.

    ---Jitendra

      Terms & ConditionsAccessibility statement

      Loading footer...