The default location for the Novell Teaming file repository varies by platform:
Under the main Teaming file repository root directory are subdirectories for various kinds of data files that are not stored in the Teaming database (MySQL, Microsoft SQL Server, or Oracle). Using an Advanced installation, you can store Teaming data files in various locations.
The data files not stored in the Teaming database are divided up into several functional areas:
Simple file repository: A large consumer of disk space.
All attachment files are stored in the file repository. All versions of files are also stored here.
Jackrabbit repository: (Optional) Takes only a fraction of the space consumed by the file repository.
By default, Teaming stores all data files individually on disk, in the file repository. If you prefer to store data files in the database itself, you can use Apache Jackrabbit* with Teaming. See the Apache Jackrabbit Web site for setup instructions.
Extensions repository: Depends on the number of extensions you add to your Teaming site.
An extension is a software program that you can incorporate into your Teaming site in order to enhance (extend) Teaming capabilities. Adblock Plus is an example of a browser extension for the Firefox Web browser that filters out advertisements. You or a Java developer can create custom extensions for your Teaming site. For more information about creating and using Teaming extensions, see the Kablink Teaming 2.1 Developer Guide.
Archive store: A large consumer of disk space.
When entries are deleted, files that were attached to the deleted entries are retained in the archive store in order to meet compliance and archival goals. Previous versions of documents are also retained in the archive store. After files have been archived, they are inaccessible from the Teaming site. Files that accumulate in the archive store must be manually deleted as needed to manage the disk space occupied by the archive store.
Cache store: Consumes less disk space than the file repository.
Information derived from the attachments, such as thumbnails, HTML renderings, scaled images, and word lists for indexing are stored in the cache store.
Lucene index: Takes only a fraction of the space consumed by the file repository.
The Lucene index contains only pointers to the actual data stored in the file repository. The index enables the Lucene search engine to perform very fast searches through large quantities of data.
The directories for the various types of data can be on the Teaming server or on a remote server. Data access is fastest if the data is local, but depending on the size of your Teaming site and the types of data you store, the Teaming server might not be the best place to store all the Teaming data. If you want to store any of the data types on a remote server, you must ensure that the remote location of the data appears local to the Teaming server and that it is always available with read/write access.
|
Linux: |
Mount the file repository to the Teaming server. |
|
Windows: |
Map a drive from the Teaming server to the file repository. |
|
Linux and Windows |
Place the file repository on a SAN (storage area network) with read/write access. This alternative provides the most reliable remote location for the Teaming file repository. This is required for a clustered environment, as described in Section 15.0, Running Teaming on Multiple Servers. |
|
ADVANCED TEAMING INSTALLATION SUMMARY SHEET |
|---|
|
Under , specify the directories where you want to store the various types of Teaming data. |
Complete the planning process for additional Advanced installation features as needed, then perform the Advanced installation as described in Section 10.0, Performing an Advanced Teaming Installation.