Mapping ATG Intrinsic Fields to eServer Properties

Before migrating eServer properties, you should understand a few key differences between the ATG model and the eServer model.

ATG Knowledge has several solution fields called intrinsic fields. These fields are inherent characteristics of the solution and are updated by the system; they are not editable by users. Examples include dateCreated, author, and dateModified.
ATG fields are defined on each solution class, while eServer properties are created and stored globally.

eServer global properties do not have a one-to-one correspondence to The ATG intrinsic fields, but certain intrinsic fields are required in ATG. Therefore, you need to specify which eServer properties should be mapped into these required intrinsic fields. You create this map in the EserverMigrationService. properties configuration file.

See Migration and Security for information on how ATG migrates security on intrinsic fields.

ATG requires the intrinsic fields in the following table, and populates them based on migration settings as shown.

ATG Intrinsic Field	Source for Populating This Field
`author`	`EserverMigrationService.author`
`dateCreated`	`EserverMigrationService.dateCreated`
`modifiedBy`	`EserverMigrationService.modifiedBy`
`dateModified`	`EserverMigrationService.dateModified`
`status`	Solution class’s `workflowName` and `solutionStatus` settings in XML file. See Mapping eServer Solution Statuses to ATG Workflow Statuses.
`owningGroup`	Solution class’s `owningGroup` setting in XML file. See Migrating Solution Owning Groups.
`language`	Language of the solution. See Mapping Language Settings.

The default EserverMigrationService.properties file maps intrinsic fields to commonly used eServer properties as follows:

# Service intrinsic field mappings. These should be mapped to
# eServer property tags
dateCreated=date_created
author=author
modifiedBy=modified_by
dateModified=date_modified

ATG Knowledge Configuration Guide

Mapping ATG Intrinsic Fields to eServer Properties