The file system location is on the Shared Services Web application server computer. The default destination on the Shared Services computer is MIDDLEWARE_HOME/user_projects/epmsystem1/import_export/username@ProviderName. Applications or artifacts exported (or copied) to the file system location are displayed under the File System node in the View pane. When artifacts are exported to the file system, they retain the last modified time the artifact was updated in the native product.
For migration scenarios, see Migration Scenarios.
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, ensure that Shared Services is not running as a Windows service. |
To export artifacts and applications to the file system using Shared Services Console:
Launch Shared Services Console. See Launching Shared Services Console.
View artifacts. See Viewing Artifacts.
Optional: Click Selected Artifacts (above the artifact listing) to filter the list of selected artifacts and display only the selected artifacts.
On the Source page, select the source applications for migration, and click Next.
Note the following:
The Source page displays only if you have selected artifacts from multiple applications (or multiple sources). If you have selected artifacts from only one product, the Migration Wizard skips this page and jumps to the Source Options page.
All sources displayed on the Source page are included in the migration definition, and you must provide migration options for each source.
To exclude a source from a migration definition, select it and click Remove Source.
You can execute the migration once at the end after providing migration options for each. After a migration is defined in Migration Wizard, a green check mark is displayed next to the source on the Source page.
On the Source Options page, enter information about the source, and click Next.
Source options differ by product. For a listing of options by product, see the appendixes at the end of this guide.
On the Destination page, expand the nodes to view the destination locations, specify the File System option, and click Next.
If you specify a directory name that already exists on the file system, and the directory is used by the same application, the preexisting information in that directory is overwritten. If the directory is used by a different application, you will not be allowed to proceed with the migration definition.
On the Destination Options page, review the destination options, and click Next.
Destination options differ by product. For a listing of options by product, see the appendixes at the end of this guide.
On the Migration Summary page, review the source and destination options you specified. Click Back to make changes.
Save the migration definition for a later migration or execute the migration immediately:
To save a migration definition, see Saving a Migration Definition.
To execute a migration immediately:
Click Execute Migration.
Click Launch Migration Status Report to view migration status, or click OK.
Tip: | Artifacts that are migrated to the file system can be secured. The first level of security is file system security. To limit access to artifacts on the file system, modify the permissions on the import_export folder to ensure that the user who starts Shared Services has full permissions on the import_export folder; no other user has these permissions. If an additional level of security is needed, the content of the import_export folder can be moved to a password-protected container such as Winzip, or it can be encrypted on the file system using PGP or other data encryption methods. Ensure that before the artifacts are imported from the file system, they are unencrypted by the authorized user. |