Editing Migration Properties

Lifecycle Management uses migration properties to set the global parameters for migrations.

  To modify the migration properties:

  1. Launch Shared Services Console.

    See Launching Shared Services Console.

  2. On the View pane, expand the Application Groups node.

  3. Under Application Groups, expand Foundation, and then Deployment Metadata.

  4. On the Artifact List tab, expand Shared Services Registry, then Foundation Services, and then Shared Services.

  5. Select the Properties artifact; then, right-click and select Export for Edit.

  6. In the File Download dialog box, save the Properties artifact to the desired location.

  7. Edit the migration properties as desired.

  8. Return to Lifecycle Management, right-click the Properties artifact used in Step 5, and select Import after Edit.

  9. In the Import after Edit dialog box, point to the file system where the edited Properties artifact is available.

  10. Restart Shared Services.

Table 5. Migration Properties and Their Descriptions


Allows Base64 encoding on top of UTF-8 encoding in Financial Management application migrations.

This property is not supported if you are performing Financial Management migrations in a mixed-release environment (for example, using a previous release of Financial Management with this release of Shared Services). If you are performing a Financial Management application migration in a mixed-release environment, set this property to false.

Default value: true


Location of the directory where the exported applications are to be stored. This is the shared disk location if Shared Services is configured for high availability. To customize this parameter, uncomment this line and add a path location.

Default value: This parameter is commented out and the Lifecycle Management engine uses the default file system location on the Shared Services computer; for example, MIDDLEWARE_HOME/user_projects/epmsystem1/import_export.


On Windows 2003, if the file system path is a network-accessible location, you must use a UNC path, or a shared file system with read/write permissions for concurrent access.


To enable data migration across distributed environments, filesystem.artifact.path must be a shared path.


Whether to store the files for an artifact with extended names (a combination of artifact ID and name).

Default value: true


fileSystem.friendlyNames is applicable only for Reporting and Analysis and deployment metadata. Artifacts of other products are always stored with artifact names.

groupcountNumber of artifacts that are migrated in a group.

This option is available for products that support migration in groups (Planning, Financial Management, Financial Close Management, Performance Management Architect, Reporting and Analysis, and FDMEE). Performance Management Architect and Financial Close Management artifacts are always migrated in one group irrespective of the size and count of the artifacts.

The default group count is 30. This means that artifacts are migrated in groups of 30. Based on data regarding types of artifacts, size of artifacts, and number of artifacts, this value can be changed to improve migration performance.

Default value: -1

MSR.PURGE.EARLIERTO.DAYSAdministrative setting relating to Lifecycle Management migrations.

Any migrations older than this value are periodically purged when the Foundation Services system is started, with the check running every 24 hours.

Default value: 30 days


Directory where the migration status and artifact estimation reports are stored.

Default value: ../reports (MIDDLEWARE_HOME/user_projects/epmsystem1/diagnostics/logs/migration/reports)

zip.thresholdMaximum ZIP file threshold size.

If the size of export content exceeds this threshold, then the exported content is stored as a folder. This size should not exceed 1.8 GB. Any size bigger than this has browser and JDK limitations for ZIPand download.

Default value: 1.8 GB