Multiple sources to single target

Hi,

I am trying to deploy files from two sources to a single target.

For this, in od.xml file i configured as in attached file.

scenarios:
1. if list1.txt have files as a.js,b.js and list2.txt has files as c.js,d.js
In this case deployment is happening properly without any issue

2.if a.js is also present in list2.txt (if same files are there in the both source filesystems)
In this case deployment is failing.

Please can any one help in this cases. Is it possible to deploy duplicate files from two servers to a single target in a single deployment..?

Thank you in advance.

Find more posts tagged with

Comments

Adam Stoller

I'm assuming you copy/pasted/edited the config file you posted since it is currently syntactically incorrect.

It would probably help to look at the errors in the OD logs (probably more on the receiving side than the sending side, but check both just to be sure)

You might eliminate the problem (but cause others?) if you change the deployment from transactional to non-transactional -- since you're effectively trying to change the same file twice within the same transaction which doesn't sound "kosher" to me.

ISCBorisB

Hi,

I am trying to deploy files from two sources to a single target.

For this, in od.xml file i configured as in attached file.

scenarios:
1. if list1.txt have files as a.js,b.js and list2.txt has files as c.js,d.js
In this case deployment is happening properly without any issue

2.if a.js is also present in list2.txt (if same files are there in the both source filesystems)
In this case deployment is failing.

Please can any one help in this cases. Is it possible to deploy duplicate files from two servers to a single target in a single deployment..?

Thank you in advance.

In addition to what Ghoti already mentioned...

You absolutely cannot do it in transactional mode without at least some changes. The reason is txn
roll-back. OD Engine cannot create duplicated iwold/iwnew components for the (potential) roll-back
and aborts the whole transaction.

Note that single deployment runs deployment legs as multiple threads. You can neither predict nor control
an order of individual Files transport. If identically named Files are present in both A and B sources,
which one do you expect to win? Can they differ?

Long story short, in your place I would probably run two deployments or alternatively, create "on Source, Before"
DNR script to "massage" Lists leaving only unique A/B entries or perhaps copy all files into temp source location
and perform single Filelist deployment from there.