If you have made changes to your company and no longer require the use of a repository within your default federated repository, you can delete the repository from your 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, you must stop all application servers on your system, including WebSphere_Portal, then start the nodeagent and deployment manager servers before you begin any of the following steps.
Perform the following steps to delete a repository from the default federated repository:
- Run the ./ConfigEngine.sh wp-query-repository -DWasPassword=password task, from the wp_profile_root/ConfigEngine directory, to list the names and types of configured repositories.
- Use a text editor to open the wkplc.properties file, located in the wp_profile_root/ConfigEngine/properties directory.
- Enter the following parameters in the wkplc.properties file under VMM Delete federated repository properties:
See the properties file for specific information about the required parameters and for advanced parameters.
- Save your changes to the wkplc.properties file.
- Run the ./ConfigEngine.sh wp-delete-repository -DWasPassword=password task, from the wp_profile_root/ConfigEngine directory, to delete a federated repository.
- Stop and restart the appropriate servers to propagate the changes. For specific instructions, see the following link under Related tasks: Starting and stopping servers, deployment managers, and node agents.
If the deleted repository contained the base entry where new users and groups are stored, you need to run the wp-update-entitytypes
task to select a new base entry to store the new users and groups.
If you created your clustered environment then performed the steps in this task, you must now run the update-jcr-admin
task on the secondary node. See Enabling LDAP security after cluster creation