About Mapping the Hardlink Server

For example, when a UNC path is used for accessing the Hardlink Server (not applicable for Pro/ENGINEER and UGS NX collaborative products), the Hardlink path for the user is \\HardlinkServer\Hardlinks\Test Everything, then the mapping should be:

Hashtable defaultLocation = new Hashtable();

defaultLocation.put("HardlinkServerURL","http://RFAServer:7001/
enovia");

defaultLocation.put("ShadowUser","creator|")]

?defaultLocation.put("StorePath","E:/stacks/STORE")]

locationHardlinkServerDetailsMapping.put("STORE",defaultLocation);

If the password for the Matrix Super User "creator" is changed when RFA is enabled, then the updated password must be specified in the IEFGetHardlinkServerDetailsForRFA JPO. The password must be entered after "|". For example, "ShadowUser", "creator|password"

The StorePath is the path to a file STORE. If you have an FTP STORE, you must specify the full path to the FTP root directory local to that FCS machine, as shown in the example.

When a mapped drive is used to access the Hardlink Server, the Hardlink root path is shared and mapped on the client machine as H:\ and a sample user's hardlinks directory is then H:\Test Everything, then the mapping should be:

Hashtable defaultLocation = new Hashtable();

defaultLocation.put("HardlinkServerURL","http://RFAServer:7001/
enovia");

defaultLocation.put("ShadowUser","creator|")

defaultLocation.put("MappedDrive", "H:");

?defaultLocation.put("StorePath","E:/stacks/STORE")]

locationHardlinkServerDetailsMapping.put("STORE", defaultLocation);

All clients must create the mapped drive to the Hardlinks root path as specified in the JPO (H:\ in the above example). If any local drive is mapped to the Hardlink Server, then the mapped drive is used in forming the paths to access files from the Hardlink server. In the absence of this mapping, the UNC path will be used to access the files from the Hardlink server.

For RFA to work, the client machine must map the hardlinks directory to exactly the same drive letter that is specified in the IEFGetHardlinkServerDetails JPO file. For example, if the string in the JPO is, "defaultLocation.put("MappedDrive", "H:")", then the client machine must map the hardlinks directory only to drive letter H.

If you implement RFA on FCS machines, then the JPO needs a separate block in the mapping section for each location. For example, if you have:

• An FCS Location defined as Japan
• FCS URL for this FCS store set to http://japan:7001/enovia
• G:\ is the drive on the client that maps to the Hardlink root path on the FCS machine.

The JPO would be modified as follows:

Hashtable japanLocation = new Hashtable();

japanLocation.put("HardlinkServerURL","http://RFAServer:7001/
enovia");

japanLocation.put("MappedDrive", "G:");

?japanLocation.put("StorePath","e:/JapanLocation")]

locationHardlinkServerDetailsMapping.put("Japan", japanLocation);

The hardlink server name in the JPO should not be defined as localhost or 127.0.0.1. The applet uses this information to get the value of user's hardlink directory. The URL should also specify and include the enovia application name, such as http://servername:7001/enovia.