Hi Rahul,
the documentation that Alex provided is helpful, but very far from being perfect.
If you follow it, there will be a lot of debris left in the system, which later will only get it stuck with unneeded data. Additionally the deletion of the repository might not even work, because you will get a message that there are certain references to this repository and until those are removed, you won't be able to delete it.
Here is a list of passes, which we always implement in order to de-commission a repository properly: (depending on what you want to achieve, you might have to run some of the below passes with BYPASS_MEMBER_TASK=1)
1. Remove all repository privileges from any business roles
2. Remove all repository privileges from any users
3. Delete any repository generated attributes (e.g. ACCOUNT)
4. Delete all repository privileges from the identity store
5. Delete the system privilege for this repository
6. Delete any generated groups for the repository (e.g. Java., AD)
7. Obsolete jobs, which refer the repository you are about to delete
8. Check and update any PVO, which might be pending for that repository
9. Login to Admin UI and try to delete the repository
That's all.
BR,
Todor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.