Customize/Use iwadmin store Yes/No

Firenze

I typically create an Administration branch to version config files and provide a collaborative way for developers and app support to view files without providing console access to production systesm for developers.

It seems this is achievable within the iwadmin store, branch and workarea structure.

My gut instinct is to err on the cautious side and to leave that store alone as it is created by the Interwoven install and used by such things as the workflow modeler.

I am interested to know if anyone has been using the iwadmin store and to what level of success. Were there issues and/or side effects during release upgrade or patch installs?

Adam Stoller

I typically create an Administration branch to version config files and provide a collaborative way for developers and app support to view files without providing console access to production systesm for developers. It seems this is achievable within the iwadmin store, branch and workarea structure. My gut instinct is to err on the cautious side and to leave that store alone as it is created by the Interwoven install and used by such things as the workflow modeler. I am interested to know if anyone has been using the iwadmin store and to what level of success. Were there issues and/or side effects during release upgrade or patch installs?

Some people have used it (I believe Andy likes to use it) - but I believe the official word is that "Interwoven does not recommend using the iwadmin store for field customization purposes -- most likely because they aren't ready to guarantee that they won't touch it / change it / etc. through service packs and/or upgrades (it may be unlikely, but they're not willing to guarantee it).

So can you use it? Yes.
Should you use it? Probably not.