23.2 Meeting Novell Teaming System Requirements on OES 2 or SLES 10 SP1 Servers

Prerequisites in the Novell Teaming 1.0 Installation Guide lists the standard system requirements for Novell Teaming. If you are installing Teaming on Novell Open Enterprise (OES) 2 or SUSE Linux Enterprise Server (SLES) 10 SP1, a default operating system installation does not meet these system requirements. The following sections explain how to update an OES 2 or SLES 10 SP1 server so that it meets the Teaming system requirements:

23.2.1 Linux Open File Limit

The default limit on the number of open files on SLES 10 is not sufficient for Novell Teaming.

To configure SLES 10 with an appropriate open file limit:

  1. Edit the /etc/security/limits.conf file in an ASCII text editor.

  2. Add the following lines to the bottom of the list, following the format of the example lines:

    *    hard    nofile    65535
    *    soft    nofile    4096
    
  3. Save the file, then exit the text editor.

23.2.2 Java Development Kit Requirement

In Prerequisites in the Novell Teaming 1.0 Installation Guide states that Teaming requires Sun Java Development Kit (JDK) 1.5.0_11 or IBM JDK 1.5. A JDK is not provided with OES 2 or SLES 10 SP1. You must install a JDK on your Linux server before you install Teaming.

IMPORTANT:Make sure you download the JDK, not the Java Runtime Environment (JRE).

  1. Go to the following URL:

    Java SE Downloads - Previous Release

    The update you need is listed as “JDK 5.0 Update nn.”

  2. Click Download next to this update.

  3. In the Platform field, select Linux.

  4. Select I agree..., then click Continue to accept Sun’s License Agreement.

  5. Select Linux RPM in Self-Extracting File, then save the file to an empty temporary directory on your Linux server.

  6. As the root user, change to that temporary directory, then use the following command to make sure that the download arrived safely:

    ls -l
    

    You should see a file named jdk-1_5_0_nn-linux-i586-rpm.bin.

  7. Change the permissions on the file to include execute permissions:

    chmod +x jdk-1_5_0_nn-linux-i586.bin
    
  8. Run the self-extracting file:

    ./jdk-1_5_0_nn-linux-i586-rpm.bin
    

    This creates a file named jdk-1_5_0_nn-linux-i586.rpm, and a directory named /usr/java/jdk1.5.0_nn.

    The Sun JDK is now installed and configured on your Linux server. The Teaming installer asks for the JDK directory.

If you would prefer to use the IBM JDK, refer to the IBM developerWorks Web site.

23.2.3 MySQL Setup

Although MySQL is installed by default on OES 2 and SLES 10 SP1, it is not configured with a password, nor is it configured to start automatically. Follow the steps below to set up MySQL for use with Novell Teaming:

  1. In YaST, click System > System Services.

  2. Select the MySQL service, then click Enable.

  3. Click Finish, then exit YaST.

  4. In a terminal window, become the root user.

  5. To verify that MySQL has started, use the following command:

    ps -eaf | grep mysql
    

    You should see MySQL processes running.

  6. Set the MySQL root password:

    mysqladmin -root password root
    

    This sets the password for the MySQL root user to root, which matches the default MySQL configuration in the Teaming installer.

The following are some basic and useful MySQL commands:

Action

Command

Stop MySQL

/etc/initd/mysql stop

Start MySQL

/etc/initd/mysql start

Show MySQL status

mysqladmin -r root -p extended-status

If you would like to administer MySQL using a GUI interface, you can download tools from:

MySQL GUI Tools Downloads

For more information about MySQL, see:

MySQL Documentation

23.2.4 Potential Web Server Port Conflicts

Novell Teaming includes its own Web server. If the Linux server where you plan to install Novell Teaming already has a Web server on it, make sure that you specify different, unique port numbers when you install Novell Teaming or remove the existing Web server from the Teaming server. Teaming does not start successfully if another Web server is already running on the Teaming server using the same port numbers.