Setup guide
For example, Lustre running on a Windows workstation can work with an Autodesk Creative Finishing
product's soft-imported clip on a SAN or NAS.
For the Windows workstation, the syntax of the path to the media files may resemble:
N:\myclips\clip1\frame1.dpx
On a Linux workstation, the path to the same media files may resemble: /CXFS1/myclips/clip1/frame1.dpx
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.
Configuring the Path Translation Database
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.
To configure the path translation database:
1 Consider your network environment and how you can organize hosts to simplify the path translation
process.
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?
2 Open /usr/discreet/wiretap/cfg/sw_wiretap_path_translation_db.xml in a text editor.
3 Create the rules for translating the file path. The rules are applied in the order that they appear in the
file. The first rule is applied. If that rule matches, then the translation is complete. If the rule doesn't
match, the next rule is examined.
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.
See the sections that follow for a description of the possible path translation rules you can create.
4 Save the file.
5 You do not have to restart Stone and Wire to apply changes in the path translation database. The
Wiretap server periodically checks the timestamp of the file and, if there are changes, it updates itself
accordingly. However, if you want to test the results of your changes, you can restart Stone and Wire
manually. To restart Stone and Wire manually, type: /etc/init.d/stone+wire restart Stone and
Wire restarts.
About XML Syntax
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.
WiretapCentral and Wiretap Gateway Installation | 141