Novell Teaming can run on the versions of Linux and Windows listed in Section 2.1, Teaming Server Requirements.
Novell Teaming can run on 32-bit or 64-bit processors. A 64-bit processor is recommended for a large Teaming site where the processor load will be heavy and data storage will require a large amount of disk space.
If a 32-bit processor is sufficient for your Novell Teaming server, the server needs at least 3 GB of memory. If you plan to use a 64-bit processor in your Teaming server, the server needs more.
Teaming server memory usage is significantly affected by some factors and less affected by others:
Number of users logged in: No significant effect.
Number of concurrent active sessions: No significant effect.
Database server caches: Significant memory usage.
When you follow the instructions for a Basic installation, the database is located on the same server as the Teaming software. After you have successfully tested your Basic installation, you can reconfigure Teaming to have its database on a remote server, so that the database uses separate memory resources, as described in Section 13.0, Creating the Teaming Database on a Remote Server.
Teaming internal data caches: Significant memory usage.
When you follow the instructions for a Basic installation, the Teaming internal data caches are subdirectories of the teamingdata directory, described in Section 3.2.4, Teaming Installation Locations. The Teaming internal data caches are separate from any caching or memory usage by the database server itself.
Lucene index cache: Significant memory usage.
The Lucene* Index Server is a high-performance Java search engine. Large file repositories (particularly with large files or a large number of files) can create a very large data index. When you perform a Basic installation, the Lucene index is created on the same server where the Teaming software is installed. After you have successfully tested your Basic installation, you can reconfigure Teaming to have its Lucene index on a remote server, so that it uses separate memory resources, as described in Moving the Lucene Index Server to a Remote Server.
|
BASIC TEAMING INSTALLATION SUMMARY SHEET |
|---|
|
Under , specify the amount of physical memory you plan to have in your Teaming server. |
When you perform a Basic installation, the amount of memory allocated to the Java Virtual Machine (JVM*) where the Teaming software defaults to 1 GB, which is adequate for a medium-sized Teaming site running on a 32-bit server. This memory allocation, called the Java “heap size,” does not include memory used by your database server or by the Lucene Index Server when these programs are running on the same server as the Teaming software.
A general rule is that no more than 75% of the available physical memory should be allocated to the JVM. Memory not allocated to the JVM must be sufficient to support the operating system, the database server, and the Lucene Index Server if they are also running on the Teaming server, and any other processes running on the Teaming server.
IMPORTANT:A JVM on a 32-bit server should not be configured to take more than 1.5 G of memory. However, large numbers of users and documents often need memory settings higher than 2 GB to provide adequate performance. Such a Teaming system should be set up on 64-bit hardware.
|
ADVANCED TEAMING INSTALLATION SUMMARY SHEET |
|---|
|
Under , specify the amount of memory to allocate to the JVM where Teaming runs. |
Although it is possible to run Novell Teaming with less than 1 GB of memory for the JVM, this applies only to very small test configurations, and is not suitable for production systems. In a test configuration, 512 MB is the minimum amount of memory required to produce a functioning Teaming installation.
The default file location for the Novell Teaming software varies by platform:
Included under the main Teaming software directory are subdirectories for Tomcat and file viewer software.
The default file location for the Novell Teaming file repository also varies by platform:
IMPORTANT:On Windows, the Teaming Installation program displays the Windows pathname using forward slashes (/) rather than the traditional back slashes (\). This syntax is necessary in the Installation program.
The Teaming file repository holds all files that are imported into Teaming, information related to the imported files, such as thumbnails and HTML renderings, and the search engine index.
|
BASIC TEAMING INSTALLATION SUMMARY SHEET |
|---|
|
Under , specify the directories where you want to install the Teaming software and data if you prefer not to use the default locations. |
A Basic installation allows you to change the root directory for the Teaming software and the Teaming file repository.
IMPORTANT:If you want to organize the Teaming file repository so that some file types are not under the Teaming file repository root directory, you must perform an Advanced installation as your initial Teaming installation. You cannot move directories out of the Teaming file repository root directory after the initial installation has been performed. To perform an Advanced installation in order to organize the Teaming file repository to meet your needs, complete the planning steps for a Basic installation and complete the Basic Teaming Installation Summary Sheet, then follow the additional instructions in Distributing Different Data Types to Different Locations.
The Oracle Outside In viewer technology used by Novell Teaming to render various file formats into HTML for viewing require access to TrueType* fonts. Typical locations for these fonts are:
/usr/X11R6/lib/X11/fonts/truetype /usr/share/fonts/truetype