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

Vendim Birbili

hi,
we are using the teamsite 7.3.2 and we Im trying to use a split architecture for deployment( static files on separate drive then runtime). in the 7.2.1 we used to do that on the opendeploywebroot.xml but on this version I heard we have to do on the commit-deploy-plc.xml. any one have any example to provide?

thanks in advance

Find more posts tagged with

Comments

Rick Poulin

If you've already done it in 7.2, the bottom portion of commit-deploy-plc should look pretty familiar. The only difference is you have to keep the PLC's additional variables in there, but for your purposes it should be no harder than adding an additional <target> as you would have in opendeploywebroot.xml.

Vendim Birbili

I tried to modified the bottom portion but I was getting problems.
Attached is the opnedeploywebroot.xml file that is working on 7.2.1
I also attached the comit-deploy-plc_new.xml that I tried to modify but is not working.
do I need to modify that file only on the Od/conf/lscs or under the authoring folder as well?

Rick Poulin

It would help if you specified what problems you were running into, and providing logs where appropriate... but your definition looks ok, except for the <exceptPath> nodes -- there's no such thing.

You actually want to change this file under 'authoring'. In 7.3.x, the PLC uses the authoring copy to generate a final conf under OD/conf/lscs (with some random number for uniqueness). The 'template', so to speak, is the copy in LSCSAuth.

Vendim Birbili

Thanks Rick,
I Removed the ExcepPath but for somehow the deployment keep going under the same path (E:\Interwoven\LiveSiteDisplayServices\runtime\web) even though I have different targets.
Any Idea?

Thanks

Vendim Birbili

I did modify the commit-deploy-plc.xml file but still is not doing anything. I checked the Customer-teamsite-resource-config.xml and the nodes are defined as the attached. Someone mention that the target directory shouldnt be pointed there should be a targetArea variable?
Any insight

Rick Poulin

I did modify the commit-deploy-plc.xml file but still is not doing anything. I checked the Customer-teamsite-resource-config.xml and the nodes are defined as the attached. Someone mention that the target directory shouldnt be pointed there should be a targetArea variable?
Any insight

This makes no difference, given the ODConf you shared earlier.

Make sure you changes are actually getting picked up, namely that your new <deployment> actually gets fired (review OD logs). I get the feeling you're still not changing this file in the right place (which is the LSCSAuth copy).

Vendim Birbili

HI Rick ,
I do change the file on the path below:
E:\Interwoven\LiveSiteCSAuth\authoring\etc\deployment\config

going through the logs the deployment executes fine just that the target area always comes as E:\Interwoven\LiveSiteDisplayServices\runtime\web

thanks

Rick Poulin

going through the logs the deployment executes fine just that the target area always comes as E:\Interwoven\LiveSiteDisplayServices\runtime\web

So by "executes fine" you mean that OD is actually correctly generating separate micro deploy logs for "LiveSiteRuntimeDeployment-Dynamic" and "LiveSiteRuntimeDeployment-Static" ? Because the way you have it configured, it's impossible for the -Static one to be deploying to anything but E:\web\www\lsds.

Vendim Birbili

actually I do see that on the minideployment is generating a file name like this
src.commit-deploy-plc_hfbiou2phfbiou2qd0765deeebcf13fd7537af965c6c0e7e.LiveSiteRuntimeDeployment1.severnameXXXX.to.ls-qa.log.

So does that mean that is not looking at the correct file?
I see on the name this "LiveSiteRuntimeDeployment1"

Vendim Birbili

looking at the logs on OD seems like the deployment are using the file
E:\Interwoven\OpenDeployNG\conf\lscs\commit-deploy-plc.xml . Is that correct or Im wrong? if so is that where I do the split deployment?

thanks

Rick Poulin

So does that mean that is not looking at the correct file?
I see on the name this "LiveSiteRuntimeDeployment1"

looking at the logs on OD seems like the deployment are using the file
E:\Interwoven\OpenDeployNG\conf\lscs\commit-deploy-plc.xml . Is that correct or Im wrong? if so is that where I do the split deployment?

I guess you missed what I said earlier in the thread..

The PLC uses the commit-deploy-plc.xml under LiveSiteCSAuth as its template to *generate* the copy/copies under OpenDeployNG. I think there's a subtle difference here between 7.3.1 and 7.3.2, and I don't have a build handy... so unless someone can chime in with the specifics, you'll have to try changing different files and retrying and looking at logs until you can get OD to see you changes (and thus execute your two deployments).

Basically what you're looking for is instead of having one microdeploy log called LiveSiteRuntimeDeployment1, you should have two (one for -Static and one for -Dynamic).

-- side note (something else to try) --
The fact that your log file has a '1' at the end of the deployment name makes me think something else is being generated/rewritten here.. As in I have a vague memory about the PLC maybe creating a whole new <deployment> node and rewriting the whole <exec> piece on you... which means instead of defining separate definitions, you could try defining separate targets within the same deployment.
/sorry, kinda wish I had a server to play with to give concrete meaning to my ramblings

