What good is "Development" deployment in PLC?

If this is a dumb question because it's documented in some manual somewhere, I totally apologize now, because we haven't found the answer. If the answer is "RTFM" please enlighten me as to which manual, section/page would be helpful.

What does selecting "Development" in a Publish LiveSite Content do for me? After that deployment completes is there some magical URL I can use to see my 'stuff'?

(I asked this question to a number of people, including some IWOV people, and no one seems to know)

Find more posts tagged with

Comments

nipper

With LSCS it deploys stuff to your DB

OOTB, LSDS only, not much, but you can change it to push to a preview server.

Crsb

development target maps to development DB and the preview node in lscs-authoring.xml. the task does datadeployment to the dev DB and lscs deployment to whatever you designated as your preview node, by the default it is localhost (TeamSite server). this is only useful when you want to execute lscs queries against that preview (development) environment.

test.rptdesign

que_giro

development target maps to development DB and the preview node in lscs-authoring.xml. the task does datadeployment to the dev DB and lscs deployment to whatever you designated as your preview node, by the default it is localhost (TeamSite server). this is only useful when you want to execute lscs queries against that preview (development) environment.

We have TS 7.3.1, LSDS and LSCS. We don't have any "preview" installations, except what comes out-of-the-box. We are not using Targeting either.

Here's what someone told me re. publication to the Authoring/Development target node:

"Please note that in 7.3.1 version the Authoring publish has changed. Workarea gets sync’d with the Preview automatically so nothing gets published in that env ... the Authoring deployment task that PLC in new version performs is OD/DD to db for tags and then kicks off import handler so IDOL OEM index can be updated. Physical content is not needed for authoring as that gets sync’d automatically."

However, after an Authoring/Development deployment which included files with metadata, I checked all the SitePub and other Authoring-side database tables. Apparently, none of them was updated. The OD deployment logs show no activity.

As for LSCS on the Authoring side, one seems to be able to access all versioned documents (without having used the PLC workflow at all) using a URL such as:

http://server:8080/lscs/v1/document$?q=*&project=//server/default/main/mybranch

So I'm not sure what the "kicks off import handler so IDOL OEM index can be updated" is for.

By the way, during a Runtime/Production deployment, if the Reviewer decides that Revisions are needed, after the Author makes his changes as per the Reviewer, the PLC workflow does not deploy anything back to the Authoring environment. Hmm ... I'm tempted to remove the Authoring deployment from my copy of the PLC workflow.

Anyway, it seems to me that Autonomy needs to revamp the PLC workflow. It's contrived and obscure. Trying to figure out what it does, e.g., what it deploys to where is a struggle. It should use the plain old OD "iwodcmd" command to copy data and files, so all activity would show up in the OD log files.

Thoughts?

Thanks,

S.