Migrating To and From the File System

Use this scenario to migrate artifacts to and from a file system location on the Shared Services Web application server computer. The default file system location is MIDDLEWARE_HOME/user_projects/epmsystem1/import_export/username@ProviderName.

If the final application destination is not on the same network as the source application, the artifacts copied to the file system must be moved to the isolated destination system using File Transfer Protocol (FTP), DVD, or another transfer method.

Note:

In a transfer scenario, ensure that the files are copied to the user directory on the destination file system for the user performing the migration from the file system. If they are copied to a directory for a different user, the user performing the migration will not see the files under the File System node in Shared Services Console.

Process flow:

  1. The LCM Administrator specifies the source and selects the “File System” destination option in Shared Services Console or Lifecycle Management Utility.

  2. Optional: The user saves the migration definition to an XML file that can be used for a later migration.

  3. When the migration is executed, the artifacts are saved to the file system location.

  4. Optional: The user can modify artifacts on the file system.

  5. Optional: The user can use DVD, FTP, or another transfer method to transfer artifacts from one file system location to another.

  6. On the destination server, the LCM Administrator uses Shared Services Console or Lifecycle Management Utility to specify the “File System” as the source and then specify the “Applications” destination option.

  7. Optional: The user saves the migration definition to an XML file that can be used for a later migration.

  8. The artifacts are imported from the file system to the destination application.