Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Publishing rendition assets from one DAMS instance to another publishing instance

Avatar

Level 3

We have historically used an AEM instance for web content management.  The assets repository for that instance retains assets used/published on those web properties.

We would like to have a separate DAMS instance to house all original master assets that published renditions are created from.  This "global" repository would have heavy ingest and update use and architecturally would be tailored for managing those large and many original assets.  Isolating performance impacts from the web content publishing instance is the driving thought behind this.  Can asset renditions suitable for web presentation be shared/published from this global DAMS into the instance for web publishing via a best practice or proven use case?  We would like to update one master asset and new renditions would then be replicated to the publishing instance for update to all end pages utilizing that asset.

Any thoughts, direction or reference would be greatly appreciated.

Jim P

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi Jim , 

Here are few points which may be helpful in answering your question :

- You can have separate DAM system to store all original master asset and renditions.

- To avoid performance impact due to ingestion of assets , you can configure dam workflow offloading. Refer [0] [1] for more info.

- You can also configure Dynamic Media to generate custom rendition on the fly without storing in repository. Refer [2] for more info.

- Also make sure you are following best practices for scaling and sizing of the architecture. Refer [3] for more info.

Hope this helps.

 

Best Regards,

Abhishek

 

[0] https://docs.adobe.com/docs/en/aem/6-2/administer/content/workflow-offloader.html

[1] https://docs.adobe.com/docs/en/aem/6-2/administer/content/assets/best-practices-for-assets/assets-of...

[2] https://docs.adobe.com/docs/en/aem/6-2/author/assets/dynamic-media.html

[3] https://docs.adobe.com/docs/en/aem/6-2/administer/content/assets/best-practices-for-assets.html

View solution in original post

0 Replies

Avatar

Level 10

Watch this session on Ask the AEM Community Experts - our Assets experts covers best practices.  I will also ask them to look at this thread. 

Avatar

Level 3

Thanks Scott.  Nice overview, but nothing specific to this.  Anything that pertains to this subject would be great.

Jim P

Avatar

Correct answer by
Employee

Hi Jim , 

Here are few points which may be helpful in answering your question :

- You can have separate DAM system to store all original master asset and renditions.

- To avoid performance impact due to ingestion of assets , you can configure dam workflow offloading. Refer [0] [1] for more info.

- You can also configure Dynamic Media to generate custom rendition on the fly without storing in repository. Refer [2] for more info.

- Also make sure you are following best practices for scaling and sizing of the architecture. Refer [3] for more info.

Hope this helps.

 

Best Regards,

Abhishek

 

[0] https://docs.adobe.com/docs/en/aem/6-2/administer/content/workflow-offloader.html

[1] https://docs.adobe.com/docs/en/aem/6-2/administer/content/assets/best-practices-for-assets/assets-of...

[2] https://docs.adobe.com/docs/en/aem/6-2/author/assets/dynamic-media.html

[3] https://docs.adobe.com/docs/en/aem/6-2/administer/content/assets/best-practices-for-assets.html

Avatar

Level 3

Thank you Abhishek, very helpful.  If there is any documentation at all on how to publish from one DAMS instance to the publishing instance of another, I'd love to see them. 

Thanks again!

Jim P