Novell Doc: Kablink Teaming 2.0 Installation Guide - Windows: Setting Up a Basic Teaming Site

4.2.1 Performing Pre-Installation Tasks on Windows

Make sure that the Windows server where you plan to install Kablink Teaming meets the system requirements listed in Section 2.1, Teaming Server Requirements.
If a Web server is currently running on the Teaming server, stop it, and preferably disable it.

For example, to stop and disable the Internet Information Services (IIS) Web server:
1. On the Windows desktop, click Start > Administrative Tools > Services.
2. Right-click World Wide Web Publishing Service, then click Properties.
3. In the Startup type drop-down list, select Disabled.
4. Click Stop, then click OK.
Make sure that the Windows PATH environment variable includes the path to your database server.
1. Right-click My Computer, then click Properties.
2. On the Advanced tab, click Environment Variables.
3. In the System Variables list, locate the PATH environment variable.
4. If the path includes your database server software directory, click Cancel.
  
  or
  
  If the path does not include your database server software directory, add the directory, then click OK.

4.2.2 Running the Windows Teaming Installation Program

Log in to the Windows server as a user with Administrator rights.
In Windows Explorer, browse to the directory where you downloaded and extracted the Kablink Teaming software.
Double-click the installer-teaming.exe file to start the Teaming Installation program.
Accept the License Agreement, then click Next.
Click Next to accept the default of New installation.
Click Next to accept the default of Basic.
Use the information that you have gathered on the Basic Teaming Installation Summary Sheet to provide the information that the Teaming Installation program prompts you for:
- Installation Locations
- Default Locale for Kablink Teaming
- Network Information
- Database Selection
- Database Type
- JDBC URL
- Credentials
- Setup
- Encryption Algorithm
- Java JDK Location
- Outbound E-Mail Configuration
- Protocol
- Host, Port, and Time Zone
- Username, Password, and Authentication
- Allow Sending E-Mail to All Users
- Inbound E-Mail Configuration
The Installation program stores the information it gathers in the installer.xml file in the same directory where you started the Installation program.
After you have provided all the requested information, click Install to begin the Teaming installation.
When the installation is completed, click Finish to exit the Teaming Installation program.

Information about the installation process is written to the installer.log file in the same directory where you ran the Installation program. If a problem arises during the installation, the installer.log file provides information that can help you resolve the problem.
Continue with one of the following sections, depending on how you want to run the Teaming software:
- Section 4.2.4, Running Teaming as a Windows Service
- Section 4.2.5, Running Teaming as a Windows Application

4.2.3 Configuring the Document Converter on Windows

Kablink Teaming uses OpenOffice.org converters to prepare documents for indexing by the Lucene Index Server. The OpenOffice.org converters are also used on the Teaming site for viewing documents (by converting them to HTML).

Installing OpenOffice.org as the Document Converter for Teaming

Download the OpenOffice.org software for Windows from OpenOffice.org to a convenient temporary location on the Teaming server.
Run the downloaded executable, then click Next to unpack the OpenOffice.org software.
Browse to or select the destination directory for the unpacked files, then click Unpack.

This starts the OpenOffice.org Installation program.
Click Next to begin the installation.
Provide your customer information, then click Next.
Select Custom, then click Next.
In the Optional Components drop-down list, select This feature, and all subfeatures, will be installed on local hard drive, then click Next.

This includes the OpenOffice.org Java Runtime Environment (JRE) and other components required for document conversion.
Click Install.

The OpenOffice.org software is installed to:

c:\Program Files\OpenOffice.org 3
Click Finish.
Continue with Configuring OpenOffice.org for Proper HTML Conversion.

Configuring OpenOffice.org for Proper HTML Conversion

Start OpenOffice.org from the desktop.
Proceed through the Welcome pages.
Click Tools > Options.
Expand Load/Save, then click HTML Compatibility.
In the Character Set field, select Unicode (UTF-8).
Click OK to save the character set setting, then exit OpenOffice.org.
Continue with Running OpenOffice.org as the Document Converter for Teaming

