Delete the repository on i
If you have made changes to company and no longer require the use of a repository within default federated repository, you can delete the repository from configuration.
In single server environments, you do not have to start or stop the WebSphere_Portal and server1 servers to complete the following steps. In clustered environments, stop all application servers on system, including WebSphere_Portal, then start the nodeagent and dmgr servers before you begin any of the following steps.
To delete a repository from the default federated repository:
If the deleted repository contained the base entry where new users and groups are stored, run the wp-update-entitytypes task to select a new base entry to store the new users and groups.
- Run the ConfigEngine.sh wp-query-repository -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to list the names and types of configured repositories.
- Edit WP_PROFILE/ConfigEngine/properties/wkplc.properties
- Enter the following parameters in wkplc.properties under VMM Delete federated repository properties:
federated.delete.baseentry
federated.delete.id
- Save changes to wkplc.properties.
- Run the ConfigEngine.sh wp-delete-repository -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to delete a federated repository.
- Stop and restart the appropriate servers to propagate the changes.
If you created clustered environment then performed the steps in this task, now run the update-jcr-admin task on the secondary node. See Enable LDAP security after cluster creation for instructions.
Parent
Delete the user registry configurations on i
Related tasks
Start and stop servers, dmgrs, and node agents
Enable LDAP security after cluster creation