2

I am in the process of creating the Archive Manager DB to setup Archive Manager for a website. This website can be published to two publication targets and I was wondering if archive manager makes any distinction per publication target. I know it does distinguish by url (preview.site.com vs live.site.com), but was wondering:

  1. Is it possible at all to use the same db for both?
  2. Most importantly, is it recommended to do so? What do best practices say?

Thanks,

|improve this question
1

There are modules of the Archive Manager that are installed and configured in the deployer and the storage layer. Since you will have a different deployer / storage for your preview vs. live website; there should NOT be any technical limitations per publication target. The resolution in the Archive Manager database, I believe, is done by the URL (and not relative); so there should not be any issues.

If we are using the same db for both of the publication targets; we will have to account for user experience who is using the Archive manager explorer. By using inclusion rules, I would recommend using a different Archive Manager explorer interface for preview vs. LIVE.

Hope it helps!

|improve this answer
  • Thanks Shiva, I totally agree on separating the db per target, specially for the Production-Live target. – Jaime Santos Alcón Jul 13 '16 at 14:08
  • And after thinking about it, due to maintainability, I would probably recommend having separate am dbs per site too, so there's not archives of siteA.com in the same db of siteB.com – Jaime Santos Alcón Jul 13 '16 at 14:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.