Running OpenOffice.org as the Document Converter for Teaming

OpenOffice.org must be running as a background process on the Teaming server in order for indexing and viewing to take place for Teaming users.

Edit the properties of the OpenOffice.org desktop icon so that the Target field includes the following additional options:

"C:\Program Files\OPenOffice.org 3\program\soffice.exe" 
                            "-accept=socket,host=localhost,port=8100;urp;
                              StarOffice.ServiceManager" 
                             -nologo -headless

Double-click the OpenOffice.org desktop icon to start OpenOffice.org as a background process.

IMPORTANT:Run OpenOffice.org as a user that has full rights to the Teaming file repository.
Use Windows Task Manager to observe that the soffice.exe and soffice.bin processes are running.
Test HTML conversion on your Teaming site by viewing a document that has been added as a File Entry in your Teaming site.
Configure the Teaming server so that OpenOffice.org is always running as a background process whenever Teaming is running.

4.2.4 Running Teaming as a Windows Service

Configuring Teaming as a Windows Service

The Kablink Teaming Installation program created a service.bat file for configuring Teaming to run as a Windows service.

In a Command Prompt window, change to the following directory:

c:\Program Files\Novell\Teaming\apache-tomcat-version\bin

where version is the version number of Tomcat that was installed along with Teaming (for example, 6.0.18).
Use the following command to configure Teaming as a Windows service:
```
service.bat install Teaming
```
This creates a service named Apache Tomcat Teaming.

Starting Teaming as a Windows Service

On the Windows desktop, click Start > Administrative Tools > Services.
Right-click Apache Tomcat Teaming, then click Start.

Configuring the Teaming Service to Start Automatically on Reboot

When you run Kablink Teaming as a Windows service, you can configure Teaming to start automatically each time you reboot the Windows server.

On the Windows desktop, click Start > Administrative Tools > Services.
Right-click Apache Tomcat Teaming, then click Properties.
In the Startup type drop-down list, select Automatic, then click OK.

Restarting the Teaming Service

You need to restart Kablink Teaming whenever you use the Teaming Installation program to make configuration changes, as described in Section 9.0, Performing an Advanced Teaming Installation.

On the Windows desktop, click Start > Administrative Tools > Services.
Right-click Apache Tomcat Teaming, then click Restart.
Close the Services window.

Stopping the Teaming Service

On the Windows desktop, click Start > Administrative Tools > Services.
Right-click Apache Tomcat Teaming, then click Stop.
Close the Services window.

4.2.5 Running Teaming as a Windows Application

Starting Teaming as an Application

The Kablink Teaming Installation program created a startup.bat file for starting Teaming.

In a Command Prompt window, change to the following directory:

c:\Program Files\Novell\Teaming\apache-tomcat-version\bin

where version is the version number of Tomcat that was installed along with Teaming (for example, 6.0.18).
Run the startup.bat file to start Teaming as an application.

Stopping Teaming as an Application

In a Command Prompt window, change to the following directory:

c:\Program Files\Novell\Teaming\apache-tomcat-version\bin

where version is the version number of Tomcat that was installed along with Teaming (for example, 6.0.18).
Run the shutdown.bat file to stop the Teaming application.

4.2.6 Uninstalling Teaming

If you move the Kablink Teaming site to a different server, you can delete the Teaming files from the original server to reclaim disk space. The default Teaming file locations are:

Teaming Software	c:\Program Files\Novell\Teaming
Teaming File Repository	c:\Novell\Teaming
MS SQL Database	c:\Program Files\Microsoft SQL Server\MSSQL\Data

For a complete list of your Teaming files, check the installer.xml file in the directory where you originally ran the Teaming Installation program.

4.2 Windows: Setting Up a Basic Teaming Site