Usage of Opendeploy Filters

cute_guy

We have a workarea setup in which we have website content ( images, flash, jsp,jpeg,gif), generated HTML files and also the templatedata folder.

Our client's requirement is to deploy only files with specific extensions like .jsp,.csv,.html.js,.jpeg and templatedata should not be deployed to target webserver.

We have submitted the entire content in workarea to staging and create a edition and deploy it to target webserver.

We have used the includePattern filters to deploy specific files to target webserver and since the [highlight]templatedata is part of the edition it is getting deployed [/highlight]to the target webserver.

Is there any way restrict templatedata?

- We know that inclusion filter and exclusion filter cannot be used together in the source definition.

- Workaround is to make templatedata private and avoid it getting submitted to staging and becoming part of the edition, but a large amount of data has already been submitted to staging it is difficult to goback to first step and make the templatedata folder private.

- create dnr script to remove the templatedata folder after the deployment has occured in the target webserver, since there are 4 target server this dnr script has to be placed in all the 4 server which is a tiresome job.


Is there a simple way to restrict the templatedata folder from getting deployed to target webserver with minimum effort involved.

Thanks and Regards,
G
-----------------------------------
TS 6.5, Solaris 8, OD 6.0.1

Adam Stoller

We have a workarea setup in which we have website content ( images, flash, jsp,jpeg,gif), generated HTML files and also the templatedata folder. Our client's requirement is to deploy only files with specific extensions like .jsp,.csv,.html.js,.jpeg and templatedata should not be deployed to target webserver. We have submitted the entire content in workarea to staging and create a edition and deploy it to target webserver. We have used the includePattern filters to deploy specific files to target webserver and since the [highlight]templatedata is part of the edition it is getting deployed [/highlight]to the target webserver. Is there any way restrict templatedata? - We know that inclusion filter and exclusion filter cannot be used together in the source definition. - Workaround is to make templatedata private and avoid it getting submitted to staging and becoming part of the edition, but a large amount of data has already been submitted to staging it is difficult to goback to first step and make the templatedata folder private. - create dnr script to remove the templatedata folder after the deployment has occured in the target webserver, since there are 4 target server this dnr script has to be placed in all the 4 server which is a tiresome job. Is there a simple way to restrict the templatedata folder from getting deployed to target webserver with minimum effort involved. Thanks and Regards, G ----------------------------------- TS 6.5, Solaris 8, OD 6.0.1

Are you only deploying entire editions (dir-diff) or are you deploying a filelist?

If the latter - it should be trivial to exclude templatedata files from getting into the filelist used for the deployment (I've done it many times)

If the former, might it be easier to develop the filters as a list of exclusions, rather than as a list of inclusions? And make sure that your filters are applied on both the source and target side of the deployment.

Making templatedata private is, IMO, the wrong solution.

CrosstabAlternatingRow.rptdesign