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 Deployment

GRD

Does anyone know how to prevent deployment to LSCS for a given branch (7.2.1)... it looks like I can edit the bean, or the deployment script, but I'm thinking there has got to be an easier way? Perhaps I'm just missing it in the developer guide.

For the given branch, I want the LiveSite deployment to LSDS, but I don't want the LSCS deployment.

-Greg

Find more posts tagged with

Comments

AlexC

LSCS is an integral part of the product, why would you want to prevent the deployment?

BopReport.RPTDESIGN

Frederik

euhm, we can hardly call LSCS an integral part of the solution, if it comes with an additional opt-in license & cost? Also, apart from cost, I think it's an architectural matter... for some websites, you just don't need the additional complexity of LSCS.

I think the question is highly relevant!

AlexC

I can't comment on the sales/licensing question, but from the development point of view LSCS is used in both preview and runtime for targeting and content retrieval (and IDOL based search of content). If you never itend to use it then you can look into modifying the PLC workflows, but it is not something I will recommend personally (i.e. caveat emptor).

srosewall

If you never itend to use it then you can look into modifying the PLC workflows, but it is not something I will recommend personally (i.e. caveat emptor).

If you never intend to use it, you can make sure it's disabled and the PLC wont bother trying:
iw-home\local\config\lib\content_center\livesite_customer_src\etc\conf\livesite_customer\content.properties
# Whether to connect to LSCS
#
lscs.enabled=true|false

I think the question is if you want to partially use it for specific projects / websites / branches, but not for all.
That sounds like a reasonable question.

Regards,

RonaldV

Alex,

what you (and your co-workers) should start to understand, 4 yrs after being bought by Iwov, is that there is a large community that happily uses teamsite without all the LiveSite stuff (create a dcr, deploy to webserver where some engine transforms it to html).

And there is a second large group that uses livesite-pages without the bloat of targeting/taxonomies/.....

For these administrators every un-used dependency is just another source for failure that one day will show it ugly head.

So apart from licensing there is a very good reason to allow installing teamsite without having to supply database-details.

GRD

LSCS is an integral part of the product, why would you want to prevent the deployment?

In the design we are separating content from sites at the branch level, and then delivering that content dynamically via LSCS. In the branch containing the sites, we do not want the additional overhead of the LSCS deployments as nothing from that branch will ever be queried via LSCS.

No plans for targeting.

-Greg

GRD

Alex, any comment on this?

-Greg

AlexC

The only thing I can think of is editing content.properties files and setting lscs.enable=false Hopefully that will prevent all LSCS deployment and disable targeting.

GRD

The only thing I can think of is editing content.properties files and setting lscs.enable=false Hopefully that will prevent all LSCS deployment and disable targeting.

That works to disable LSCS all together. However, I am asking about disabling the extra overhead of LSCS for certain branches.

-Greg