Lifecycle Management uses migration properties to set the global parameters for migrations.
To modify the migration properties:
Launch Shared Services Console. See Launching Shared Services Console.
Under Application Groups, expand Foundation, and then Deployment Metadata.
On the Artifact List tab, expand Shared Services Registry, then Foundation Services, and then Shared Services.
Select the Properties artifact; then, right-click and select Export for Edit.
In the File Download dialog box, save the Properties artifact to the desired location.
Return to Lifecycle Management, right-click the Properties artifact used in Step 5, and select Import after Edit.
In the Import after Edit dialog box, point to the file system where the edited Properties artifact is available.
Table 3. Migration Properties and Their Descriptions
| Property | Description |
|---|---|
double-encoding | 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 |
filesystem.artifact.path | Location of the directory where the exported applications are to be stored. 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/username@ProviderName. Note: On Windows 2003, if Shared Services is started as a Windows service and the file system path is defined for a mapped drive, you cannot view the file system contents using Shared Services Console. If the file system path is a network-accessible location, use the UNC path (//host/share/path) instead of a mapped drive. Ensure that the separator is a forward slash (/). |
fileSystem.friendlyNames | Whether to store the files for an artifact with extended names (a combination of artifact ID and name). If the value is true or if this property is missing, the path for the files corresponds to the artifact path in listing.xml. If the value is false, the pathAlias value in listing.xml is used. Some file systems have a directory path depth limitation. In rare cases, the file system might not allow a depth of more than 256 characters, in other cases 4000 characters. If an application has a directory structure that can be greater than this limit, this property can be set to false and the Lifecycle Management engine will use shorter names (UUIDs) for the directory and artifact names. Recommended value is true. Default value: true |
| hfmCallBackPortRange | Callback port for status updates on Financial Management application creation. Default value: 12010-12210 |
| HFM.client_timeout | HTTP Session Time Out setting for Lifecycle Management SOAP calls from Lifecycle Management and Shared Services to Financial Management Web Service. Default value: 5000 |
report.enabled | Enables you to use the [-estimate] argument in Lifecycle Management Utility to estimate the number of artifacts in a proposed migration. For more information about using the [-estimate] argument, see Running the Utility. Default value: Y |
report.folder_path | Directory where the migration status and artifact estimation reports are stored. Default value: ../reports (MIDDLEWARE_HOME/user_projects/epmsystem1/diagnostics/logs/migration/reports) |