Home

 

Disabling file versioning

By default, when a user uploads a new version of a file it becomes the latest version, and all previous versions are kept. Users can see all versions of a file in the user interface. You can disable file versioning in the files-config.xml properties file.

Disabling versioning can help control the size of data storage. When you disable versioning before users start using Files, only one version of a file is ever stored, and all updates are reflected in that version.

However, you can disable versioning at any time. If there are already multiple versions of a file when you disable versioning, the latest version becomes the "active" version, and all future updates are reflected in that version. The older versions are hidden from the user interface, but still exist and take up space in the database. If a user reaches their space quota, you can delete these older versions by enabling versioning again and having the user open the file page, click the Versions tab, and delete versions.

You can also perform a manual database update to remove all versions of files prior to the current ones. You would execute a delete statement on your database for the MEDIA_REVISION table, but specify a constraint that the column IS_CURRENT_REVISION = 0, as a record still exists for the current version.

  1. Start the wsadmin client.

  2. Access the Files configuration files...

    If you are asked to select a server, you can select any server.

  3. Check out the Files configuration files...

    FilesConfigService.checkOutConfig("<working_directory>", "cell_name")

    where:

    • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied. The files are kept in this working while you make changes to them.

    • cell_name is the name of the WebSphere Application Server cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. If you do not know the cell name, do one of the following to determine it:

      • Stand-alone deployment: Look at the name after the following in the file system:

          WAS_HOME\profiles\profile_name\config\cells\

      • Network deployment: Type the following command while in the wsadmin command processor:

          print AdminControl.getCell()

    For example:

    • AIX/Linux:

        FilesConfigService.checkOutConfig("/opt/my_temp_dir", "CommServerNode01Cell")

    • Microsoft Windows:

        FilesConfigService.checkOutConfig("c:/temp","foo01Cell01")

  4. Optional: To view the current configuration settings use the following command:

      FilesConfigService.showConfig()

  5. To set the file.versioning.enabled property to false

      FilesConfigService.updateConfig("file.versioning.enabled", "false")

  6. Check in the changed configuration property file using the following wsadmin client command:

      FilesConfigService.checkInConfig()

  7. To exit the wsadmin client, type exit at the prompt.

  8. Stop and restart the server hosting the Files feature.


Administer Files

 

Related tasks

Start the wsadmin client

+

Search Tips   |   Advanced Search