In the eserver_migration_config.xml configuration file, you use the properties element to list all eServer properties that you want to migrate. Any properties that you omit from this file will not be migrated.
Note: ATG requires some fields, called intrinsic fields. For more information, see Mapping ATG Intrinsic Fields to eServer Properties.
Migration maps properties, property attributes, and statement roles according to the following table:
eServer Property | ATG Solution Field Mapping |
|---|---|
indexing | property’s |
purpose | becomes a property on the solution |
usage | becomes a custom property on the solution |
editor | maps into an ATG user |
eServer Property Attribute | ATG Solution Field Property |
tag |
|
name |
|
multiValued |
|
eServer Statement Role | ATG Solution Field Property |
goal, symptom |
|
status (or other specified property) |
|
The migration process maps property data types according to the following table:
eServer Property Data Type | ATG Property Data Type |
|---|---|
List | List |
List (Boolean) | Boolean See Mapping eServer Number Properties for more information. |
Member | User or Organization See Mapping eServer Member Properties to ATG Users or Organizations for more information. |
Date | Date |
Number | Integer, Boolean, or Decimal See Mapping eServer Number Properties for more information. |
Specifying Default Values for Properties
ATG migration supports specifying a default value for properties, to use when a solution has a property but no value set for it. In eServer, default values are defined per-member; in ATG Knowledge, default values are defined globally. When configuring migration, you choose one eServer member to use as the source of default values for all solutions.
In EserverMigrationService.properties, set the defaultPropertyValueEServerMemberId property to the member ID you want to use as the source for default values. The default value of this property is 2 (“Everyone”).
