Transactional Deployment with Edition-Comaprison

Hi,
I am using edition-based deployemnt where the recent editions are compared.
Can some one tell me how does transactional deployment works.
Is it a requirement that the target directory contents should be same as edition content only - that means it cannot contain any other files other than the ones in edition.
The previous edition in my case id 'INITIAL'- empty one.
If I use a transactional deployemnt and in case the deployment fails- the target directory becomes empty .
My target directory contains some other files that are not coming from Interwoven.
In case, the previous edition is 'INITIAL' and the transaction rollbacks - the target directory is becoming empty.
Has anyone came across a situation like this.
What I thought it to be is that only the new files that are coming from Interwoven should be rolled-back.
But this seems to be restored back to the same state as previous Edition.

Find more posts tagged with

Comments

John742

Transactional deployments tracks what has been done to each target leg during deploy and if ANY failure occurs it rolls back the changes it has made to each leg within the deployment definition. Do Deletes = yes should take care of files in the target location that are not part of the source location(BE CAREFUL WITH THIS SETTING!!!) Also make sure you are not just comparing editions on the source side and deploying the differences. Please post your Open Deploy XML config. for more assistance

Adam Stoller

Another thing to note with regard to edition-comparison deployments is that you need to track the last successfully deployed edition to use it as your previous-source-area and not just rely on EDITION/IW_PREV.

Otherwise its possible to miss deploying files that were added in interim editions but never managed to get deployed.

tsrookie

If I use a transactional deployemnt and in case the deployment fails- the target directory becomes empty .
My target directory contains some other files that are not coming from Interwoven.
In case, the previous edition is 'INITIAL' and the transaction rollbacks - the target directory is becoming empty.
Has anyone came across a situation like this.
What I thought it to be is that only the new files that are coming from Interwoven should be rolled-back.
But this seems to be restored back to the same state as previous Edition.

To prevent those files in the target directory that aren't coming from Interwoven from being deleted look at using target filters in your odconfig.xml under the target rules element

garima

Hi,
I have not used dodeletes option as it is turned off by default.
PFA my deployment config file.
Please look at it and let me know what is wrong with the same.
there would be two definition in the xml one for deploying to web server and other to app server.
for the time being I am deploying to the same web server

Adam Stoller

Hi,
I have not used dodeletes option as it is turned off by default.
PFA my deployment config file.
Please look at it and let me know what is wrong with the same.
there would be two definition in the xml one for deploying to web server and other to app server.
for the time being I am deploying to the same web server

As I mentioned the code:

...
        <areaDiff  area="//IWSERVER/$branchPath^/EDITION" 
                   previousArea="//IWSERVER/$branchPath^/EDITION/IW_PREV">
        ...

is dangerous because it uses the last edition and not the last successfully deployed edition for the comparison - so you stand the chance of missing files from your target server that exist on your source server if they changed between current and last successfully deployed edition, but not between current and previous edition.

Beyond that you have no doDeletes specified nor any filters to adjust the functionality of the same - if you need that functionality then you need to update your config appropriately - read the manuals for more details.