The Wiretap path translation service converts the syntax of a file path referred by a Wiretap server running on a Linux workstation to a format that the client can understand. This service allows Wiretap clients, who might be running Windows or Mac OS X, to understand file paths that are referenced by an Autodesk Creative Finishing product to clips that have been soft-imported from a NAS, SAN, or any remote mounted storage.
When the Wiretap client tries to locate this clip, the path translation service converts the syntax of the path so that the client can access the soft-imported clip from a remote storage device it has mounted locally.
The path translation service uses a translation database. The path translation database contains a set of rules that specify how to convert (or “translate”) a file path referred to by a source workstation (the host running the Wiretap server) into a path that the client can understand. These rules are contained in the /usr/discreet/wiretap/cfg/sw_wiretap_path_translation_db.xml file on each Autodesk Creative Finshing workstation. This configuration file is read by the Wiretap server.
The translation database is an XML file that must be updated by hand as the network configurations change. The file should be created and maintained by a system administrator who is aware of the configuration of the network.
Do you have many hosts accessing the same storage device? Do they mount the central storage using the same syntax and drive names? Are these hosts running the same application? Are they running the same operating system?
If your network includes groups of hosts that mount their storage using the same syntax, you may be able to use a group or platform rule to translate the syntax for all similar hosts. If, however, all of your hosts use different syntax and mount points for their storage, you will have to create a host/path rule for each source and destination host.
You must respect XML syntax standards when editing the path translation file. For example, the values assigned to attributes must not include ampersands (&) or left angle brackets (<) in their literal form. All instances of these characters, except left and right angle brackets used to delimit XML tags, should be replaced with & and < respectively. Do not concern yourself with the white-space between attributes; it is ignored when the file is parsed.
|src_host||The host name or IP address of the workstation to which a client connects. |
If you create a group rule for source workstations, the value of this attribute can be the group name.
|src_path||The path to the remote storage as referred to by the source host (or hosts, when mapping a group).|
|dst_host||The host name or IP address of the client that mounts the same storage referred to by the source, using a different syntax. |
If you create a group rule for destination workstations, the value of this attribute can be the group name.
|dst_path||The path to the remote storage as referred to by the destination host (or hosts, when mapping a group).|
Setting up a host-to-host translation for every machine in your network is inefficient. If you have many hosts that will use the same path translation rule, you can set up a group or platform rule. See the sections that follow.
Use the group rule when you have several workstations that will use the same rule to convert the path syntax of a single source or group of source workstations. This rule is effective in larger installations where numerous workstations mount storage using identical syntax.
|group name||Identifies the name of the group. Create a group name of your choosing. Each group name must be unique. |
Use the value of this attribute in a host-to-host rule to map all members of the group to the same storage mount point.
|host name||Identifies the name of a host that is in the group.|
|os||This attribute is optional. It allows you to link all of the hosts in the group to a single operating system. You can then use a platform rule to map all the hosts in a group to the same mount point. The os attribute is restricted to the following values: Linux, Windows NT, and MacOSX.|
All hosts running the same operating system must mount directories using exactly the same syntax. For example, all Windows workstations must mount the NAS on the N:\ mount point to use the same path translation rule for the NAS.
|src_os||The operating system of the workstation to which a client connects|
|src_path||The path to the remote storage as referred to by all hosts using the same operating system|
|dst_os||The operating system of the client that mounts the same storage referred to by the source|
|dst_path||The path to the remote storage as referred to by the hosts running the destination operating system|
After the path translation database is updated by the system administrator, it must be tested. The sw_wiretap_translate_path command verifies that a path requested from the Wiretap server on the local machine can be translated into a path that can be understood by the client machine.
|-h||Specifies the host name or IP address of the Wiretap server. The default is localhost.|
|-p||Specifies the path on the Wiretap server host to translate.|
|-f||Specifies the file containing the paths on the remote host to translate to the path on the local host, delimited by new lines.|
|-H||Specifies the destination host name. The default is localhost.|
|-O||Specifies the destination operating system (Linux, Windows NT, Mac OSX).|
For example, suppose you have a SAN mounted as “/CXFS1” on your Flame workstation (flame1). A Windows PC (windows1) will mount the SAN as “N:\”. The path translation file contains the following entries: