Installing Novell Teaming 1.0.3 on SLES 10 SP2

Novell Teaming is a product that leverages modern day communication. It's main focus is to create a platform that makes working together and sharing information more effective & efficient, even when you're not in the same room, building or working at different times.

You can get a full working starter pack that can be used up to 20 users (unlimited time). Get it here!. You will also find more information on possibilities and what Novell Teaming can do for you.

Here's how to get your first setup running on a SLES 10 SP2 server.

* SLES 10 can also be installed and used free of charge. You will get free updates for 60 days after which you will need a support contract to be able to update using the Novell channel.
Do note that the product does not expire nor lose any functionality. You will only lose the right for support & updates until you acquire a support contract from Novell.

SLES 10 SP2 base:

Setup a basic SLES 10 SP2 system. No eDrectory or extra services are needed.

NOTE: You will need a minimum of 2GB of memory for production systems! 1 GB should suffice for a test environment.
Also if running with more then 2GB of RAM, only use 64bit versions of SLES & Java.

Preparing for the Teaming installation:

* All console commands must be run as root.

After having run the SLES setup, install these extra packages:

mysql (note: don't use version 5.1 as it's not supported yet)

Download Sun's java JDK 5.0 Update 16, you can find it here.
(NOTE: jdk 1.5 = 5.0, get the jdk-1_5_0_xx-linux.rpm.bin package found under JDK 5.0 Update xx)
* Java 6.0 (1.6) is not supported and not recommended!

Extract & install the jdk by running it as script in a console:

sh jdk-1_5_0_xx-linux.rpm.bin

MYSQL setup

Now we need to start and configure the MySQL server & DB and set it to start at boot.

chkconfig mysql on
service mysql start

to set MySQL root password:

/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h [servername.domain] password 'new-password'

Create a Novell Teaming daemon user:

Using YaST > User Management, create a normal user account that will be used to run the teaming daemon with, e.g. we create a user runteaming.

Check for the latest updates:

(Make sure you have run YaST > Novell Customer Center. This adds the SLES 10 update repository giving you the latest packages)

Run YaST > Online Updates one last time to check for the latest updates, reboot and check if all services (mysql) started ok.

Set the minimum open file limit:
edit /etc/security/limits.conf

Add the following lines to the end of the file:
* hard nofile 65535
* soft nofile 4096

Install the teaming packages:

Unzip the downloaded from Novell and cd into the directory the files have been unzipped in.

Copy your license file to the install directory and rename it to license-key.xlm (you can obtain it through the link to Novell mentioned at the beginning).

Rename the sample-installer.xml to installer.xml (or use a previous/custom xml file if you have one).

Grant the executable right to the install script:

chmod +x installer-liferay.linux

export JAVA_HOME path to point to the installed jdk

export JAVA_HOME=/usr/java/jdk1.5.0_16
* to make this setting persistent, add the above command to /etc/profile.local

Now run the installer (must be run in a console within X):

(an installer GUI should pop up!)

A walk through installer specifics:

Choose a new install & accept license agreement

Both basic and Advanced setups are fine, but go for Advanced setup to give an idea of what can be configured. If you don't know what to set, stick with the defaults.
*Don't change the default http/https ports. We'll get back to this later.

User and Group ID:
Set the userid to the created user account , in this example runteaming
Leave the groupid blank

MySQL details
Just enter the DB password you've set, leave the user set to root and keep suggested defaults.

Note: When the installer states the Java path make sure it states /usr/java/jdk1.5.0_16

Enter your mailserver (smtp and pop) details

-the installer will now finish the installation-

Starting the Teaming services:

We can start the service bij opening a console

/opt/icecore/liferay-portal-tomcat-5.5-jdk-4.3.0/bin/icecore start

Check if the server has started successfully:
tail -f /opt/icecore/liferay-portal-tomcat-5.5-jdk-4.3.0/logs/catilina.out

