Customized PLC | LSDS deployment error

Ashish_Sangal

Hi,

We are using TS-7.4.0 and OD - 7.3.2 on Linux box.

I have customized the PLC to add new node "qa" in between dev and prod.

I have followed all the steps mentioned in SiteDev guide.

Also, i have updated "Production Deployment" task in .ipm file and change the value of

"TargetNodes" to CONFIGURABLE(TargetNodes) from "production" so that it will deploy to qa node as well.

I am able to achieve LSCS deployment but content is not getting deployed on LSDS.

I am getting this warn in content_center.log

 "WARN com.interwoven.livesite.opendeploy.impl.OpenDeploymentServiceAdapter () - no target for /default/main/WJDemo/WORKAREA/WJWA"

PFA customer-teamsite-resource-config.xml .

As per my understanding, for LSDS deployment we have to update "customer-teamsite-resource-config.xml " file.

Please, let me know what step i'm missing for LSDS deployment.

Find more posts tagged with

Comments

Rick Poulin

The value of the TargetName property should be LiveSiteRuntime, not LiveSiteQARuntime. This value is used to match against the value recorded in the default.site file in the workarea.

Ashish_Sangal

Thanks rpoulin.

You save my day Smiley Happy

I saw one more issue while deploying content on LSCS on qa server, its not updated the project name.

For eg.

On dev server --

project name starts with //xyz.com/

while on QA server it starts with //abc.com

So, ideally when i deploy any content from dev to qa, project name should change accordingly but its not happening.

On QA server, its saving the project as //xyz.com/default/main/WJDemo not as //abc.com/default/main/WJDemo

Any idea, why this is happening and what will be the solution for this?

Rick Poulin

It works this way to specifically avoid what you're doing. If content comes from two different places, it'll keep them separate for you. Having two sources for the same runtime content is a terrible idea.

If you have content in dev that you want to promote to QA (which is also a terrible idea), then have your dev workflow push to the QA Teamsite box, merge the content there first, and then deploy it from QA TS to QA LS.

Or, if you still want to merge them in LSCS, assign specific project names to those branches in lscs-authoring.xml. Not recommended.

Ashish_Sangal

Hi rpoulin,

Thanks for the information. I will keep it this way only.

I am facing one more issue, while deploying page & site to Runtime, its getting deployed on LSCS and LSDS both but under workflow tab im getting "Resolve Production Deployment Error".

Any idea about this?

Rick Poulin

You should find a less-than-useful error message in the task comments (it'll probably say deployment failed) in which case you'll have to inspect the server.log and/or OD logs to find the cause.

Ashish_Sangal

Hey rpouling,

Files (including pages) are getting deployed but in case of pages, im getting this error.

I didn't get much from the server.log and odbase.log.

Let me tell you the scenario-

My dev and prod runtime are installed on same server but qa is on another server.

When i select production, everything works fine and files got deployed without any error but in case of qa this is happening.

Also, only for pages(files got deployed) it is happening other files are getting deployed fine.

Hope, this will clear the setup achitecture.

HTML5 Charts -- Fill the rest of year with 0s X-Axis is category axis__cwong.rptdesign

Ashish_Sangal

I got some error in lscs.log of qa LSCS.

PFA the log. Its saying -

IdolSearchDaoRuntimeImpl - handleDbSync(): failed to sync DB.

Rick Poulin

Seems to me like your target folder for the QA LSCS is not the same in your lscs-authoring.xml and your runtime-side lscs-conf.properties.

Caused by: java.io.FileNotFoundException: /mnt/SATA/LSCSRT-Store/625/8af/6258afde9c71cb64eda08d7fed38965e/idx (No such file or directory)

Ashish_Sangal

Thanks a lot rpoulin.

Updating "destinationArea" lscs-authoring.xml resolves the issue. Smiley Happy