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

commit-deploy-plc deployment failing on new adding new definition

TeamsiteDev

Hi,

I am configuring the deployment for PLC workflow , using LSCS also. I am using standard commit-deploy-plc.xml available in OD_HOME/cond/lscs folder . There are two definitions in this deployment descriptor - MYDEFINITIONNAME & LiveSiteRuntimeDeployment . I want to add a new definition in this xml for deployment of static content on different webserver for which I have added a new definiton in the same file . Now if I am trying to execute this new definiton , deployment is failing :

<deployment transactional="yes" >
<execDeploymentTask useDefinition="MYDEFINITIONNAME" />
<execDeploymentTask useDefinition="LiveSiteRuntimeDeployment" />
<execDeploymentTask useDefinition="LiveSiteRuntimeWEBDeployment" />
</deployment>

If I comment the last <execDeploymentTask> , deployment runs fine but fails if the WEB definition is executed.

even though the definiton is present in XML I am getting error in the logs as :

---------------------------

ENG: End of deployment config file[C:\Interwoven\OpenDeployNG\conf\lscs\commit-deploy-plc_hcndazzthcndazzv.xml]

ENG: ***ERROR - Can not found definition LiveSiteRuntimeWEBDeployment specified in execDeploymentTask

ENG: ***ERROR - Failed to start deployment.
-------------------------------------------

Is adding new definition to commit-deploy-plc.xml not allowed ??

Thanks !

Regards,
Ankit

Find more posts tagged with

Comments

Adam Stoller

I think you want to do the modification in the LiveSite/OpenDeployWebRoot.xml rather than the lscs/*.xml config files - but I'm not 100% sure (haven't done that - someone here added another task to take care of deploying static web assets to the web server)

TeamsiteDev

Hi Ghoti,

Thanks for your reply. I am using LSCS deployment also so OpenDeployWebroot.xml is over-ridden by commit-deploy-plc.xml . The runtime deployment definition present in OpenDeployWebroot.xml is present in commit-deploy-plc.xml also and only this descriptor is invoked by the PLC deployment task so I have added new definition in this file only but its failing . Its a simple OD concept but I am getting error that definition does not exist in XML even though its there.

Regards,
Ankit

Rick Poulin

I am using LSCS deployment also so OpenDeployWebroot.xml is over-ridden by commit-deploy-plc.xml.

So in other words, you're on 7.3.x then? Specifying your environment details now and for future posts would be useful Smiley Happy

Its a simple OD concept but I am getting error that definition does not exist in XML even though its there.

The error you're seeing can be secondary if the definition was syntactically invalid and thus removed from the map of 'valid definitions' for your deployment. If you're lucky, you'll have an error higher up in your logs, but I'd double check the definition syntax either way.

dlsoderberg

I am actually working through the exact same issue with support right now. The problem is that the commit-deploy-plc.xml config is not read by OpenDeploy. It is parsed with a java class that builds deployment configs based on this file. So, while the original config looks fine, when it is parsed and translated into the new config file that is actually read by OD, there could be issues. My problem is centered around my new definition having job variables for the filelist area and filepath. Those variables don't end up being read and translated by OD correctly. There is a workaround that has been put in place for this in the past...they're just digging it up for me. Once I get the solution from them, I'll update this thread again.

Vendim Birbili

Please update the case if you have any response from the support. Im having the same issue on the 7.3.2. the commit-deploy-plc.xml doesn't like the third definition
<execDeploymentTask useDefinition="MYDEFINITIONNAME" >
<execDeploymentTask useDefinition="LiveSiteRuntimeDeployment1" >
<execDeploymentTask useDefinition="StaticLiveSiteRuntimeDeployment" >

Also it included its own numbers and replication farm( LiveSiteFarm1, LiveSiteRuntimeDeployment1

kaleemS

I am facing the same issue.
Did you get it resolved ?

Rick Poulin

The bulk of this conversation happened 9 months ago. You're better off starting your own post with details specific to your scenario. Also [thread=39499]read this[/thread].

Vendim Birbili

I am facing the same issue.
Did you get it resolved ?

We got a patch from HP that allows to have multiple exec definition on the commit-deploy-plc.xml.

kaleemS

Thank you vend2804
I have create the support ticket and requested for patch.

mishravik

We are using TeamSite 7.3.2 on Window 2008 R2 Enterprise.

We are trying to customize, PLC workflow to Deploy all content(static + .pages) to Application server (LiveSite) and static content to Web Server (OpenDeploy Receiver without DataDeploy).

Can someone help with sample commit-deploy-plc.xml configue file for above scenario for multiple execDeploymentTask and filtering for static files.

Rick Poulin

Everybody has different requirements, so it's a lot easier if you try this yourself first, and then post your config when you need help resolving errors.

mishravik

We are using TeamSite 7.3.2 on Window 2008 R2 Enterprise.

We have implemented Fan Out deployment to Application Server (LiveSite) using "Publish Live Site" workflow using LSCS.

We are need solution for addition deployment for static content to Web Server (OpenDeploy Receiver without DataDeploy). Was thinking that we can add another task to "commit-deploy-plc.xml" configue file.

Addition task should take care for deploying static files to Web server.

Currently, we need approach/solution for same, before implemented into our environment.

Adam Stoller

It's been a while since I looked at it, but I believe the OOTB PLC WFM provides for a deployment task of static web content to the web server -- take a closer look at all the different deployment tasks in that workflow and the various task properties and any associated configuration files.

Rick Poulin

I don't know offhand if fish is right -- I haven't looked at recent updates to the PLC -- but I've always done it the way you're proposing. That said, I'm not entirely sure what you're looking for. As I've already said, nobody here is going to build the solution for you. Try something first. Doesn't matter if it works or not, actually put some sweat into it and then we can help you get it right.