Simon Barratt

Leveraging AdminP

As of 6.5.4 user name changes will not revert back, if the user does not accept the change, without admin approval.

AdminP needs to be managed.

ACL, in 6 default access can be dropped to No Access
Admins need author as a minimum

Replication retention should be standardised, should not be longer than 21 days.  Anything longer is dangerous

Db size will be affected if approvals are not managed.

Delayed request settings.  Default is Sunday, can be more frequent, this manages reader/author name changes


don't use tell adminp process all!!!!!!!!!!!
tell adminp process new - jump starts processes
tell adminp process prople
person doc changes
tell adminp process daily - this will fix unread marks for users who have had their name changed

tell adminp show databases - will show you which dbs do and do not have an admin server set

speed up replication if you want to speed up adminp in a global environment.

Assign responsibility for Error, Admin attention and Approval views monitoring

Be very wary of turning on an old server - this will recreate all the old stuff that has already been processed.  Never restart a server that has been out of service for more than the purge interval of admin4.

Find Users or Groups will locate user names listed explicitly in db ACL's for example.

Best Practises

• can be achallenge
• only difficult the first time