Why are DCR deployed to LSDS server?

We just noticed (or actually paid attention to) that DCRs from templatedata are being deployed to the LSDS server. Also, they are not separated out by branch names - its just one templatedata folder. So two files with same path/names but different branches will overwrite each other.

Anyone know why Autonomy designed it this way? We are using the out of the box PLC workflow.

1. With LSCS in picture, I don't see the need for physical DCR files to be deployed to the LSDS server. Does anyone know why DCRs are needed on LSDS server? The best guess we have is that components with DCR Datum need them.

2. What workaround are you using so DCRs don't overwrite eac other?

Thanks!

Linux, 7.3.2. LSCS, LSDS on an IIS server.

Find more posts tagged with

Comments

nipper

This is COMPLETELY wrong.

When using LSCS you want these files on LSDS. Here is why

When you query LSCS, you get a list of DCRs that match your query but not the complete data. Then you need to get the DCR data itself. That can be from LSCS but if you have the DCRs local, why not just open a local file instead of making one or more calls to LSCS.

You have to make a query per DCR you want, so if you need a lot of data, it is easier to open a local file

argh_teamsite

Thanks for responding.

I am not sure what is 'completely' wrong.

I see your point that having those files locally could help performance, but it runs counter to the idea of having a server for content.

More importantly however - in your case - are all these files not being deployed to the same templatedata folder on LSDS?

That is my biggest issue. All templatedata files from 4 different branches are being deployed to one folder for me: \Interwoven\LiveSiteDisplayServices\runtime\web\templatedata. I want to better understand why and any dependencies before I muck around with the OD configs separating them out by branch.

nipper

When you start performance testing you will see my point

Deploying from multiple branches to a single runtime is a dicey proposition in general. DCRs are the least of your worries, you can use FormAPI to save them to sub directories. I would be more concerned about other items on each branch.

Rick Poulin

Generally, the solution to using a single webroot is to employ a unique namespace the folder path within the workarea, even though it looks kinda redundant within TeamSite. For example,

/templatedata/category/datatype/data/branchname/***

If your users can't be trusted to save within that subfolder, you can use FormAPI as mentioned by nipper to automate the DCR naming.