 |
Vaults define and reserve a protected part of a storage
media on individual computers or within a network. Access to this areas
must go through the Agile e6 file management
system and is restricted to users with the necessary access rights. Generally
speaking, storage areas can be defined on any storage media within a network.
Vaults in a network are defined on the operating systems level using system
privileges. Vault management functions of Agile e6
can be found in the File Server FMS-Vault mask. It is reasonable to create
only such vaults that physically exist in order to ensure system integrity.
|
 |
Select .
The mask is opened.
|
 |
To change to insert mode click . |
 |
Fill in all fields.
Field |
Meaning |
Vault |
Unique name of the vault |
Type |
IN: |
Check-in, vault for standard file management operations |
BCK: |
Backup area, vault used for the file backup |
EXT: |
External storage area, vault that is used for export operations |
Or additional storage areas if required (additional areas are treated
like "IN" type storage areas).
|
Kind |
FMS: |
Standard vault, encrypted machine-dependent vault (with predefined
names) |
PUB: |
Public storage area, public vault with direct read access
for all users via mounts or client programs |
EIF: |
Extended storage area, encrypted machine-dependent vault (with
cache directories); meta files are created for each file. |
Or additional storage areas if other file servers are used.
|
Site |
Defines the physical location of the computer. |
Node |
Name of the computer/disc node of the corresponding
vault. |
Disc + path |
Name of disc and path of the vault. Entry always has
to end with a "/". |
Network reference |
Automatic generated entry. Network reference for the
file server. |
Name |
Automatic system entry: User name of the user who created
the vault. |
Date |
Automatic system entry: Date of creation. |
Remark |
User comments. |
|
|
 |
 |
To create a vault for the Web Client, additional information
has to be entered in the Web Client-specific fields described below. A vault
must be created to be able to view documents via the Web Client. |
|
Web Client-specific Information
Click on the tab and fill in
the fields:
Field name |
Description |
Protocol |
Protocol for the Web FileService (e.g. http) |
Host |
Host name where the Web File Service runs |
Port |
Port number of the Web FileService |
Path |
Servlet Path on the Web Server (Default: /FileService) |
|
 |
Introduction Web-enabled File Server |
 |
Save the entry. |
 |
Create the vault on the FileServery by using the FMS administration
tool (fms_adm).
See file The File Server Administration Program
for UNIX.
e.g. fms_adm -h fmsHost -n 804257548 -c FMS -p /app/fms/vaults/test_vault/
|
 |
Add the vault to the configuration file filserver.cfg.
The configuration file is located in the FileServer root directory and
lists all standard vaults.
#
# This is the default configuration file for the Agile e6 File Server.
#
# You may adapt this file to your needs, but be aware that any change
# may have severe consequences on performance and memory consumption.
#
# This file is not changed by the application.
#
# --- Allowed vault path section ---------------------------------------------
#
# Only vaults defined in this section are accessible by the File Server.
# Syntax: <vault name>=<vault path>
# Tip: use the PLM vault name to make it easier to synchronize the vault
# definition within PLM with the allowed paths.
#
# The standard vaults are predefined.
#
[Vaults]
FMS=fms/
EIF=area/
PUB=pub/
|
 |
Reload the configuration using the FMS administration tool.
e.g. fms_adm -h fmsHost -n 804257548 -r |