Page tree

Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.

This pages explains how to delete a JCR workspace on a Magnolia system.

JCR API and Jackrabbit

You cannot delete a JCR workspace programmatically with Magnolia. You must delete it manually.

Apache Jackrabbit, which is the JCR implementation used by Magnolia, does not implement the #deleteWorkpace method defined in the JCR 2.0 API (see javax.jcr.Workspace javadoc). 

org.apache.jackrabbit.core.WorkspaceImpl#delete
public void deleteWorkspace(String name) throws AccessDeniedException, UnsupportedRepositoryOperationException, RepositoryException {
  this.context.getRepository().getWorkspaceInfo(name);
  this.context.getAccessManager().checkRepositoryPermission(32768);
  throw new UnsupportedRepositoryOperationException("not yet implemented");
}
For more information, see Apache Jackrabbit - Frequently Asked Questions.

Deleting a workspace manually

Before starting:

  • Note that deletion cannot be reverted.
  • Ensure the workspace you want to delete does not contain content you still require.
  • Shut down the application server (such as Tomcat) before manually deleting. You cannot delete a workspace on a running system. 

Overview

There are two main steps involved in deleting a workspace manually:

  1. Delete the folder $magnolia.repositories.home/magnolia/workspaces/$workspace-name.
  2. Delete database tables with table names containing the workspace name.

On embedded databases such as H2 you can skip step 2.

Deleting the workspace folder in the repository folder

For every JCR workspace there is a folder on the file system. The value of the magnolia.repositories.home property defines the location of these folders. Check the value for your system:

  • If your system is still running, use the About app to look up the property.
  • Alternatively, check the magnolia.properties files where the property is defined.

Determine the path for $magnolia.repositories.home/magnolia/workspaces/$workspace-name and delete the folder.

Example: 

magnolia.repositories.home/var/lib/author/tomcat/webapps/author/repositories
Workspace namedms
Folder to delete/var/lib/author/tomcat/webapps/author/repositories/magnolia/workspaces/dms

Deleting database tables

Generally you should delete all tables which contain the JCR workspace name.

Your approach when deleting these tables depends on the persistence layer. Some examples of persistence layers are: Apache Derby, H2, Ingres, MySQL, Oracle and others. The value of the Magnolia property magnolia.repositories.jackrabbit.config gives an indication of the persistence layer in use.

Example:

Jackrabbit persistence layerMySQL (Version 14.14, Distribution 5.7.20, for Linux (x86_64))
Workspace namedms
Table names in MySQL DBPM_DMS_BINVAL, PM_DMS_BUNDLE, PM_DMS_NAMES, PM_DMS_REFS

Multiple instances and clustering

Depending on how your Magnolia instances are set up and if you use clustering, you must delete a workspace in one or several locations.

Make sure you delete the workspace on both the author instance and on all public instances.