Home Home > 2009 > 01 > 21 > Novell Teaming on SLES
Sign up | Login

Novell Teaming on SLES

January 21st, 2009 by

As per the request of Andrew Wafaa, I thought I’d set up a quick guide to how I got teaming running on SLES.  The documentation for Teaming on the administrative end was relatively sparse, but the installation guide was sufficient for most purposes.

Read on to learn more about Teaming and SLES…

Documentation

Most of the Teaming documentation can be found here:  http://www.novell.com/documentation/team_plus_conf/

Prerequisites

  • SLES (our server platform)
  • OES2 (not entirely important, but it knocks out a lot of the pre-reqs and gives you LDAP support if you have eDirectory running)
  • Teaming Licenses (a “starter pack” of 20 free licenses is available, contact your Novell vendor for more information)
  • I’m assuming you’re running the setup from a Linux box, but this isn’t 100% necessary

Preparing your installation

There are a few things you need to do before getting started.  First being to install mysql:

# zypper in mysql mysql-client mysql-shared perl-DBD-mysql perl-DBI perl-Data-ShowTable libmysqlclient-devel

# chkconfig –add mysql

# /etc/init.d/mysql start

# mysql_secure_installation

Next, you’ll need to edit your /etc/my.cnf to change the default character set support.  Add the following lines to /etcmy.cnf:

[mysqld]
character_set_server = utf8
[client]
default_character_set = utf8

Additionally, you’ll need to increase your open file limits in /etc/security/limits.conf:

  • hard nofile 65535
  • soft nofile 4096

Installation

I like to run everything from a single location, so to kick things off, I created the directory ‘/incoming’.  Once there, you’ll need to download your copy of Teaming and extract it into this directory.

Once you’ve gotten everything extracted, download your license file and copy it to the same directory, but make sure that you rename it to “license-key.xml”.  The Teaming installer will complain to no end if it’s unable to find this exact file in the install root.

Next, you’ll need to make the installer executable:

# cd /incoming && chmod 755 installer-liferay.linux

Now it’s time to run the installer.  The installer comes as a GUI package, but can be run via a text interface as well.  If you’re ssh’ing into your server to set up Teaming, you’ll want to forward X to allow the GUI to open (ssh -X -C user@server.com).  Otherwise, use the ‘-console’ knob to initiate the text based installer.

# ./installer-liferay.linux

-or-

# ./installer-liferay.linux -console

I recommend choosing advanced options for install as it allows for greater flexibility in options.  Once you’ve followed through the installation steps (note, I installed mine copy into /opt/icecore), liferay/Teaming should be successfully installed.  Now you’ll need to start the server:

# /opt/icecore/liferay-portal-tomcat-5.5-jdk5-4.3.0/bin/icecore start

To ensure that Teaming starts on boot, issue the following commands:

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

# chkconfig –add icecore

After that, you should be able to start, stop, and restart ‘icecore’  using the /etc/init.d/icecore script.

At this point, Teaming should be up and running.  To access it and get started, open your browser and navigate to http://yourserver.com:8080 and log in as user admin with the password ‘admin’ (no quotes).

Once logged in, you’ll need to pull the administrative modules down to your view by selecting the ‘Add Content’ option in the upper right hand corner.  I like to use the shotgun method and add all of the administrative modules for my admin user.

So there you have it, a fresh Teaming install.  Enjoy!

Both comments and pings are currently closed.

Comments are closed.