Pathname translation overview

When you create sources, you use pathnames to specify the locations of the source files used by those sources. This pathname information is stored in the Integration Manager database file. If several people access Integration Manager from different workstations, or if you will be distributing the Integration Manager database file to multiple users, the pathnames may not be consistent.

For example, one workstation may use the drive letter H to refer to the network location where the source files are stored. Another workstation may use the drive letter R to refer to the same network location. If you tried to use the same Integration Manager database file on both workstations, one of them would not be able locate the source files.

To solve this problem, Integration Manager has implemented pathname translations. Using pathname translations, you can define substitutions that will be used in any pathnames defined in the Integration Manager database file.

Pathname translations are stored on a per user basis, not per workstation. If you create a pathname translation on a computer, and log in as someone else, that translation won’t be available.


In the previous example, all the paths for the queries on the first workstation use the drive letter H. If you moved the Integration Manager database file to the second workstation, you would need to create a pathname translation on that workstation that translates from the drive letter H to the drive letter R. Any path that used the drive letter H would then have the drive letter R substituted.

You do not need to use pathname translations if the source files are stored on the server and everyone on the network uses the same drive letter for the server.



Documentation Feedback