What Prerequisites are needed for Teaming + Conferencing?

  • 7001396
  • 19-Sep-2008
  • 27-Apr-2012

Environment

Novell Teaming 1.0
Novell Teaming 1.0 Support Pack 1
Novell Teaming 1.0 Support Pack 2
Novell Teaming 1.0 Support Pack 3
Novell Teaming + Conferencing
Novell Conferencing 1.0 Support Pack 1
Novell SUSE Linux Enterprise Server 10
Novell SUSE Linux Enterprise Server 10 Support Pack 1

Situation

Prior to installing Teaming + Conferencing there are several Prerequisites that need to be installed and configured.  The purpose of this document is to help identify which Prerequisites are needed and where they can be found.

Resolution

Prerequisites for Teaming:

Computer:
Minimum 2 GHz processor
Multi-CPU systems preferred
Minimum 2 GB RAM

 
One of the following operating systems:
Novell Open Enterprise Server 2.0 (Linux Kernel)
SUSE® Linux Enterprise Server (SLES) 10 SP1
Red Hat Enterprise Linux 3 or 4
Windows Server 2003

 
Java 1.5 JDK/SDK:
NOTE: Java 1.6 is not yet supported.
Sun JDK 1.5.0 Update 11 or Later
NOTE:Sun has changed the name of JDK 1.5 to 5.0, any reference to the JDK 1.5 refers to JDK 5.0.
The Sun JDK has to be downloaded from http://java.sun.com, go to downloads, JAVA SE, Previous Releases, J2SE 5.0 Downloads, JDK 5.0 Update 11(or later), and select the OS version.
or
IBM SDK 1.5
NOTE: On SLES 10 SP1 or OES 2 the IBM Java5 SDK Standard Edition is included but not installed by default. This can be installed by accessing Yast2, Software Management and searching for "java-1_5_0-ibm-devel" package.  Installing this package and any dependencies will fullfill the Java requirements for Teaming
NOTE: If you intend to Add the Novell Collaboration Portlets (see KB 7001209) you will want to use the Sun Java.

 
Database server:
MySQL 5.0.26 (or higher) Server and Client for Linux or Windows
Linux: MySQL 5.0.26 ships with SUSE® Linux Enterprise Sever (SLES) 10 SP1 and can be added from Yast2, Software Management.
Windows or Linux: MySQL 5.0.26 or later can be aquired from http://dev.mysql.com/downloads/mysql/5.0.html.  Either the Community (free) or Enterprise versions will work. Choose the OS and Bit version desired. Acquire the Server, Client and Share libraries for the version desired.
NOTE 1: MySQL 5.1 is not yet supported.
NOTE 2: The GUI Tools packages are also useful.
Or
SQL Server* for Windows* (2000 or 2005)
Or
Oracle* 9, 10
 
 
Open File Limits:
Linux systems need to have a minimum open file limit of 4096.
For SLES, add the following lines to the /etc/security/limits.conf file:
* hard nofile 65535
* soft nofile 4096
 
 
Environment Variables:
JAVA_HOME
Teaming must know the path and maker of the Java that is installed.  One method of doing this is to set the JAVA_HOME environment variable on the computer to the correct JDK path (this path may vary depending on which Java is installed).
For example:
On Linux: export JAVA_HOME=/usr/java/jdk_1.5.0_11
On Windows: JAVA_HOME=C:\Program Files\Java\jdk1.5.0_11
If you do not set the JAVA_HOME environment variable you will need to provide this information to Teaming during the installation.  You will receive a prompt requesting the path to the JAVA_HOME and if the maker is Sun or ibm.
Experience has shown that doing both (setting the environment variable and inserting during the installation) is useful.
 
PATH=
It is helpful but not required to add the Java JDK/SDK to the PATH statement.
Again, the actual path/directory may vary depending on which Java is installed.
For example:
On Linux: export PATH=$PATH:/usr/java/jdk_1.5.0_11/bin
On Windows: PATH=C:\Program Files\Java\jdk1.5.0_11\bin;C:\windows; etc....
 
NOTE: These setting will not last outside the terminal window or after a reboot.  To make them permanent they need to be added to configuration files.  For linux, they can be added to the /etc/profile.local file.  For Windows they are added to the System Environment Variables.
 
 
Other items to consider:
Access the Novell Teaming Installation Guide at https://www.novell.com/documentation
Under "Pre-Installation Steps" read through the sections on:
Database Planning, File System Planning, Network Planning, and Memory Guidelines.
 
 
Prerequisites for Conferencing:
 
Server:
Minimum Server Configuration
1.0 GHz Pentium P4
512 MB RAM
20 GB disk free
 
 
Server Operating System:
Each Conferencing server host must be running Linux, there is no Windows version.
SUSE Linux Enterprise Server (SLES) 10 SP1 (strongly recommended)
Red Hat Enterprise Server 4
NOTE: The 32bit versions have less issues currently than the 64bit and the 32bit SLES 10 SP1 is required (due to the NMS communications board driver) if doing VOIP at this time.
 
Required packages:
Before running the installer, the following packages and their dependencies need to be installed:
neon
postgresql
postgresql-libs
postgresql-server
Emacs
apache2
php5
 
NOTE 1: On SLES 10 SP1, all of these packages can be installed from Yast2, software management.
NOTE 2: The libneon and libpq libraries need to installed before running the installer. On SUSE Linux Enterprise Server (SLES) 10, these libraries are not installed on the system by default. The libneon library is inside the neon RPM. If installing on a 64-bit server, use neon-32bit and postgresql-libs-32bit to complete the install. These are contained in the postgresql RPM.
 
 
IP and DNS addresses:
Conferencing requires a minimum of three IP addresses with associated DNS names. If planning on adding the Voice Over IP capabilities of Conferencing then two more IP addresses and DNS names will be needed for a total of five.
NON-VOIP system:
One IP address and DNS name for each of the three services running: XML-router, Portal and Desktop/application Share.
Examples:
192.186.1.100 conf.yourcompany.com
192.168.1.101 confportal.yourcompany.com
192.168.1.102 confshare.yourcompany.com
NOTE: DNS resolution needs to be setup prior to the installation.  The HOSTS (linux:/etc/hosts) file on the server can be used for installation but clients will need to be able to resolve these names also, therefore the DNS server will need to be updated.
VOIP System:
To use the Voice Over IP capabilities of Conferencing, a minimum of two more IP addresses and DNS names will be required.  One for the VOIP service and one for the NMS Communications board.
Examples:
192.168.1.103 confvoip.yourcompany.com
192.168.1.104 confnms.yourcompany.com
 
 
Voice Over IP:
To use the VOIP capabilities of Conferencing, either just using the built in PC phone or integrating with a PBX, an NMS communications board must be installed and configured.  See http://www.nmscommunications.com/NovellTeamingConferencing/default.htm for more information.

Additional Information

When installing Teaming + Conferencing into a production environment then Teaming and Conferencing should be installed on separate servers.
If installing for evaluation or testing purposes then both can be installed on the same server.  The only conflict is that Conferencing will use Ports 80 & 443 and Teaming will need to be configured to use other ports.  This is not a problem as the default configuration of Teaming uses ports 8080 & 8443.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.