Documentation Center

Moving the database

Access restrictions, disk space availability, or other issues might require moving the Legacy Content Delivery database from the installation directory to another location.

About this task

You should perform this procedure on your test server first and then repeat it for your production server.

ContentDelivery_home refers to ContentDelivery_InstallDir\WEB-INF on Windows and ContentDelivery_InstallDir/WEB-INF on Linux.

Procedure

  1. On the Legacy Content Delivery server, stop the Tomcat service or Legacy Content Delivery database service .
  2. Create a backup copy of the ContentDelivery_home\conf.xml file.
  3. Update ContentDelivery_home\conf.xml to reference the new database location.
    1. In the db-connection element, change the value of the files attribute from data to the new location.
      For example, change files="data" to files="D:\KnowledgeCenter\data".
    2. In the recovery element, change the value of the journal-dir attribute from data to the new location.
      For example, change journal-dir="data" to journal-dir="D:\KnowledgeCenter\data".
  4. Copy the data directory from the ContentDelivery_home installation directory into the new location.
    For example, if Legacy Content Delivery is installed in the C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\KnowledgeCenter directory and the new database location is D:\KnowledgeCenter, copy C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\KnowledgeCenter\data to D:\KnowledgeCenter\.
  5. Start the Tomcat service or Legacy Content Delivery database service .
  6. Log on to Legacy Content Delivery and verify that the new database location is working properly.
  7. Delete the data directory underneath the ContentDelivery_home installation directory.