When you perform a Basic installation, the Novell Teaming Installation program needs hostname and HTTP port information about the server where you are installing Teaming.
When you install Novell Teaming, the Teaming installation program needs to know the name of the server where you are installing the Teaming software. The default is localhost. Do not use the default.
For internal use, you can use the DNS hostname of the Teaming server. However, if you want your Teaming site to be accessible from the Internet, you must specify the fully qualified domain name for the Teaming server in order to allow external access.
When you install Novell Teaming, Tomcat is installed along with the Teaming software. Teaming uses Tomcat as a standalone Web server for delivering data to Teaming users in their Web browsers. For more information about Tomcat, see the Apache Tomcat Web site.
IMPORTANT:If the server where you want to install Teaming already has a Web server running on it, shut it down while you install and test Teaming. The instructions for a Basic Teaming installation assume that no other Web server is running on the Teaming server. If you want to maintain another Web server on the Teaming server, you are responsible to resolve any port conflicts that might arise.
On the command line, use the netstat command to see what ports are currently in use on the server where you plan to install Teaming:
Make sure that the port numbers that you specify during Teaming installation do not conflict with ports that are already in use on the server.
By default, standard Web servers such as Apache and Microsoft Internet Information Server (IIS) use port 80 for non-secure HTTP (Hypertext Transfer Protocol) connections and port 443 for secure HTTPS connections. HTTPS connections use SSL (Secure Sockets Layer) for added security. As a result, Web browsers default to port 80 when no port is specified in a non-secure HTTP URL and to port 443 when no port is specified in a secure HTTPS URL.
Tomcat defaults to port 8080 for non-secure HTTP connections and to port 8443 for secure HTTPS connections, so that it does not conflict with the standard Web server port numbers. If you configure Novell Teaming with the Tomcat default port numbers, users must include the appropriate port number when providing the Teaming site URL. Typically, users prefer not to do this.
Unfortunately, the situation is not as simple as just configuring Teaming to use the default port numbers of 80 and 443. On Linux, non-root processes are not allowed access to port numbers lower than 1024 and you are counseled against running Teaming as root in Section 3.8.2, Linux User ID for Teaming. Also on Linux and Windows, the default Tomcat installation expects ports 8080 and 8443.
For a Basic installation, you can use the default port numbers as presented by the Teaming Installation program:
After you install Teaming on Linux, you need to complete the steps in Setting Up Port Forwarding so that users are not required to include the port number in the Teaming URL.
If you want to use secure HTTPS connections for your Teaming site, you must obtain signed certificate files as described in Preparing for Secure HTTP Connections
in Site Security
in the Kablink Teaming 2.1 Administration Guide either before or after you install Teaming.
By default, Novell Teaming uses 8005 as its shutdown port. For an explanation of the shutdown port, see Tomcat - Shutdown Port.
By default, Novell Teaming uses 8009 as its AJP port. For an explanation of the Apache JServ Protocol port, see The AJP Connector.
IMPORTANT:If you are installing Teaming on Novell Open Enterprise Server 2, port 8009 is already in use, so you need to select a different port (for example 8010).