For each solution class (and associated solutions) you wish to migrate, create a solutionClass entry in the eserver_migration_config.xml configuration file. All solutions of that solution class will be migrated according to the attributes specified in that entry.
You can specify which eServer properties ATG should use for the solution class name, solution statuses, and owning group. The following example shows how this appears in the XML file:
<solutionClass tag="medical_solutions"
workflowName="/Service/SvcPublishContent.wdl"
owningGroupProperty="owner"
migrate="false"
defaultLanguage="en_US"
…
</solutionClass>
For information on migrating solution class statuses, see Mapping eServer Solution Statuses to ATG Workflow Statuses.
For information on migrating solution owning groups, see Mapping eServer Member Properties to ATG Users or Organizations.
For information on language settings, see Mapping Language Settings.
You can control solution class migration in the following ways:
Globally disable solution class migration by setting
EserverMigrationService.to
enableMigrateSolutionClassesfalse.Note: Globally disabling solution class migration also disables migrating all solutions.
Exclude one or more solution classes by omitting them from the
eserver_migration_config.xmlconfiguration file. That is, do not createsolutionClassentries for any solution classes you do not want to migrate.Note: Excluding a solution class from migration also excludes all solutions of that solution class. If you disable migrating a solution class, no solutions of that solution class will be migrated.
Override global migration settings for specific solution classes by setting the
migrateattribute in theeserver_migration_config.xmlconfiguration file tofalse, as shown in the example above. (For example, you can setenableMigrateSolutionClassestotrue, but have one or more solution classes withmigrate="false".)
