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; } } }

Create Workarea scripts for iwmigrate

ProfessorX

All-

We have a problem with our backing store which is requiring us to do a migrate (iwmigrate). This doesnâ€™t migrate workareas.

Some workareas I can create manually because all content and code have been submitted. In other WA's code/content cannot be promoted and must stay in the designated WA. These WAâ€™s I am concerned about.

Does anyone have any steps/suggestions on how to create say 100+ workareas automatically? Does anyone have a script that they could share with me?

I'm looking on migrating over WA content/code, group for sharing and file/directory permissions.

Some steps I am considering are:
-- Create the new WA with Owner and Shared By permissions using the latest edition
-- Do a get latest in new WA to be double sure that the WA is in sync with staging
-- Copy over content from the old WA to the new WA only if content is different from staging (old WA -- old staging)

Some tools that I will probably use:
iwmkwa
iwupdate
iwcmp

What am missing?

I would greatly appreciate it if anyone could help me out.

Thanks in advance!
win2k3 TS 6.5 sp1; OD 6.0.1; DD enabled
The Professor-

Find more posts tagged with

Comments

Adam Stoller

Some steps I am considering are:
-- Create the new WA with Owner and Shared By permissions using the latest edition
-- Do a get latest in new WA to be double sure that the WA is in sync with staging
-- Copy over content from the old WA to the new WA only if content is different from staging (old WA -- old staging)

Some tools that I will probably use:
iwmkwa
iwupdate
iwcmp

iwlasted - used to get the name of the last edition, so when you create the workarea it will be reasonably close to in-sync, you'll still need to do the iwupdate though to pick up changes since the last [named] edition.

I think the steps you have outlined are probably the way to go though you may need to use some packaging utility (tar / gzip, etc. or if you're writing a Perl script - try the Archive::Tar module) since you cannot have both stores "active" at the same time.

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

ProfessorX

Thanks for the input fish

You can have 2 stores active at the same time absoultly

We migrated the store to a different naming convention "iw-store.migrate"

Maybe you thought we migrating the store to a differnt location with the same name?

You just make an entry in wi.cfg

[iwserver]
store_directory_New=C:\iw-store.migrate\default

Thanks in advance!
win2k3 TS 6.5 sp1; OD 6.0.1; DD enabled
The Professor-

Adam Stoller

You can certainly have multiple stores active at the same time - that's what MultiStore is all about - I'm just talking about the context of backing store migration - I believe that the *target* store for the migration cannot be active during the migration, and hence you'd need to extract the modified files (and their EAs) from the source store while it is active, so that they can be transferred to the target store after the backing store migration has finished.

If the migration is at the "surface" level - not at the backing store level - then yes - both stores could/should be active at the same time.

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