fbpx

How to Use Link-Management: Keep your links working when moving all files to a new server

In the case of a broken link, the linkmgmt.txt file directs Solid Edge where to look for files. The first thing in the file is CONTAINER, RELATIVE, ABSOLUTE.

In the case of a broken link, the linkmgmt.txt file directs Solid Edge where to look for files. The first thing in the file is CONTAINER, RELATIVE, ABSOLUTE. This means if you open an assembly and you can’t find a Solid Edge file, it will look first in the Container (folder) where that file is located. Then it will look in the relative path, meaning if the missing file was up two file folders and saved in that area, Solid Edge will go up two folders no matter what the names of the folders happen to be and then look for the file there. Then, the absolute path is checked for that file. There are two ways to look in other locations. These correspond to two sections in the linkmgmt.txt file.

  • One section (BEGIN SEARCH PATH) is for those locations you want to search directly. The search path section is for single entries; it says if you can’t find the file in container, relative or absolute paths also search for it here (in the example below D:Ally Solid Edge FilesCommon Parts).
  • The other section (BEGIN MAP) is for those locations that you want to swap out in the search – instead of path A directory, replace it with path B. They are in pairs – so Solid Edge (in the example below) sees a path with AllyPLMServer1 in it and swaps it with this AllyPLMServer2012. The BEGIN MAP section is the section that is helpful when you move all the files from one server to another server. If you take a top level folder from one server and move it to another server, you can just add the server names to the link management file and place the file in the Preferences directory in the Solid Edge installation location (default is C:Program FilesSolid Edge ST8Preferences) for every client to resolve these links.
    One issue you may run across is if users have mapped their own drives and used these mapped drives to pull the parts into the assembly on creation of the assembly. So if someone has mapped a drive to a folder three levels deep and the other person has a mapped drive that is only one level deep and they are both pulling parts into assemblies this way, you may have to use the other section (search path) to put in the path specifically. It is best practice to have standard mapped drives for all users.

Also, keep in mind the more you add to this file, the more you will see a performance hit as Solid Edge has to search all of these locations.

Example LinkMgmt.txt file

CONTAINER

RELATIVE

ABSOLUTE

BEGIN SEARCH PATH

D:Ally Solid Edge FilesCommon Parts

END SEARCH PATH

BEGIN MAP

AllyPLMServer1

AllyPLMServer2012

END MAP

Get the latest tips, software updates and promos.

1 Comment. Leave new

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.

Menu