7.2.1 PLC LSCS deployment questions...

How are content.properties and lscs-authoring used by PLC ?

I am setting up a second deployment to LSCS, (which will use the localhost:8080 LSCS) and then the production deployment.

I have an entry for <preview> and <production> in lscs-authoring as well as another entry for the next deployment but I am failing. It seems to use localhost as the preview deployment and 1876 for the port (which is not running LSCS). It should be localhost:8080 but that is not being picked up.

Tips/pointers/RTFMs greatly appreciated

Andy

Find more posts tagged with

Comments

Rick Poulin

How are content.properties and lscs-authoring used by PLC ?

The PLC doesn't use content.properties at all. That's only used to tell SitePub page rendering where to find LSCS. lscs-authoring.xml (plus deployment-source.properties in the same folder) are the files that configure the LSCS deployment.

I am setting up a second deployment to LSCS, (which will use the localhost:8080 LSCS) and then the production deployment.

Can you do that in 7.2.1? I thought that the bug with this was fixed only in 7.3.1? (bug being that the PLC would **** on you if you tried using a target node named other than "development" or "production")

I have an entry for <preview> and <production> in lscs-authoring as well as another entry for the next deployment but I am failing. It seems to use localhost as the preview deployment and 1876 for the port (which is not running LSCS). It should be localhost:8080 but that is not being picked up.

Here's generally how you'd build this from scratch (in 7.3.x).. I have no idea why yours would find the right host but the wrong port.

in customer-teamsite-resource-config.xml, find the DeploymentTargetMap bean and add a new entry key (copy <entry key="production"> for instance)
In your PLC's production deployment task, make the TargetNodes a variable (or create a whole new copy of the workflow) such that TargetNodes uses the name of your new entry from the bean config. Do NOT touch the deployment/preview deployment if you want it to keep deploying to localhost:8080 at this part of the job
in lscs-authoring.xml, add a new <runtime mode="entry-name"> where entry-name matches the TargetNode in workflow and the bean entry key

Why I'm confused is this. I know that in 7.2.1 unpatched, the LSCS part of the deployment will croak if TargetNode isn't deployment|production. Secondly, I didn't think any of this worked with the "old" lscs-authoring format of <preview> and <production>, but rather that the <runtime mode="production"> style was required.

I'm working on 7.2.0 right now, and we've had to build an unpretty hack to get around the bug until we upgrade to 7.3.

Adam Stoller

If this is the project I think it is - he's on 7.2.1 P1 (not vanilla - precisely because of the bug in the vanilla version)

nipper

in lscs-authoring.xml, add a new <runtime mode="entry-name"> where entry-name matches the TargetNode in workflow and the bean entry key

Yes, this is 721 with the multi-deployment target patcv installed.

So are you saying where I have

<preview lscsContext="lscs" lscsRuntimeTransport="http" lscsRuntimeHostname="localhost" lscsRuntimePort="8080" destinationArea="/usr/LSCS-Store" destinationNode="localhost"/>
<production lscsContext="lscs" lscsRuntimeTransport="http" lscsRuntimeHostname="localhost" lscsRuntimePort="1876" destinationArea="/usr/LSCS-Store" destinationNode="LSCSRuntime"/>

I add something like this:
<runtime mode="Staging" lscsContext="lscs" lscsRuntimeTransport="http" lscsRuntimeHostname="localhost" lscsRuntimePort="1876" destinationArea="/usr/LSCS-Store" destinationNode="NewLSCS"/>

?

Rick Poulin

So are you saying where I have [..] I add something like this [..]

I'm saying that's what you would add in 7.3.1. I have no idea how you're meant to add a node to lscs-authoring.xml in this crossover flavour you've got. I'd say create your new bean entry and update your workflow, and then just keep updating lscs-authoring.xml with different things until you find the one that works Smiley Happy

nipper

I'm saying that's what you would add in 7.3.1. I have no idea how you're meant to add a node to lscs-authoring.xml in this crossover flavour you've got. I'd say create your new bean entry and update your workflow, and then just keep updating lscs-authoring.xml with different things until you find the one that works

Got it. I see the syntax in 721 is different. d**n.

ReferSheet2fromSheet1_error_no_forumlas.xlsx