nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Confusion over location / usage of LSCS

Adam Stoller

I'm trying to draw up some diagrams to explain (both to myself and my customer) some aspects of the LiveSite environment - and I find myself getting confused by the manual (big surprise there - eh?)

This is a 7.2.1 environment, so I'm looking at

ls_72_runtime_install_rev3_en.pdf

Find more posts tagged with

Comments

Adam Stoller

Continued reading and, ...
in

ts_72_author_install_rev4_en.pdf

nipper

Yes you have 2 LSCS runtimes, one is the authoring environment and one is the prod env.

LSDS does not contain LSCS, they are separate installs on TS and on the ap servers. Can be the same server but also can be different.

I have set up LSCS AT for preview but more for development. You will need that to develop the components and things that consume the LSCS data.

Finally there is very different behavior at 7.3.1, there Idol indexes everything in staging and passes that to LSCS AT, there is a separate deployment in 7.2.1 for that step

Adam Stoller

Remember - this is with respect to 7.2.1

Yes you have 2 LSCS runtimes, one is the authoring environment and one is the prod env.

I need to re-visit this.

When you say I would have two LSCS runtimes ("preview", "production") - does that mean:

aware of anything that gets codified in the LSCS repository representing the "mode" of deployment.I'd love to find out that it does this and we can use the same directory, but if not - (which I suspect) I would welcome points to which section(s) of which manual(s) to read to find the setup information (I see some reference in Appendix J of the SP Dev Guide - but it's a little difficult to just search for since both "preview" and "development" are such general and oft-used terms through the manuals)

nipper

Typically the preview is on the TS server and production is not (but not required). That should make a number of your questions moot.

Good luck finding decent documentation.

Bowker

This is the diagram I used to convey this information to everyone here.

(See attachment, sorry I had to zip it. PDF too big for forum.)

Adam Stoller

Typically the preview is on the TS server and production is not (but not required). That should make a number of your questions moot.

Good luck finding decent documentation.

As per the conversation we had off-line (thanks again) - It's become a lot clearer to me (and hopefully accurate).

In my case - using 7.2.1 (not 7.3.1) - LSCS is still on a target server rather than on the TS server. Plus, with the intention of providing a full contextual preview environment.

This is the diagram I used to convey this information to everyone here

In the interest of "sharing the wealth" - I'm attaching my somewhat simplified - but hopefully accurate - diagram - which hopefully will be accessible to you folks http://dl.dropbox.com/u/21776252/ts_721_env.png (the size limitation for images on this site is rather frustrating - and I apologize in advance because I am likely to remove that file one of these days forgetting that it was posted publicly)

To further explain the diagram - and my understanding behind it:

jasonmcneil

In our typical 7.2.1 setups we have:

TS box:
TS, OD, SitePub, etc.
iw-preview (essentially LSDS on the TS box)
LSCS Authoring (which stores deployed content at say d:\LSCSAuth-Store\...) - and is connected to the same database which hosts TS/CommonServices, etc.

RT box:
LSDS
LSCS Runtime (which stores content on the runtime box at /LSCS-Store/... or equivalent) - and is connected to a production database server

During the deployment workflow, content is first deployed to 'development' which is the LSCSAuth running locally on the TS Box. When a user who clicks on a .page file in the TS workarea to preview the page, it's rendered by iw-preview, which has components we've built to connect to LSCSAuth (e.g. localhost), as defined in content.properties

When they are happy with their results (for example the proper articles are being listed in the "What's New" component), the workflow then progresses and performs the production deployment which sends the attached files to the Runtime LSDS and LSCS.

As your diagram indicates there is certainly the possiblity of having a separate LSDS/LSCS Runtime for Previewing purposes, though in 7.2.1 this is essentially duplicating what's available in iw-preview/LSCSAuth. However this can be very useful if you have reviewers who are not TS users (e.g. Executives who'd like to view content before it's published to production).

Adam Stoller

In our typical 7.2.1 setups we have:
[...]
As your diagram indicates there is certainly the possibility of having a separate LSDS/LSCS Runtime for Previewing purposes, though in 7.2.1 this is essentially duplicating what's available in iw-preview/LSCSAuth. However this can be very useful if you have reviewers who are not TS users (e.g. Executives who'd like to view content before it's published to production).

In our case:

They have application clustering in WebSphere and will actually be expecting LSCS to exist on all the App Servers accordingly - at least for "production" purposes.The "preview" instance of LSCS will probably only be on one server - but this means I have to be able to configure two instances of LSCS on the same server with two distinct store directories. I've barely had a chance to breathe today, let alone look through the manuals - but can someone confirm for me that this is possible?I have a feeling that this is going to be additional "fun" with the various OpenDeployNG/conf/lscs/*.xml configuration files - so if anyone's already dealt with this kind of thing (multiple LSCS instances on a single server with different store directories) - I'd appreciate any specific pointer you have on the configuration aspects.(I'm still trying to get fan-outs to work ... oh joy)