All documents must be stored in repositories. These repositories may be located either in a database instance or in directory hierarchies in the file system.

When documents are checked in, they are stored in repositories. If an error occurs during a transaction, the database transaction mechanism, rollback, is used. This mechanism is not available if the documents are stored in the file system.

Document data or fragments are not stored temporarily on the hard disk at any time.

If documents are stored in the file system, you must follow the conventions of the respective operating systems when assigning access rights: Under UNIX all files are created with the access rights rw, rw, rw (i.e. 666), directories are created with the rights rwx, rwx, rwx (i. e. 777). All other restrictions must be made using the relevant "umask" reductions. Furthermore, the user with the effective UID, under which the server processes run, becomes the owner of all objects in the repository.

Under Windows all the file system objects inherit the predefined access rights of the repository root directory. This directory must be created manually (in both Windows and UNIX). The current user becomes the owner of the root directory and of all the repositories contained in this directory.

In addition to the documents and repositories, all the configuration data of the SAP Content Server is stored in a configuration file. The name and address of the path to find this file is different for Windows and for Unix.

Under UNIX the file is called cs.conf (or csc.conf for the cache server). After the content server has been installed, the file is located in directory $HOME/conf. Though you can redefine the name and path of the configuration file in the environment variable CSConfigPath (CSCConfigPath for the cache server), or by setting this variable in the config section of the Web server, (provided this is permitted). Variable definitions in the web server configuration will precede the environment variables. In every case the access rights for the file cs.conf/csc.conf should be restricted to only the owner having read and write access and group members having only read access. Other users should not be able to read the configuration files. These access rights (640) are set by the installation program.