Note: On grid setups and job node setups, an area configured as import/export directory must be a shared directory, accessible from the nodes and from the master server.
Folders configured as import/export directories must be readable and writable by the user that runs the CLC Server process. Users logged into the CLC Server from their Import/export directories can access files in that area, and potentially write files to that area. However, it is the user running the server process that actually interacts with the file system.
Permissions can be set on import/export directories, restricting access to certain groups. This is done under the Global permissions area of the web administrative interface, under the Configuration tab.
Press the Add new import/export directory button to enter the relevant path (figure 3.7). The specified folder and its subfolders will then be available to CLC Workbenches logged into the CLC Server when relevant activities, such as import and export, are carried out.
If direct data transfer has been enabled, then CLC Workbench users can import data from their local file system to the CLC Server. These files are transferred over the network, placed as temporary files in the area configured for this purpose, which will be an import/export directory, and then imported. Direct data transfer configuration is described in Direct data transfer from client systems.
Whether or not direct data transfer has been enabled, users connecting to the CLC Server via client software will be able to select files from areas configured as import/export directories (figure 3.5).
Note: Import/export directories should NOT be set to subfolders of any defined CLC file system location. CLC Server file system locations are intended for data imported into or generated by CLC software. Import/export directories are intended for holding other data, for example, sequencing data that will be imported, data that is exported from the CLC Server, or BLAST databases.