How to deploy generated HTML files with OOTB PLC Workflow

chandra1987

Hi All,

Is anyone know how to do below two tasks?

1. We are using sitepublisher to create .page files and want to convert these .page files as .html files to deploy to webservers(As we are not using LiveSite Runtime) through OOTB PLC workflow. As we are using only .html files we do not want to deploy any dcr's,layout files,.page files, default.site , default.sitemap, cache files to the target webservers. For this I have included some PatternWrapper's in teamsite-resource-config.xml file located in $JBOSS-HOME/default/deploy/iw-cc.war/WEB-INF/conf/livesite/resources/teamsite-resource-config.xml file (please find attached the same) from line number 296 to 325. Even thorugh I added these patterns still PLC workflow is deploying all the files to target. Please let me know if some one knows how to restrict these files.

2. We have enabled Generate HTML task in PLC and it is generating .html and attaching the same to job (I am able to see generated html atatched to job in prod review task). Even though it is atatched to job it is not getting deployed to target webserver. Please let me know if someone knows how can i deploy generated html file to target system.

Thanks In advance.

Find more posts tagged with

Comments

interDev

You dont need PLC workflow in this case as you not using runtime environment. PLC does lots of things which are specific to Runtime environment.
Writing down a small custom Workflow will be a better approach (Plug in Generate HTML Task from PLC workflow).

sheikh1

I agree with interDEV, my thoughts are at same level.

Although if you just want to juse PLC workflow you can take out the add dependencies task from the workflow and the value which decides the target location is mentioned at [teamsite_home]/local/config/lib/content_center/livesite_customer_src/etc/conf/livesite_customer/opendeploy.properties


# the LiveSite Runtime installation directory on the production host.
# this would translate into: /runtime/web
opendeploy.runtimeHome=/usr/Interwoven/LiveSiteDisplayServices/runtime/web

chandra1987

Thanks for replies.

I agree with interDev and we have created already a custom workflow to do this but autonomy consultant has reviewed the solution we provided to customer and they want use only OOTB PLC workflow to do this.

sheikh, I have configured this target path and there are no issues with target paths.The only issue is we want publish only generated html's to target.

Rick Poulin

I agree with interDev and we have created already a custom workflow to do this but autonomy consultant has reviewed the solution we provided to customer and they want use only OOTB PLC workflow to do this.

This is a rare occasion where I'll agree with the Autonomy guy. There's really no reason to go custom on this when everything is already done for you.

1. [...]Even thorugh I added these patterns still PLC workflow is deploying all the files to target. Please let me know if some one knows how to restrict these files.

Even if this did work, it's the wrong way to make that change. In any case, forget that. The easiest way is just to edit odhome/conf/LiveSite/OpenDeployWebRoot.xml and put in deployment filters. Don't forget to backup your original.

2. [...] Even though it is atatched to job it is not getting deployed to target webserver. Please let me know if someone knows how can i deploy generated html file to target system.

This almost certainly means that you put your "Generate HTML" task *after* the "Attach Deployment Targets" task. The latter should come first.

Adam Stoller

This almost certainly means that you put your "Generate HTML" task *after* the "Attach Deployment Targets" task. The latter should come first.

I think you meant to say "*before*" not "*after*" (which your last sentence would seem to imply) - as I'm pretty sure the Attach Dependencies task does come before the Generate HTML task in the OOTB PLC.

chandra1987

This is a rare occasion where I'll agree with the Autonomy guy. There's really no reason to go custom on this when everything is already done for you.

I am fine going with OOTB PLC but the thing is I want to publish the on the fly generated html files to target systems but PLC is detaching the generated html's from Production Deployment task.

Rick Poulin

as I'm pretty sure the Attach Dependencies task does come before the Generate HTML task in the OOTB PLC.

Agreed, but I said "Attach Deployment Targets", not "Attach Dependencies" Smiley Tongue

I am fine going with OOTB PLC but the thing is I want to publish the on the fly generated html files to target systems but PLC is detaching the generated html's from Production Deployment task.

Crank up the debug logging and figure out which task is doing the detaching and why. This is not standard/ootb behaviour.

Adam Stoller

Agreed, but I said "Attach Deployment Targets", not "Attach Dependencies"

Doh! I have to stop reading what I think I'm seeing and start reading what's actually written - sorry about that; given the source I should definitely have re-read it carefully a few more times before responding ... (merry xmas)

chandra1987

Crank up the debug logging and figure out which task is doing the detaching and why. This is not standard/ootb behaviour.

Thanks all for your replies.

I do not know how to enable logging for this workflow, could you please help me to do that?

However I have added one user task after prod deployment task and verified the attached files and the html files are still atatched to job.So generated html's are detached from job as I said earlier but some where in the java code or in configurations they are filtering those files.

To my surprise if I attach any flat html file the workflow is deploying those to target systems.

Rick Poulin

However I have added one user task after prod deployment task and verified the attached files and the html files are still atatched to job.So generated html's are detached from job as I said earlier but some where in the java code or in configurations they are filtering those files.

Careful with your wording. You're saying your files are actually NOT detached but they ARE being filtered out of the deployment -- there's a difference.

As I said, make sure your "Generate HTML" task appears before the "Attach Deployment Targets" task in your workflow. If that's the case, use that new task of yours to check the job variables after the deployment step. You should have a variable called "deployable.files". Confirm that the JSON text value of that variable contains the HTML files you're looking to deploy. If the files are not in the list, then your tasks are in the wrong order. If however the files ARE in the list, then the problem is further downstream -- perhaps in your customer-teamsite-resource-config.xml filters or in your OpenDeployWebRoot.xml filters.

chandra1987

Moved "Generate HTML" task before the "Attach Deployment Targets" task in the model and tested the deployments, it worked Smiley Happy

Thanks a lot rpoulin.