ReverseDeploymens and filelists

stefanmaier

Hi All,

I have some problems with a reverse deployment, perhaps someone can give me some hints:

Situation:

  Server A            <<<<<<<< Server B
  Reverse Target               Reverse Source
  OD 6.0.2.1.1 installed       OD 6.0.2.0.0 installed

The deployment is started through an "iwodstart myconfig" command on Server A.

Here's the OD-Config on server A (some lines are "blurred"):

<definition name="def1">
  <reverseSource>
      <sourceFilesystem  area = "Y:\...\directory" filelist="c:\list.txt">
              <pathSpecification>
                  <path name = "." />
              </pathSpecification>
      </sourceFilesystem>

      <replicationFarmLink>
            <internal name="Farm1"/>
      </replicationFarmLink>
  </reverseSource>

  <reverseTarget>
        <comparisonRules dateDifferent="yes" />
        <targetFilesystem area="C:\temp\reverse" />
        <transferRules doDeletes="no" />
  </reverseTarget>
</definition>

Problem is:
The deployment does only complete when the file c:\list.txt (given in the filelist attribute above) exists on the reverse source server (Server .
If the file doesn't exist on server B, I get an error message.
e.g. in the odbase.log on server B:

ENG: 2007-10-02 14:48:19 CEST GMT+02:00 ***ERROR - FileList c:\list.txt not found.

Intention is, that the filelist has to exist on server A, where the iwodstart command is triggered,
so that we can first create the filelist and then start the deployment.

Any suggestions to implement our requirement?

Regards
Stefan

Adam Stoller

Hi All, I have some problems with a reverse deployment, perhaps someone can give me some hints: Situation:   Server A            <<<<<<<< Server B   Reverse Target               Reverse Source   OD 6.0.2.1.1 installed       OD 6.0.2.0.0 installed The deployment is started through an "iwodstart myconfig" command on Server A. Here's the OD-Config on server A (some lines are "blurred"): <definition name="def1"> <reverseSource> <sourceFilesystem area = "Y:\...\directory" filelist="c:\list.txt"> <pathSpecification> <path name = "." /> </pathSpecification> </sourceFilesystem> <replicationFarmLink> <internal name="Farm1"/> </replicationFarmLink> </reverseSource> <reverseTarget> <comparisonRules dateDifferent="yes" /> <targetFilesystem area="C:\temp\reverse" /> <transferRules doDeletes="no" /> </reverseTarget> </definition> Problem is: The deployment does only complete when the file c:\list.txt (given in the filelist attribute above) exists on the reverse source server (Server . If the file doesn't exist on server B, I get an error message. e.g. in the odbase.log on server B: ENG: 2007-10-02 14:48:19 CEST GMT+02:00 ***ERROR - FileList c:\list.txt not found. Intention is, that the filelist has to exist on server A, where the iwodstart command is triggered, so that we can first create the filelist and then start the deployment. Any suggestions to implement our requirement? Regards Stefan

Off the top-o-my-head, it seems you need to run two deployments - the first, to send the filelist, the second to perform the reverse deployment using that filelist.

Reverse deployments tend to be somewhat rare, and also tend to use source-target-diff mode, perhaps with filters, to pull things like log files and such that live in a given directory on the reverse-source server.

Although it won't help you right now - you might open a FR with IWOV Support for a reverse-filelist feature that would allow you to specify the filelist on the initiating (reverseTarget) server and let it transfer the filelist in-memory to the sending (reverseSource) server to be processed as-if the filelist was there (or something like that).