OD Config - adding a definition for new src/target

David Smith

I think I know the answer to this already, but I am hoping I just am not smart enough.  Do I have your attention, Nipper?

 

I have an existing deployment config that is the main deployment config for our content.  It is pretty simple:

 

  <definition name="MYDEF">
    <source>
      <fileSystem>
        <filelist area="/iwmnt/default/main/company/WORKAREA/shared" filePath="$filelist^">
          <pathSpecification>
            <path name="." />
            <filters>
              <includePath subPath="assets"/>
              <includePath subPath="fragments"/>
              <includePath subPath="html"/>
            </filters>
          </pathSpecification>
        </filelist>
      </fileSystem>
    </source>

    <target>
      <targetFilesystem area="/opt/interwoven/webdocs/foo" />
      <filters>
        <includePath subPath="assets"/>
        <includePath subPath="fragments"/>
        <includePath subPath="html"/>
      </filters>

      <transferRules doDeletes="yes" />
      <comparisonRules dateDifferent="yes" />
      <permissionRules file="0644" directory="0755" user="_iwod_user_"
                       group="_iwod_group_" />
      <replicationFarmLink>
        <external name="PRD_WEB" />
      </replicationFarmLink>
    </target>
  </definition>

Note the use of the includePath filters - this is important and I'm not about to change this.

 

We have a new requirement to publish content for a separate site's content that will be maintained in our same branch/workarea as our main site's content.  The path for that site's content (let's call the site "blah") is:

 

/default/main/company/WORKAREA/shared/html/site/blah

 

The unfortunate part of it is that the target path for this new site's content is:

 

/opt/interwoven/webdocs/foo/blah (the relative path from source to target is not the same, in other words)

 

I'm trying to figure out a way to add this new definition to the existing deployment config, but I can't combine includePath and excludePath in the same config.  I just don't see a way to do it without creating a new filelist in my java code (recognizing files attached to the workflow in the new site's path) and creating a new definition with the proper source path and unique target path.  That will work, of course.  I would just prefer not to have to use java code to solve the problem.  Any brilliant ideas?