In order to successfully install Teaming 2.0, you need to understand the Teaming system requirements and the system environment where you are installing the Teaming software. For your convenience, the Teaming Installation program includes many default settings that can be accepted during a typical Basic installation.
The Basic installation shown in this demonstration assumes that the Teaming software, the database server, and the data indexing server are all installed on the same physical server. Other configurations are possible when you perform an Advanced installation.
This demonstration uses the company name of Greenergy Power, a fictional company that operates in the green power space. Its corporate Internet domain name is greenergy.com.
The Teaming 2.0 software can run on a 32-bit processor or a 64-bit processor. Use a 64-bit processor for a large Teaming site. A 32-bit processor is adequate for a small to medium Teaming site.
You can run Teaming 2.0 on Linux or Windows. If you prefer Linux, you can choose the Linux version of Novell® Open Enterprise Server 2 or you can use SUSE® Linux Enterprise Server 10 or 11. If you prefer Windows, you can choose Windows Server 2003 or 2008.
Teaming 2.0 supports three types of database servers. On both Linux and Windows, you can use MySQL or Oracle. On Windows, Microsoft SQL is also supported.
Teaming can import user information from two directory services, eDirectory™ or Active Directory:
Teaming also requires a Java Developer Kit or “JDK”. You can use the JDK from Sun or from IBM.
Complete system requirements are listed in the Teaming 2.0 Installation Guide.
For your convenience, the Teaming Installation Guide provides a summary sheet where you can gather the system requirements and system environment information that the Teaming Installation program prompts you for.
This demonstration presents the planning, setup, and testing of a Teaming site where the Teaming software is being installed on a Novell Open Enterprise server with a 32-bit processor and 4 GB of memory. The MySQL database server and the Sun JDK have already been installed and configured.
For security reasons, it is highly recommended that you do not run Teaming as the Linux root user. You might want to create a teamingadmin Linux user to run the Teaming software and a teamingadmin Linux group for this user to belong to.
If you are familiar with the wwwrun user and the and the www group in SUSE versions of Linux, you can use those, rather than creating a new Linux user and group for Teaming. The wwwrun user is typically used to run the Apache Web server and is therefore a good candidate for running Teaming.
If you decide to create a user and group, it’s easiest if you create the Teaming Linux group first. The group does not need a password.
Next, you create the Teaming Linux user. This user should be configured withselected, because you want it to be like a system user. The Teaming Linux user does not need a password, but YaST requires you to provide one.
To make this user as much like a system user as possible, you need to change two settings on the teamingadmin group you created. Then click . YaST does require you to provide a password before it will add the user. You can avoid that annoyance by creating the user and group on the command line, if you’d prefer.tab. In the drop-down list, select , because you don’t ever log in as this user. In the Default Group drop-down list, select the
When the Teaming Installation program installs the Teaming software and creates the Teaming data store, the directories and files are created with teamingadmin user and group ownership and permissions. In addition, the teaming startup script is customized to start the Teaming software as the teamingadmin user.
Before you start the Teaming Installation program, be sure to complete the following tasks:
If a Web server is already running on the Teaming server, stop it. Teaming includes Tomcat as a standalone Web server.
Create the Linux user and group for Teaming, or make sure that you know the password for the wwwrun user.
Increase the Linux open file limits to meet the needs of Teaming. The default file limits are insufficient.
When you have the prerequisites in place, you can start the Teaming Installation program.
In a terminal window on the Linux server, change to the Linux root user, then provide the root password. root permissions are required to install the Teaming software, but should not be used when you run the Teaming software.
Next, change to the directory where you downloaded and extracted the Teaming software. In this demonstration, we use /home/teamingsoftware.
Now use the following command to start the Teaming Installation program.
Accept the License Agreement, then click.
Again, clickto accept the default of .
Ainstallation gets your Teaming site installed and running as quickly and easily as possible, so click once again to accept the default of a Basic installation.
In a Basic installation, you can choose where you want to install the Teaming software and where you want to create the Teaming data store. The Teaming data store holds files that you import into your Teaming site, plus information associated with those files, such as thumbnails and HTML renderings, and the data search engine index. This means that the Teaming data store is a big consumer of disk space. In this demonstration, go ahead and click /opt/novell/teaming and /var/opt/novell/teaming.to accept the default locations of
Because you shouldn’t run Teaming as the Linux root user, you provide a non-root user and group, then click .
Ensuring that the network information is correctly specified is a very important part of the Teaming installation process. The hostname of the server where you install Teaming is required in order for other programs, such as the GroupWise® Windows client, to access the Teaming site. The HTTP port and the secure HTTP port are the port numbers that your Web browser expects to use when no port is specified in a URL. When you use the default HTTP ports of 80 and 443, users do not need to include the port number when they provide the Teaming site URL in their Web browsers.
The listen port and the secure listen port are the port numbers that Teaming uses internally for Tomcat to listen on. Because Teaming runs as a non-root user, it cannot access port numbers less than 1024. After installation, you set up port forwarding, so that when a Web browser sends a request to port 80 or 443 by default, the request is automatically forwarded to Teaming on listen port 8080 or 8443. A default certificate is provided for use with the secure ports. The Teaming Installation program fills in the correct defaults, so click to continue.
As mentioned earlier, you can use MySQL or Oracle on Linux. For this demonstration, we use the default of MySQL.
The JDBC URL enables Teaming to locate the MySQL database server. Because the database server is on the local server in this demonstration, we can keep the default of localhost. For the MySQL database server credentials, the Teaming Installation program uses root as the database server username, because that is the standard default username for MySQL. Be aware that the MySQL root username is not the same as the Linux root user.
You or your database administrator must set the database server password when you install MySQL, because the Teaming Installation program needs the database server password. When you perform a Basic installation, the easiest approach is to let the Teaming Installation program create the initial database for you. Specify the database server password, then click.
Unless you have already set the JAVA_HOME environment variable in the terminal window where you started the Teaming Installation program, you need to browse to and select the directory where you installed the JDK, then click.
E-mail messages can be sent from the Teaming site for several reasons.
Teaming users can subscribe to e-mail notifications, so they automatically receive a message whenever a workspace or folder changes.
From the Teaming site, users can send e-mail messages to individual users or to teams.
If your e-mail client is iCal-enabled, appointments created in a Teaming Calendar folder can be sent to your e-mail client for posting in your e-mail client Calendar.
Teaming includes basic SMTP mail host functionality. Teaming can use either SMTP or secure SMTP to send outbound messages. In order to send messages, Teaming needs to know some information about an existing SMTP mail host.
In thefield, specify the fully qualified hostname of a server where the GroupWise Internet Agent is running. Teaming can also be configured to use Microsoft Exchange or Lotus Notes as its e-mail system.
In the teamingadmin.field, specify the e-mail address of a valid GroupWise user. You might want to create a separate GroupWise account for receiving e-mail from the Teaming site, for example,
What you put in theand fields when you install Teaming depends on the requirements of your e-mail system. Authentication might or might not be required. Now, click to continue.
By enabling inbound e-mail, you enable users to post to Teaming folders from their e-mail clients for folders that have been configured with e-mail addresses. The default configuration information provided by the Teaming Installation program is typically appropriate, so you can enable inbound e-mail, then click.
The Installation program now has all the information it needs, so you can click.
Installation takes only a few seconds.
When the installation is complete, review the instructions about what to do next., then click.
Next, you need to enable port forwarding, so Teaming users don’t need to include a port number with the Teaming URL. The easiest way to enable port forwarding for SUSE Linux is by editing the SuSEfirewall2 file.
In the SuSEfirewall2 file, find the line you need by searching for REDIRECT. Remember to match the case.
The first instance is the one you want.
The Teaming Installation Guide provides a sample string that you can paste between the double quote marks on the FW_REDIRECT line. Now we just need to change the ip_address variable to the IP address of the Teaming server.
Now save the changes and exit the text editor to return to the command line.
After editing the SuSEfirewall2 file, the firewall must be restarted.
You see some status messages indicating that the firewall has restarted successfully.
Next, you use the iptables-save command to show that the ports have been successfully redirected. On other types of Linux besides SUSE Linux, iptables commands can be used to accomplish the same result.
Log out as the Linux root user. Now, you can start Teaming. You are prompted for the password of the Teaming administrator user.
Some Tomcat status messages show that Teaming has started.
In a Web browser on a workstation, provide the Teaming site URL, which is simply the hostname of the Teaming server. Thanks to port forwarding, you don’t need to include a port number.
The first time you log in, you use admin as the username and admin as the password.
The personal workspace for the Teaming administrator appears.
You should immediately reset the admin password. Click Modify Profile, then provide your own password for the admin user. You can give your Teaming administrator user a name as well. Then click .
Now, let’s create a new Teaming user. Start by clicking. Of course, this approach is appropriate only for a very small Teaming site, but we’ll show you how to create multiple users in a minute.
For the single user, provide a username, password, first name, last name, and e-mail address, then click.
Now we’ll show you how to add users from an existing directory service such as Novell eDirectory or Microsoft Active Directory. To create Teaming users based on a directory service, LDAP authentication is used to obtain user information from the directory. Again, click, but this time, click .
In order to fill in the fields on this page, you need to gather the following information about your directory service:
The URL of the LDAP server where your directory service is located, including the port number on which Teaming can communicate with your directory service.
The username and password that Teaming can use to access the directory service, in the format expected by the directory service (for example, cn=admin,ou=users,o=greenergy).
The LDAP attribute that your directory service uses for usernames. eDirectory and Active Directory both use cn.
A directory context where Teaming User objects are located (for example, ou=users,o=greenergy).
You also need to make some decisions about how you want LDAP synchronization to work, such as when to perform synchronization and what specifically to synchronize. The Teaming Installation Guide helps you decide how to configure LDAP to meet the needs of your Teaming site.
After you have installed the Teaming software and created Teaming user accounts, you are ready to set up your Teaming site.