Running Migration

Note: If you are running ATG Knowledge Reports, you should use the migration application you built only during the initial setup for migrate solutions. Once you have run the migration module, use a new application that includes ATG Knowledge and excludes Service.migration module.

  1. Set up topics and import them using ImportEServer.cmd|sh.

  2. If needed (see above), disable incremental indexing by setting enabled=false in /atg/search/repository/IndexingPeriodicService.

    Start up two applications, one that includes the Service.ATG SelfService and PublishingAgent modules and one with the Service.migration module.

    Note: The PublishingAgent module is required for migrating attachments.

  3. Set up a publishing site and deployment topology in the BCC.

  4. Run the doMigration method from the /atg/svc/migration/EserverMigrationService component manually from the ATG Admin console. This will migrate your data.

    If the doMigration method completes successfully, it will return “true” in the log; if it is unsuccessful, it will return “false”.

 
loading table of contents...