Skip to Main Content
Return to Navigation

Managing Data Migration Project File Locations

The project file locations are managed by a system administrator in the Project Repository to restrict the places where Data Migration Project files can be placed. Before you can copy a Data Migration Project to a file, you must set up the Project Repository to use. Typically, this task will be performed by a system administrator.

There are two parts to the Project Repository setup process:

  1. Creating the file system folders for a specified path and the areas under that path. These folders should be manually created by a system administrator with appropriate access permissions for those users who will be starting the application and process scheduler servers or running Change Assistant. The system administrator should manually create both the path folders and the area folders.

    Note: On non-Windows operating systems, folder names are case sensitive. At run-time area names are upper cased, so the names of area folders should also be upper cased.

  2. Registering the path and area folders in the database as locations for holding project files. These database locations are the Project Repository.

This section describes the page to registration the path and area folders of the Project Repository.

Use the Manage File Locations page (PTPRJREPOSDEFN) to register the path and area folders of the Project Repository.

Image: Manage File Locations page

This example illustrates the fields and controls on the Manage File Locations page. You can find definitions for the fields and controls later on this page.

Manage File Locations page
Location Name

Assign a name for your file location.


Optionally add a description for the file location.


The specified path must be accessible from both the application server and the

process scheduler server. Absolute network paths are less prone to issues in this respect as all servers are not likely to be running on the same machine, thus may not have access to a local or relative path.

If the application server is on Windows and the process scheduler server is on non-Windows or conversely, your system administrator will need to provide special setup to share files across machine boundaries.

Note: On Windows, you must use a UNC naming convention, such as \\<servername>\<sharename>. On UNIX based platforms, you must use absolute path, such as /<rootdir>/<subdir/.../<subdir>.


The area grid is populated with the sub directories in the path.