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 Buld deployment Script

Vendim Birbili

TS 7.3.2,

Windows 2008 R2 64 bit.

Im trying to Automate the Content Sync between 2 environments (Prod and UAT) by scheduling a deployment that would push the content from production to UAT Teamsite and then from there to Runtime. As far as the Livesite deployment that would work fine using the OD script. Im wondering about the LSCS deployment since one of the sites is using LSCS. Is there a way to do that with OD script or ot has to go with PLC/LSCS Workflow? anyone has done that or something similiar. Any guidance would be helpful

thanks in advance.

Find more posts tagged with

Comments

nipper

There is a script available to help, LiveSiteCSAuth/authoring/bin/startdeploy.bat

Vendim Birbili

Thanks for the fast reply Nipper. I see on another post that you have done this before using the Manifest file to deploy.

startdeploy.sh -StartDeploy_OverrideManifest LSCSmanifest.xml -StartDeploy_DeploymentMode stage

I am stuck on generating the manifest file as part of the script. Do I need to write a perl script to do that or the open deploy will generate that for me by doing something with configurarion. Sorry I never done this before. I done manually creating a file list and pointing the open deploy to do that but never through the LCS deployment.

thanks in advance

nipper

Depends on your approach.

I always use filelist deployments that needs a manifest and you need ot generate it.

You can do ither types like edition based deployments and don't need it

Rick Poulin

Used in this manner, you'd have to generate the file list yourself.

However, if memory serves, that utility could also operate in "areadiff" mode, meaning that it could generate a filelist based on the comparison between two areas.

UC49_test.rptdesign

uc49.xlsx

Vendim Birbili

can you provide a sample of generating a manifest file or point me to some documentation? I really appreciate your help.

thanks

Vendim Birbili

Will the areadiff work for larger deployment? As i mention on I will compare Prod with Stage Workareas 9 around 80,000 dcrs) and deploy to teamsite then to LSCS/LSDS.

thanks

Rick Poulin

The typical approach of using the areadiff option is to compare the current workarea against the INITIAL edition. The result is basically saying "deploy everything" without really having to compare anything.

The other thread you found where nipper and ghoti were discussing this script should also have a sample manifest syntax, if you choose to go the route of generating a manifest yourself. EDIT: Link

nipper

vend2804 wrote:
can you provide a sample of generating a manifest file or point me to some documentation? I really appreciate your help.
thanks

<?xml version="1.0" encoding="UTF-8"?>
<deployment>
<context area="/default/main/branch/WORKAREA/shared"/>
<filelist>
<file areaRelativePath="templatedata/Type/config/data/january.xml
otherAttributes="true"/>

</filelist>

</deployment>

Vendim Birbili

Thanks Nipper for the sample of the manifest file. Again my question is that do I have to generate this file using some backend script or the OD configuration would generate that? I know that the PLC handle that internally , but im not sure how to generate this file as portion of this content Sync.

Any hint would be appreciated.

nipper

Answered that several posts ago:

I always use filelist deployments that needs a manifest and you need to generate it.