Directory Mapping
Cerebro Support avatar
Written by Cerebro Support
Updated over a week ago

This option makes network resources accessible for users of different operating systems, because network paths have different formats in different operating systems. It’s very useful for work in heterogenous OS environment.

For example, users may add some network links to forum messages. As far as these links must have different formats for MacOS, Linux and Windows, Cerebro must adjust the links accordingly to make them accessible for any platform user.

The algorhythm of directory mapping works this way: let’s say, you have a shared network resource, accessible by the following path:

  • Windows: \server\catalog;

  • Linux: /mnt/catalog;

  • Mac OS: /Volumes/catalog.

The Administrator must type these values into the configuration file. From now on, before opening a file, Cerebro will check all the specified paths and, if the beginning of a link will match one of them, the directory will be mapped according to the current OS.

For example, a Mac OS user is given a link to a file that looks like /Volumes/catalog/file.foo.

Another user (under Linux) tries to open this file. Cerebro resolves this path and substitutes its beginning - /Volumes/catalog to /mnt/catalog, the result will be /mnt/catalog/file.foo and the file is opened successfully.

Warning

The most common cause of incorrect or non-working directory mapping is incorrect path settings in the configuration file. Make sure that you specify correct path settings. Also, keep in mind that they are case-sensitive.

Let’s review a specific example of a configuration file. The directory mapping settings are specified in the <cerebro executable path>/etc/viewers.conf file. That is, the file is located in the same folder where is the Cerebro executable (In MacOS you have to open the contents of the application).

Note

If you have a single instance of Cerebro client application in your company (installed on a server), obviously, the changes will be applied for all users at once. Otherwise, if you have a separate instance of Cerebro client application on every workstation, you have to change this file on each workstation.

Directory mapping uses the values at the very neginning of the viewers.conf file. They look like this:

<dirMap>
    <enable Value="0"/>
    <dirs>
        <map>
            <win Value="//server/projects"/>
            <mac Value="/volumes/projects"/>
            <linux Value="/server/projects"/>
        </map>
    </dirs>
</dirMap>

You must type the settings of your network folders (there may be more than one folder) in there, for example:

<dirs>
    <map>
        <win Value="//server1/projects"/>
        <mac Value="/volumes/projects"/>
        <linux Value="/server1/projects"/>
    </map>
    <map>
        <win Value="//server2/data"/>
        <mac Value="/volumes/data"/>
        <linux Value="/server2/data"/>
    </map>
</dirs>

Warning

Cerebro will not map directories until you activate the enable parameter:

<enable Value="1"/>

In the configuration file you should list all network folders for all operating systems where you intend to use directory mapping. For example, Cerebro running under Linux must resolve a network path created by a MacOS or Windows user.

If you get an error message like  is not found attempting to open a file (using Mirada for example), troubleshoot it as described here: “Troubleshooting”.

Did this answer your question?