Vendim Birbili

I guess you missed what I said earlier in the thread..

The PLC uses the commit-deploy-plc.xml under LiveSiteCSAuth as its template to *generate* the copy/copies under OpenDeployNG. I think there's a subtle difference here between 7.3.1 and 7.3.2, and I don't have a build handy... so unless someone can chime in with the specifics, you'll have to try changing different files and retrying and looking at logs until you can get OD to see you changes (and thus execute your two deployments).

Basically what you're looking for is instead of having one microdeploy log called LiveSiteRuntimeDeployment1, you should have two (one for -Static and one for -Dynamic).

-- side note (something else to try) --
The fact that your log file has a '1' at the end of the deployment name makes me think something else is being generated/rewritten here.. As in I have a vague memory about the PLC maybe creating a whole new <deployment> node and rewriting the whole <exec> piece on you... which means instead of defining separate definitions, you could try defining separate targets within the same deployment.
/sorry, kinda wish I had a server to play with to give concrete meaning to my ramblings

You are correct,
looking at the logs it rewrites( created it self a whole new deployment). how I can separate the targets withing same deployment?
I really appreciate your help. I keep trying changing files but i cannot get it working.

Rick Poulin

The OpenDeployWebRoot.xml has a good example, along the lines of this:

[HTML]

[/HTML]

What you're adding is the second [filelist] element.

The first [filelist] doesn't specify a [targetRules], so it'll use the definition's global [target]. The second one specifies a [targetRules] that points it at a different path entirely. You can still do your includes/excludes filtering within each [pathSpecification] to get only the right files to each target, or you can use entirely different filelists for each. The latter would require customization of the deployment task's Java code though.

Vendim Birbili

[/HTML]What you're adding is the second [filelist] element.The first [filelist] doesn't specify a [targetRules], so it'll use the definition's global [target]. The second one specifies a [targetRules] that points it at a different path entirely. You can still do your includes/excludes filtering within each [pathSpecification] to get only the right files to each target, or you can use entirely different filelists for each. The latter would require customization of the deployment task's Java code though.
The OpenDeployWebRoot.xml has a good example, along the lines of this:

[HTML]

This really helped Rick. I did modify the commit-deploy-plc.xml under the /lscs and I was able to run the split deployment on the same server ( assets now are going to the e:\web\www\lsds). I will work on applying the same logic for running the same deployment deploying the assets on the web server and the dynamic data to livesite server .
do you know if the this version support the od_Subst_. On the workflow we do specify the TargetNodes and the Webserver(using odSubst_targetWebNode =servername)
thanks

Rick Poulin

do you know if the this version support the od_Subst_. On the workflow we do specify the TargetNodes and the Webserver(using odSubst_targetWebNode =servername)

I don't remember offhand, but it should be fairly straightforward for you to test that.

I can say that in 7.2.x, the LSCS portion of the deployment did *not* receive variables supplied by the task via odSubst_, but I can only hope that they've fixed that in 7.3. Worst case, you can subclass and override the LSCSDeploymentServiceAdapter to inject parameters into the deployment object, but that's a heavy-handed approach and I'd recommend looking for alternatives first.

nipper

do you know if the this version support the od_Subst_. On the workflow we do specify the TargetNodes and the Webserver(using odSubst_targetWebNode =servername)
thanks

You can set the deployment logging to verbose mode and you can see the variables that are set.

Vendim Birbili

What I can see is that commit-deploy-plc.xml doesn't like when you pass the parameters as

nodeRef useNode="$targetNode^"

the only way it works is with
nodeRef useNode="$destinationNode"

Vendim Birbili

I don't remember offhand, but it should be fairly straightforward for you to test that.

I can say that in 7.2.x, the LSCS portion of the deployment did *not* receive variables supplied by the task via odSubst_, but I can only hope that they've fixed that in 7.3. Worst case, you can subclass and override the LSCSDeploymentServiceAdapter to inject parameters into the deployment object, but that's a heavy-handed approach and I'd recommend looking for alternatives first.

HI Rick,
Actually the variable that Im passing is for LSDS. the LSCS deployments are fine but in order to deploy the static content to the web servers( on prod) on the workflows we are using odSubst_(Servername). Since on the 7.3.2 lscs and lsds are using the same file commit-deploy-plc.xml I was wondering how the variable will be pass. What I see from other posts seems like there is a problem with OD. you cannot have more then 2 definition on this file (Od doesn't read that file).
I don't know if anyone have come around modifying the commit-deploy-plc.xml on the 7.3.2 to have 3 definition :
MYDefinition ( LSCS default)
LiveSiteRuntimeDEployment
StaticLiveSiteRuntimeDeploymnent

Thanks