nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Staging area deployment

artor

Hi,

I have to deploy a staging area or Edition of a branch from one TeamSite server to other TeamSite server in a staging or Edition of a branch.

Both TeamSite server has same branch structure, as far as deploying workarea, working well but when i go to deploy staging area from one server to other server staging area, causes the deployment failed ..right now I am using directory camprision deployment and I read on the od manual which doesn't says anything about directory camparision.
So if anybody know please let me know .

I would really appreciate your help.
Thanks in Advance.

Environment TS 6.1 Solaris 5.8 OD 6.0
Have two teamsite server with two open deploy.

Regards,

Find more posts tagged with

Comments

herald10

You can not deploy to STAGING area as STAGING is readonly for all the purposes. The only way would be to deploy to a workarea and then promote the content to STAGING using iwsubmit CLT.

hth
-H

Edited by herald10 on 10/27/04 02:43 PM (server time).

artor

Actually I have to copy the whole branch with Workarea,staging and Edition from one server to other server with all extend attributes etc. and I am looking for a solution through opendeploy and as your iwsubmit ..if i copy the staging and edition area from 1st server to 2nd server in some other directory and then submit those content directly to staging and edition through iwsubmit, would it work or will do this through dnr script? is it possible or not?

Regards,
A

Adam Stoller

As stated - you cannot create the staging area or edition area in the way you are trying.

If you are able to use MultiStore - you can create an alternate store for the branch(es) you wish to migrate to the other server, then copy that alternate store to the other server and re-migrate them back into the default store on that other server.

If you aren't able to use MultiStore - you could do a series of deployments from each edition (in order, oldest-to-newest) on the source server to a workarea on the target server, followed by a submit and publish on the target server before deploying the next edition from the source server. OD6 provides the ability to transfer the EAs, but the timestamps and comments associated with each submission and edition will be lost (unless you create a complicated process of capturing all that information - though you'll still use the timestamps)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

artor

As far as

If you are able to use MultiStore - you can create an alternate store for the branch(es) you wish to migrate to the other server, then copy that alternate store to the other server and re-migrate them back into the default store on that other server.

If I have two machine TS1 and TS2 on Solaris and then I want to use iwmigrate then how come I use to migrate store from one machine to another machine because as for my knowledge it works well in different store on the same machine so please tell me the best way to copy store to other server
or u mean make the tar ball and ftp to othe server and untar inside the content store (default or other), it doesn't effect permission.

If you aren't able to use MultiStore - you could do a series of deployments from each edition (in order, oldest-to-newest) on the source server to a workarea on the target server, followed by a submit and publish on the target server before deploying the next edition from the source server. OD6 provides the ability to transfer the EAs, but the timestamps and comments associated with each submission and edition will be lost (unless you create a complicated process of capturing all that information - though you'll still use the timestamps)

i think as for me it becomes very complicated because i don't know that how many edition are created on one server and to deploy first on workarea of first server and then submit to editon with the same name that is on the orignal server which requires to have some external script to control this kind of task.
Am I following you??

Regards,
A
Thanks in advance for ur nice input

Adam Stoller

You've pretty much got it.
iwconvert - which works between servers - unfortunately only works for pre-5.5.2 backing stores to 5.5.2+ backing stores.

However - I may have just had an epiphany ... If you use iwstoreadm to "create" another store on the source server and then replace the created store with a read-write mount of the backing store of the target machine - you ***might*** be able to use iwmigrate to copy the branch(es) directly from the source store to the target store. If it works, it would tend to save a fair amount of time in the overall process - and you would maintain all the history and timestamps, etc.

If you do this - please keep good notes - and post them afterwards.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

artor

I have doubt to use iwmigrate on Solaris box as you mentioned

you ***might*** be able to use iwmigrate to copy the branch(es) directly from the source store to the target store.

Well I will try the process that you suggested and see what happen then,

Fish thanks again for nice input.

Regards,
A