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; } } }

LSCS 7.3.1 trivia

nipper

Our team had a long discussion with engineering on LSCS. Some questions have been answered. Some answers were quite boneheaded.

1. LSCS RT is not included with LSCS Authoring - been discussed before and confirmed. The LSCS Authoring uses the local /iwmnt content for LSCS, projects in LSCS Authoring basically do not exist anymore.

2. Any content submitted to STAGING is automatically indexed by IDOL. That content is available to Authoring.

3. The preview deploy really does not do anything. If you want to preview, the content MUST be submitted to STAGING.

4. To get around this, you need a preview WF that deploys to a LSCSRT instance.

So now, in 7.3.1 to preview LSCS, it has to be in the STAGING area (yuck) or you have to have a second install of LSCSRT.

Find more posts tagged with

Comments

Bowker

Thanks for the update. In our environment we actually have four separate LSCS - RT environments.

We have a Testing environment for TeamSite which deploys to two separate environments. one simulates "user acceptance testing" and the other simulates production. Once our "stuff" is ready, we'll move it to the the production version of TS which then has two separate environments it deploys to - a real "user acceptance testing" area and production.

Potentially we have three totally separate testing regions for different purposes. It comes in very handy for testing deployments, workflows and Java modules in the customer area.

Doesn't everyone do that (I ask rhetorically, tongue in cheek.) Although that is how our environment is setup.

GRD

Andy, please help me here. I've been working with LSCS from the beginning (you can count the arrows in my back), and while I think indexing the store directly is a great idea, I don't understand the design logic if it's not carried through to the runtimes?

Do our queries now look different in authoring vs. runtime? Does this lock us into using lscsclient.jar?

Is there any documentation on this?

-Greg

nipper

Andy, please help me here. I've been working with LSCS from the beginning (you can count the arrows in my back), and while I think indexing the store directly is a great idea, I don't understand the design logic if it's not carried through to the runtimes?

I agree that the indexing the backingstore itself with IDOL is a good way to go, it really is a different approach to the way things normally have run with TS. The fact that it has to be in STAGING for authoring to work pretty much prevents you from using that to preview.

Do our queries now look different in authoring vs. runtime? Does this lock us into using lscsclient.jar?

I do no think the queries are different, just that authoring is now a subset of the RT functionality. This all started when the projects were fine in RT but not available in authoring.

No clue about lscsclient

Is there any documentation on this?

-Greg

Not that I know of.