Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Deploying files to multiple locations
Balu110
Hello,
Using Open Deploy, I am trying to deploy from a single source to multiple directories on the destination servers by filtering folder names using sourceFilesystem xml tag.
For example,
from source/web folder to one destination location (/iw-home/OpenDeployNG/tmp) on the web server.
from source/data folder to multiple destination locations (/iw-home/OpenDeployNG/tmp & /iw-home/OpenDeployNG/test) on the app server.
But doing so, I am getting the following error:
Error : CONFIG_FILE.
Details: Duplicated destination area is not allowed:
I am unable to understand why Open Deploy is throwing an error, when I am trying to deploy files on the same location (/iw-home/OpenDeployNG/tmp) but onto different servers.
Any help is greatly appreciated.
Balu.
Find more posts tagged with
Comments
Adam Stoller
The file you posted is not syntactically correct - it's missing the end tag for
replicationFarmSet
Also, instead of:
<definition name="WWW_APP">
<source >
<sourceFilesystem area="/htdocs/data" >
<pathSpecification >
<path name="."/>
<filters >
<!-- ... -->
</filters>
</pathSpecification>
</sourceFilesystem>
</source>
<target useReplicationFarm="DEV-AppFarm">
<!-- ... -->
<targetFilesystem area="/iw-home/OpenDeployNG/test"/>
</target>
<source >
<sourceFilesystem area="/htdocs/data" >
<pathSpecification >
<path name="."/>
<filters >
<!-- ... -->
</filters>
</pathSpecification>
</sourceFilesystem>
</source>
<target useReplicationFarm="DEV-AppFarm">
<!-- ... -->
<targetFilesystem area="/iw-home/OpenDeployNG/tmp"/>
</target>
</definition>
You might try this:
<definition name="WWW_APP">
<source>
<sourceFilesystem area="/htdocs/data">
<pathSpecification>
<path name="."/>
<filters>
<!-- ... -->
</filters>
<targetRules area="/iw-home/OpenDeployNG/test"/>
</pathSpecification>
<pathSpecification>
<path name="."/>
<filters>
<!-- ... -->
</filters>
<targetRules area="/iw-home/OpenDeployNG/tmp"/>
</pathSpecification>
</sourceFilesystem>
</source>
<target useReplicationFarm="DEV-AppFarm">
<!-- ... -->
<targetFilesystem area="***OVERRIDDEN_ABOVE***"/>
</target>
</definition>
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
Balu110
Hi Fish,
Still getting the same error.
Uploaded the modified config file.
Balu
13adam13
In your definition name="WWW_APP":
In the source element, you are specifying to deploy the same area (area="/htdocs/data") and path (path name=".") to the same target space (useReplicationFarm="DEV-AppFarm").
It looks like you are attempting to deploy area /htdocs/data to server2:/iw-home/OpenDeployNG/test and server2:/iw-home/OpenDeployNG/tmp.
To do this, you should have a single source path specification, and multiple target elements. Adding the <targetRules/> element to the source specification does not actually do anything.
HTH
--Adam Wilson
Adam Stoller
To do this, you should have a single source path specification, and multiple target elements. Adding the element to the source specification does not actually do anything.
I think you're wrong here:
A
source
element can only be associated with a single
target
element.
A
source
element can be associated with 1-or-more
pathSpecification
elements
A
pathSpecification
element can contain a
targetRules
element which can include an
area
attribute
the
area
attribute of a
targetRules
element
overrides
the
targetArea
element within the
target
container.
However, it's possible that this problem is an instantiation of a bug which I thought had been fixed - wherein two definitions deploy to the same target area -
despite the fact that each is going to a
different
target node receiver
- OD sees it as two deployments to the
same
target area and disallows that (especially when one has
doDeletes
enabled.
The easiest way to verify this is to use distinct sub-directories of the target area for each deployment:
<definition name="WWW_WEB">
<source >
<!-- ... -->
</source>
<target useReplicationFarm="DEV-WebFarm">
<!-- ... -->
<targetFilesystem area="/iw-home/OpenDeployNG/tmp
/WEB
"/>
</target>
</definition>
<definition name="WWW_APP">
<source >
<!-- ... -->
</source>
<target useReplicationFarm="DEV-AppFarm">
<!-- ... -->
<targetFilesystem area="/iw-home/OpenDeployNG/test"/>
</target>
<source >
<!-- ... -->
</source>
<target useReplicationFarm="DEV-AppFarm">
<!-- ... -->
<targetFilesystem area="/iw-home/OpenDeployNG/tmp
/APP
"/>
</target>
</definition>
or
<definition name="WWW_WEB">
<source >
<!-- ... -->
</source>
<target useReplicationFarm="DEV-WebFarm">
<!-- ... -->
<targetFilesystem area="/iw-home/OpenDeployNG/tmp
/WEB
"/>
</target>
</definition>
<definition name="WWW_APP">
<source >
<sourceFilesystem area="/htdocs/data">
<pathSpecification>
<!-- ... -->
<targetRules area="/iw-home/OpenDeployNG/test"/>
</pathSpecification>
<pathSpecification>
<!-- ... -->
<targetRules area="/iw-home/OpenDeployNG/tmp
/APP
"/>
</pathSpecification>
</sourceFilesystem area="/htdocs/data">
</source>
<target useReplicationFarm="DEV-AppFarm">
<!-- ... -->
</target>
</definition>
If one of these changes works - then it looks like a bug which should be reported to Support -- although - if server1 and server2 nodes are defined to be the same receiver - then it's
not
a bug - it's OD being "smart" and realizing that you
are
trying to deploy from two source areas to the same target area....
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
