Couldnt find where the dependent files (assets) are deployed

Hi ,

I am in TS 7.3.2 , Solaris 5.10

I am currently looking in to the one the PLC workflow that is cutomized to deploy the DCR's to the target LSCS .

I could able to locate the LSCS target from the lscs-authoring.xml , where the DCR are deployed , but I could not figure out where actually the dependent files (images,pdf) are deployed .

I looked at the opendeploy.properties file and that location doesnt have the content. So I started looking in to the LiveSite logs under the "Iw-home/OpenDeploNG/log/LiveSite", there I could findthe deployment details , such as Source details (WORKAREA from where the deployment was initiated) , filelist (the files that are attached to the deployment ) and Target as "livesite-projectName" , and there is an entry exactly inside the livesite-database.xml

<database name="livesite-projectName"

.... />

and after this I am lost I could not get any leads there after .. Could some one point out / suggest the correct steps .

Thanks

Hashaan

Find more posts tagged with

Comments

Rick Poulin

If you have an uncustomized deployment process and LSCS deployments are turned on, then in 7.3.2 all files are deployed to both LSCS and LSDS. The location for LSDS is the webroot specified in opendeploy.properties. Relevant logs will be in OpenDeployNG/log/lscs, not LiveSite. Note that the LSDS portion won't even start if the LSCS import fails.

Beyond that, you're going to have to provide more information if you still need help tracing things.

Hashaan

Thank rpoulin, you are correct Smiley Happy I looked in to the said : OpenDeployNG/log/lscs location and I can see the target info and I could see the deployed assests.

I have one more query, for evey LSCS deployment all the staic dependent assests tagged in the DCR are getting deployed to runtime env. Now, how would my webserver point / interpret these image assests as every LSCS deployment creates a new contextID (for eg : 71824025ec4322bodc64e85b30af75)..?

Rick Poulin

You do not want to point your webserver at the LSCSRT-Store. You want to point it at your LSDS runtime webroot, as specified in your opendeploy.properties file. The folder structure in here would effectively mimic the folder structure in your workarea.

Note that, since the LSDS webroot contains more than just static assets, it's common practice to split up this part of the deployment such that your pages would go to LSDS and your static assets would go to a /var/www/html or equivalent. You would do this by modifying the lscs/commit-deploy-plc.xml. However, I'd suggest you understand the basics before attempting this type of customization.