read only store ability?

I am running an iwmigrate on a content store to a new "archived" content store. Is there any way that I could make this archived store read only? Do i have to do it at the active driectory level (make a new AD ldap role that is just read access to the entire Y: drive)..... or can I do it at the teamsite content store level? or creating a new user/group?

Any ideas thoughts would be appreciated.

S

Find more posts tagged with

Comments

Adam Stoller

I am running an iwmigrate on a content store to a new "archived" content store. Is there any way that I could make this archived store read only? Do i have to do it at the active driectory level (make a new AD ldap role that is just read access to the entire Y: drive)..... or can I do it at the teamsite content store level? or creating a new user/group?

Any ideas thoughts would be appreciated.

S

I assume you're talking about after the migration - right?
You could try something like iwfreeze +99999999999 store-name

Siddharta

Yes.. this is all post iwmigrate

I am only iwmigrating the editions, so those in itself will be read only. I just want to ensure that no users can create/edit on the archive store.

the iwfreeze option is an option as well, thanks for that suggestion, I want to set it up so when the archive store is activated, users can not even view it unless they are in a specified role group.

Adam Stoller

I want to set it up so when the archive store is activated, users can not even view it unless they are in a specified role group.

I don't believe you can hide archives / stores from view - but if you make sure that all the branches in that store are set with very restrictive rights and role permissions, and you have branch and workarea security enabled in iw.cfg - that should prevent users (other than those you've explicitly allowed) to see or do anything in those branches)

Note - I strongly recommend the use of TeamSite groups for both access and role permissions - that way if you want to allow someone else to access the content there you just need to add them to one TeamSite group instead of going through each branch and workarea and modifying the rights and roles that way.

Siddharta

Thanks ghoti. That is the route that I am going with for this situation. However, it is very odd, but it seems that every team I access the teamsite UI Administration tab and try and alter the roles and group configurations, the UI times out and we end up with a Jboss crash. Literally every single time.

TeamSite 7.21
Windows 2008 64 bit server SP1
8 CPUs

Any insights? I am going to open this up with the vendor b/c the symptoms are occurring in both non-prod and prod environments.