Migrating Attachments

If the enableMigrateAttachments option in EserverMigrationService.properties is set to true (the default), all solution attachments are migrated. ATG looks through the solution for URLs that match the host specified in the attachmentHosts option.

Note: When migrating attachments, make sure that all servers listed in attachmentHosts are running and are available to the machine where migration is happening.

If migration encounters any invalid URLs, MigrationExceptions will be thrown and migration will stop. To disable this error checking, set the ignoreInvalidAttachmentURL option to true in EserverMigrationService.properties. Setting this option to true causes migration to ignore invalid attachment URLs and continue migrating valid attachments. To repair invalid attachment URLs, edit the solution after migration is complete.

Attachment files are stored in the directories specified in the /atg/svc/repository/service/util/
AttachmentUtils component, in its documentRootFolder and imageRootFolder properties, in a subdirectory called migrated. As each solution is processed, its attachments are stored in a subdirectory with the same name as the eServer solution prefix. For example, attachments for a solution with prefix “acctelco” will be stored in the following directories by default:

Migrated Attachments with ATG Self Service

Migrated attachments become assets in the ATG versioned repository. If you are using ATG Self Service, you will need to create matching document and image directories on the ATG Self Service server where the Publishing Web Agent runs, so that the attachments can be deployed correctly:

  1. First, in the <ATG2007.3dir>/Service2007.3/Service/ATG
    SelfService/config/atg/svc     directory, create two directories named documents and images.

  2. In each of those directories, create a directory named migrated.

  3. In each of those directories, for each eServer solution prefix, create a directory with the same name as the prefix.

 
loading table of contents...