This page describes the method to use the auto-deploy technology for creating a new empty DMS environment, and for restoring a new DMS environment from a backup.

Git repositories involved in the process are:

Import script repository: This contains the script and service files to create new document repository.

http://172.20.32.20:7990/projects/DMSCLIENT/repos/import_script/browse

Steps to perform import of documents:

  1. Create empty repository following the instructions here. 

  2. Clone client specific repository to ~/deploy/import_script to store import script - if you start out from the preconfigured DMS VM images, this step can be skipped:

    git clone ssh://git@edmssupport.pace-ip.com:7999/dmsclient/import_script.git ~/deploy/import_script

  3. Set the path of the documents to import in ~/deploy/import_script/config/import.conf. 
    Do not alter the import_script/importer/config.py, it refers to internal paths that must be static and usually the standard settings fit


    Note: It is important that the documents have been created/copied to the import directory in UTF-8 format. To verify, find any document in the import directory of the DMS host having special symbols in its filename  (such as ä, ö, ü, å, etc.) in a terminal session on the DMS host and print its name (e.g. by listing the directory with the 'ls' command). All the special symbols must show correctly; if this is not the case, the documents must be copied over to the import directory again observing the UTF-8 requirement.


  4. If the path contains a folder named "Actor" manually rename the folder to "actor", i.e. make the first letter lowercase.

  5. Make sure files under this path have read permission for everybody. Better yet, to be absolutely sure: set all permissions for everybody during the import process (you can always delete this folder afterwards or re-set the permissions. Also make sure that the folder is owned by the main User (dms)

    chmod -R 777 /myimportfolder
chown -R 1000:1000 /myimportfolder
  6. cd into ~/deploy/import_script and update the deploy and restore scripts as per below instructions.
  7. If you are connected via SSH, consider using screen or a similar utility for the next step to avoid the import being interrupted due to the ssh session being closed.
  8. make sure to set the entry for file.import.completed in your PAT_DMS_SETTINGS to false. Else all Document Sweepers will run during Import which will slow the process down tremendously.
  9. Run "./import.sh"
  10. When the import process finished, check the final output of the compare script to be sure everything was imported correctly.
  11. Run post-import cleanup and maintenance tasks.

The DMS containers can now be deployed and the DMS started up by cd'ing into  ~/deploy/deploy_script/ folder and running "./deploy.sh" with necessary options. For options and further instructions, see here.

Steps to update the import script:

From within the  ~/deploy/import_script directory as well as the run:


git.sh -i /root/.ssh/git_id_rsa pull


 

Steps to run a differential import (repo re-sync):

Important: A differential import (repo re-sync) will only work if the initial import and, where applicable, all consecutive imports were run against a DMS version 1.9.8.2.2+

  1. Set file.import.completed = FALSE in PAT_DMS_SETTINGS table of Patricia database.
  2. Run endpoint to delete documents from repository that were created after the previous import was finished. Check item no. 12 on diagnosis servlet page. ("Deleting documents from repository that were created after import was finished").
  3. Re-run import script as outlined above.

Post-import cleanup and maintenance task:

Following a repository import, it is important to create the case folders inside the DMS for cases which contain no documents.  Check item no. 13 on diagnosis servlet page ("Creating folders in DMS for empty Patricia cases").


  • No labels