After a minute or so the log output should state 'server stated in'

congratulations!! Now you can open a browser to http://[server name or ip]:8080

Default username : admin / password admin

Paths of interest (if using the defaults):

/opt/icecore - program files
/home/icecoredata - file system location

Post install tasks:

Redirecting 8080 and 443 to port 80/443:

Seeing we don't want the teaming daemon running as root (not the safest thing to do) a side effect is that we can't let the daemon run on the standard http/https ports (just one of the security rules as root is only allowed to use lower ip ports).
To work around this we can use iptables to forward ports 80 and 443 to 8080 and 8443. This way you will be able to access the teaming site on 8080/8443 and 80/443.
Make sure no other services will be using port 80. If you've sticked to setting up as done here, no service should.

Redirect port incoming traffic on port 80 to 8080:

iptables -t nat -A OUTPUT -d localhost -p tcp --dport 80 -j
REDIRECT --to-ports 8080
iptables -t nat -A OUTPUT -d [yourHostname or ip] -p tcp --dport 80 -j
REDIRECT --to-ports 8080
iptables -t nat -A PREROUTING -d [yourHostname or ip] -p tcp --dport 80 -j
REDIRECT --to-ports 8080

Redirect port incoming traffic on port 443 to 8443:

iptables -t nat -A OUTPUT -d localhost -p tcp --dport 443 -j
REDIRECT --to-ports 8443
iptables -t nat -A OUTPUT -d [yourHostname or ip] -p tcp --dport 443 -j
REDIRECT --to-ports 8443
iptables -t nat -A PREROUTING -d [yourHostname or ip] -p tcp --dport 443 -j
REDIRECT --to-ports 8443

NOTE: You will lose this redirect rule when rebooting. You could make a script that gets run at boot or see the iptables man on saving these settings.

Set Novell Teaming to start as service:

1) Copy the start script to the inid.d directory:

cp /opt/icecore/liferay-portal-tomcat-5.5-jdk5-4.3.0/bin/
icecore /etc/init.d

2) Add the start script as service and set it to start at boot:

chkconfig --add icecore
chkconfig on

Happy Teaming!

Thank you

Thaks you Sir ! !

This Document is much superior than Novell's Document ...

U made my day ! ! !


Thank you

Incredibly excellent how-to! Thanks!

No automatic startup

How do I get /etc/init.d/icecore to start up automatically on startup? Each time I reboot the server I have to manually bring it up.

what does chkconfig say?


Did you also follow/see the last bit of this setup guide, 'Set Novell Teaming to start as service'?

If you have copied the script to /init.d you should be able to add it as service using chkconfig -add.

What does ' chkconfig icecore ' tell you? Is the service added and set to on?



I would like some straightforward instructions on customizing the login page. Any words of wisdom?


Not to many options within the web administration... (yet)

Hi David,

sorry for the late reply as I was away...

Depends on what you would like to customize.

I've done some easy adjustments by first logging in as admin and then reverting back to the welcome/login page.
Having admin rights lets you customize some bits of the page as also the default theme that will be used.

Also you can change the default logo (upper left) by editing the file teaming_logo.gif found in

As far as I know customizing the login page further would require diving into the theme files and 'hack' directly in there.

From what I've seen from Teaming 2.0 the front end is pimped up and seems to have more options for this.

You can also drop a post in the Novell forums to see if others have options for this or other themes can do the trick. ( )



Willem, thanks for such a detailed tutorial.
I am almost there! :)

I have one issue though, I cannot see Teaming Across the network. I type in a browser:
I get a not found error.

On the local SLES10 box, I can see it with no problems.

If you can give me any advice I would really appreciate it.


You're welcome!!

Hi Nemuel,

Glad you found it useful and also that you where able to follow it. ;)

As for not being able to reach the site over the network, is the firewall enabled? If so you probably need to open port 8080.

Hope that sorts it,