Open Deploy get hanged ..or not getting completed..

Hi All,

I am trying open deploy content from one teamsite branch to another
teamsite branch.

I am using CLT and passing arguments thru the command line.
But the deployment gets hanged?
/**
iwodcmd start mytestod2 -k branch=default/main/bt/btw/portal/13_CR36383963/WORKAREA/content/images -k selected_edition=BTWCR63

*///

Could some one throw light on it?
Please find the Open deploy file attached.
Note: I have configured the odbase.xml and did a service restart.

Lal

Find more posts tagged with

Comments

Adam Stoller

iwodcmd start mytestod2 -k branch=default/main/bt/btw/portal/13_CR36383963/WORKAREA/content/images -k selected_edition=BTWCR63

From your attached deployment configuration file:

        <areaDiff area="/$branch^/$selected_edition^" previousArea="/$branch^/IW_PREV">

Lal

Hi,

My requirement is the user selects an Edition(edition_dec21).
and OD has to deploy this selected edition to target area.

But if edition_dec21 already exists in target area, then OD should compare between the src edition_dec21 and target edition_dec21 and deploy only those files which are newly added or modified to the src edition_dec21.

Could you throw some more lights into this requirement.

Regards,
Lal

jkm

Why do you want to compare with your target edition? I think a better way will be to compare both the editions on the source side, get the delta, create the filelist and then run the deployment

Adam Stoller

Hi,

My requirement is the user selects an Edition(edition_dec21).
and OD has to deploy this selected edition to target area.

But if edition_dec21 already exists in target area, then OD should compare between the src edition_dec21 and target edition_dec21 and deploy only those files which are newly added or modified to the src edition_dec21.

Could you throw some more lights into this requirement.

Regards,
Lal

I just took a second look at your configuration file and it's even more confusing than I originally thought - you're assuming the top-level of a TeamSite area (presumably an edition) as the source area - but you're using a templatedata/category/data-type/data/ directory as the target area - you either need to use the root of the target workarea as the target area, or you need to specify the same templatedata/category/data-type/data/ directory on the source side.

That being said - your requirements as stated above are unclear - you are either trying to keep two branches in sync - or you are doing something else. I suggest you take a step or two back, think carefully about what you are trying to accomplish, try again to accomplish it yourself - and if that doesn't work, take your time composing a post that clearly explains the requirements, the design, the implementation tried, and the problems encountered.