target side filters

NigelF

<p>I have been trying to create a deployment with filtering on the target. I can get it to work with filtering on the server, but it doesn't behave as it would if I'd put the filtering on the target. Below is my XML, and perhapse someone can tell me what I am doing wrong. Thanks. </p>

<?xml version="1.0" encoding="ISO-8859-1" ?>
<deploymentConfiguration >
<logRules maxBytes="32Mb" level="verbose" >
</logRules>
<localNode host="C75" />
<replicationFarmSet >
<replicationFarm name="SCC" >
<nodeRef useNode="sCCPS1" >
</nodeRef>
</replicationFarm>
</replicationFarmSet>
<definition name="SCP1" >
<source>
<sourceFilesystem area="y:/default/main/www/Production/EDITION" >
<pathSpecification >
<path name=".">
</path>
</pathSpecification>
</sourceFilesystem>
</source>
<target useReplicationFarm="SCC" >
<comparisonRules dateDifferent="yes" revert="no" ignoreAcls="no" ignoreModes="no" ignoreUser="no" ignoreGroup="no" />
<transferRules doDeletes="yes" rmReadOnly="yes" svrTryCount="10" svrTryInterval="60" />
<permissionRules changeAccess="" setAccess="" />
<targetFilesystem area="d:/www/www"/>
<filters>
<excludePath subPath="logfiles" />
<excludePattern regex="web.config$" />
</filters>
</target>
</definition>
<deployment transactional="yes" >
<execDeploymentTask useDefinition="SCP1" downRev="" >
</execDeploymentTask>
</deployment>
</deploymentConfiguration>

Adam Stoller

Perhaps it would be easier if you explained what you *think* should be happening?

However, in lieu of that, let me see if I can provide sufficient information to help you:

• When OpenDeploy does a sourceFilesystem deployment,
  • it will get a list of the files from the source area (excluduing any filtered items),
    
  • and it will get a list of files from the target area (excluding any filtered items)
    
  • and then it compares those two lists (and the files represented within them) to determine which files to deploy.
    
• Any file on the source side list which is considered to be different than a corresponding file (or lack of file) on the target side will be deployed.
  
• Any file excluded on the target side is treated as if it doesn't exist and thus can be considered "missing"
  

In your case you are specifying that the directory (or file) "d:/www/www/logfiles" and any file (or directory) that ends with the string "web.config" should be considered as not-present on the target side.

Thus if you have any files on the source side that match either of these descriptions - they will be deployed over those on the target side.

However, if you do not have files with these names on the source side, their absense will not trigger a deletion of those files on the target side because you've told OpenDeploy to pretend they don't exist there.

If you have files that match these descriptions on the source side and don't want to deploy them over the files on the target side - then you need to specify a filter for them on both sides.

Hope that helps. If not, please explain what you are trying to accomplish.

--fish
(Interwoven Senior Technical Consultant)