Installing the Storage Layer extension

To track the publishing and unpublishing of binaries you need to install the documentum_storage-1.0-SNAPSHOT.jar and configure the BinaryEventsLocation in the DAO Bundle configuration file to specify where to store tracking information.

Before you begin

You need to have installed the Content Deployer Server Role as a .NET Web application or Java Web application.

Procedure

  1. Access the installation media.
  2. Navigate to the Content Delivery\ directory.
  3. Copy documentum_storage-1.0-SNAPSHOT.jar to your Content Delivery lib directory:
  4. Copy BinaryEventsDAOBundle.xml to one of the following directories:
    • to the classes directory, if your Content Delivery is running in a Java Web application,
    • to the config directory, if your Content Delivery is running in a .NET Web application.
  5. Configure BinaryEventsDAOBundle.xml:
    1. Open BinaryEventsDAOBundle.xml in a text editor.
    2. Change the BinaryEventsLocation to an existing directory on your system, for example:
      <BinaryEventsLocation path="C:\tridion\binaryevents" />
    3. Save and close BinaryEventsDAOBundle.xml.
    4. Make sure the user under which the Content Deployer is running has Read, Write and Delete access to this directory. When Content Deployer is running as a Web application, the user is the Application Pool identity.
  6. Configure the Storage Layer:
    1. Open the cd_storage_conf.xml configuration file in a text editor.
      The file is located in your classes directory (for Java Web application) or config directory (for a .NET Web application).
    2. In the <Storages> element, add the following <StorageBindings>:
      <StorageBindings>
         <Bundle src="BinaryEventsDAOBundle.xml"/>
      </StorageBindings>
    3. Save and close cd_storage_conf.xml.
  7. Restart the Content Deployer.

What to do next

After installing the Storage Layer extension, you need to install and configure the binaryeventsync Web page to sync data back to the Content Manager.