Ts 671sp1 Install Unix v01 en

TeamSite ®
Installation Guide
Release 6.7.1
Service Pack 1
UNIX
®
© 2003-2007 Interwoven, Inc. All rights reserved.
No part of this publication (hardcopy or electronic form) may be reproduced or transmitted, in any form
or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior
written consent of Interwoven. Information in this manual is furnished under license by Interwoven, Inc.
and may only be used in accordance with the terms of the license agreement. If this software or
documentation directs you to copy materials, you must first have permission from the copyright owner
of the materials to avoid violating the law which could result in damages or other remedies.
Interwoven, ConfirmSite, ControlHub, DataDeploy, DeskSite,FileSite, iManage, LiveSite, MediaBin,

MetaCode, MetaTagger, OffSite, OpenDeploy, Primera, TeamPortal, TeamSite, VisualAnnotate,
WorkDocs, WorkPortal, WorkRoute, WorkSite, WorkTeam, the respective taglines, logos and service
marks are trademarks of Interwoven, Inc., which may be registered in certain jurisdictions. All other
trademarks are owned by their respective owners. Some or all of the information contained herein may
be protected by patent numbers: US # 6,505,212, EP / ATRA / BELG / DENM / FINL / FRAN / GBRI /
GREC / IREL / ITAL / LUXE / NETH / PORT / SPAI / SWED / SWIT # 1053523, US # 6,480,944,
US# 5,845,270, US #5,384,867, US #5,430,812, US #5,754,704, US #5,347,600, AUS #735365, AU
7830068, GB #GB2333619, US #5,845,067, US #6,675,299, US #5,835,037, AUS #632333, CAN
#2,062,965, FRAN / GRBI / SPAI / SWED #480941, GERM #69020564.3, JAPA #2968582, MX
#219522, NZ #516340, SG #89006, SG #89086,# SG #74973, SG #85502 US #5,065,447, US
#6,609,184, US #6,141,017, US #5,990,950, US #5,821,999, US #5,805,217, US #5,838,832, US
#5,867,221, US #5,923,376, US #6,434,273, US #5,867,603, US #4,941,193, US #5,822,721, US
#5,923,785, US #5,982,938, US #5,790,131, US #5,721,543, US #5,982,441, US #5,857,036, US
#6,697,532, US #6,792, 454, US# 6,928,149, GERM #69902752.7 or other patents pending application
for Interwoven, Inc.
Interwoven, Inc.
160 East Tasman Drive
San Jose, CA 95134
http://www.interwoven.com
Printed in the United States of America
TeamSite Installation Guide

Part 01-009-01-EN
August 2007
Table of Contents
About This Guide 11
Notation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Online Documentation Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Chapter 1: Installation Prerequisites 13
Server Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
CPUs and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
System Running Just the TeamSite Server . . . . . . . . . . . . . . . . . . . . . . . . . . .15
System Running Just the Interwoven Search Server . . . . . . . . . . . . . . . . . . . .16
System Running the TeamSite and Interwoven Search Servers . . . . . . . . . . .16
Inodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Disk Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Connecting Through the File System Interface . . . . . . . . . . . . . . . . . . . . . . . . . .17
Chapter 2: Installing TeamSite 19
Installing a Service Pack Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Installation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
TeamSite and Search Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Installing the TeamSite Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Installing the Search Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Installing a Base Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Required Linux Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Required Solaris Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
TeamSite Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
What Gets Installed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
TeamSite Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Default File Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Retaining Essential Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Installation Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Module Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Product Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
TeamSite Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Password Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Interwoven Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Installing ReportCenter as a Standalone Module. . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Required Input for TeamSite and Search Installations. . . . . . . . . . . . . . . . . . . . . . . .28
TeamSite Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Search Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Installing TeamSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Installing Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Installing Using Graphical Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
TeamSite Installation Guide 3

Contents
Installing Interwoven Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Enabling Incremental Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Installing Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Installing Using Graphical Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Licensing TeamSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Troubleshooting Licensing Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Upgrading from a Pre-6.7.1 TeamSite Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
If Search is Installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Changes to iw.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Upgrade Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Post-upgrade Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Workflow Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Content and Permission Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Web Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Perl Scripts and Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Uninstalling TeamSite and Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Service Pack Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Base Release Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
TeamSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Chapter 3: Configuring Web Servers 87
Interwoven Web Server Port Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Configuring the iw-mount Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Configuring iw-mount for iPlanet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Configuring iw-mount for Apache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Configuring CGI Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Enabling Server-Side Include Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Installing the Redirector Module for iPlanet . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Installing the Redirector Module for Apache . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Web Server Plug-ins and VisualPreview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
NSAPI Plug-ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Apache Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Custom Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Stopping and Restarting the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Redirecting NSAPI HTTPS Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Redirecting to an Index Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Chapter 4: Configuring Samba 97
Editing the iw.smb.conf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Troubleshooting Samba. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Chapter 5: Configuring TeamSite Clients 101
Accessing TeamSite Using the Graphical User Interface . . . . . . . . . . . . . . . . . . . .101
Installing Local File Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Viewing Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Accessing TeamSite Using the File System Interface . . . . . . . . . . . . . . . . . . . . . . .103
Windows Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Creating Shortcuts from Windows Clients . . . . . . . . . . . . . . . . . . . . . . . . . .104
Interwoven, Inc. 4
Contents
Troubleshooting Windows Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

Configuring PDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
NFS Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
FTP Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Macintosh Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
UNIX Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
FormsPublisher Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Chapter 6: Loading Content Files 109
Creating a Content Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Content Store Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Supported File Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Creating Multiple Content Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Defining Content Stores in the iw.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Creating Content Stores using a CLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Viewing Content Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Creating a Subbranch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Creating a Workarea . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
Populating the Initial Workarea. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Submitting Files to the Staging Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Publishing an Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
The ContentCenter Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Displaying Workareas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Displaying Workarea Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Clicking on Workarea Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Displaying Forms in the New Forms Module . . . . . . . . . . . . . . . . . . . . . . . . . .121
Displaying Files in the Work in Progress Module . . . . . . . . . . . . . . . . . . . . . . .122
Displaying My Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Configuring Local File Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Workflow CGI Tasks and ContentCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Displaying Task Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
The Get Latest Operation in ContentCenter Standard . . . . . . . . . . . . . . . . . . . .125
Resolving Task Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
Configuring Submit Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
Eliminating Tagging Steps in Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Chapter 7: The iwui User 127
Appendix A: Configuring Application Servers 129
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129
Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Configuration Procedures: Specific Web Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
ContentCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Event Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
Configuration Procedures: Overall App Server. . . . . . . . . . . . . . . . . . . . . . . . . . . .136
Disabling Apache Auto-Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
Edit ibm-web-ext.xmi (WebSphere only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137
Appendix B: WebDesk Pro Transition Reference 139

Contents
Appendix C: Migrating Roles and Permissions 143

Migration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Steps Invoked by the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
Steps to Invoke Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
Migration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Index 147
Interwoven, Inc. 6
List of Tables
Table 1 Notation conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 2 Disk space required for TeamSite installation . . . . . . . . . . . . . . . . . . . . 13
Table 3 CPU and memory requirements: TeamSite server . . . . . . . . . . . . . . . . . 15
Table 4 CPU and memory requirements: Search server . . . . . . . . . . . . . . . . . . . 16
Table 5 CPU and memory requirements: TeamSite and Search servers . . . . . . . 16
Table 6 TeamSite installation locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 7 Information required for TeamSite installation . . . . . . . . . . . . . . . . . . . 29
Table 8 Information required for Interwoven Search installation . . . . . . . . . . . . 32
Table 9 Samba configuration directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Table 10 File status and display in ContentCenter Standard . . . . . . . . . . . . . . . . 122
Table 11 WebDesk Pro and ContentCenter Professional commands. . . . . . . . . . 139

List of Tables
Interwoven, Inc. 8
List of Figures
Figure 1 Introduction screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Figure 2 J2SE patches screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Figure 3 License Agreement screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Figure 4 Product file location screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Figure 5 License Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Figure 6 License File screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Figure 7 License validation screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Figure 8 Content Store location screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Figure 9 Web Ports screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Figure 10 Log file location screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Figure 11 Mount Location screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Figure 12 Web Server confirmation screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Figure 13 Apache Configuration Location screen . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Figure 14 Apache Bin Location screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Figure 15 Windows File Sharing screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Figure 16 Windows Workgroup screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Figure 17 Event Subsystem And Utility Daemon Ports screen . . . . . . . . . . . . . . . . .53
Figure 18 Event Subsystem Database Type screen. . . . . . . . . . . . . . . . . . . . . . . . . . .54
Figure 19 Event Subsystem Database Configuration screen . . . . . . . . . . . . . . . . . . .54
Figure 20 Database Drivers Directory screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Figure 21 ReportCenter License Key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Figure 22 Report Center Database Type screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Figure 23 ReportCenter Database Drivers Directory screen. . . . . . . . . . . . . . . . . . . .56
Figure 24 ReportCenter Database Configuration screen . . . . . . . . . . . . . . . . . . . . . .57
Figure 25 Crystal Enterprise Report Information screen . . . . . . . . . . . . . . . . . . . . . .57
Figure 26 Crystal Enterprise Report Database Information screen. . . . . . . . . . . . . . .58
Figure 27 Authentication Method screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Figure 28 ContentServices License Key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Figure 29 VisualAnnotate Administrator Email screen . . . . . . . . . . . . . . . . . . . . . . .59
Figure 30 Introduction screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Figure 31 License Agreement screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Figure 32 Product Files location screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Figure 33 TeamSite Server Host screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Figure 34 Functionality to Enable screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Figure 35 Search Server Ports and Shared Filesystem Location screen . . . . . . . . . . .68
Figure 36 Index Server Ports and Shared Filesystem Location screen . . . . . . . . . . . .69
Figure 37 Enable Incremental Updates screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Figure 38 Event Subsystem JNDI Server Port screen. . . . . . . . . . . . . . . . . . . . . . . . .70
Figure 39 Index Server Host and Port screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Figure 40 Installation Complete screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Figure 41 iPlanet Server Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Figure 42 iPlanet Content Management screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Figure 43 Configuring iw-mount in iPlanet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

List of Figures
Figure 44 ContentCenter Standard Content module . . . . . . . . . . . . . . . . . . . . . . . . . .96

Figure 45 Content Store screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Figure 46 Content Store Properties screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Figure 47 Content Store Main branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Figure 48 ContentCenter Standard New Forms module . . . . . . . . . . . . . . . . . . . . . .120
Figure 49 Non-TeamSite browser directory listing. . . . . . . . . . . . . . . . . . . . . . . . . .120
Figure 50 ContentCenter Standard New Forms module . . . . . . . . . . . . . . . . . . . . . .121
Figure 51 Files in ContentCenter Standard Work In Progress module . . . . . . . . . . .122
Figure 52 ContentCenter Standard Tasks module. . . . . . . . . . . . . . . . . . . . . . . . . . .123
Figure 53 ContentCenter Standard Task Details screen . . . . . . . . . . . . . . . . . . . . . .124
Interwoven, Inc. 10
About This Guide
The TeamSite Installation Guide describes the procedures for installing, upgrading, and
licensing TeamSite and the initial, one-time configuration of all related system
resources. The actual TeamSite Content Server configuration settings are described in
the TeamSite Administration Guide. You may want to refer to the TeamSite
Administration Guide if you are not familiar with basic TeamSite concepts (for
example, the Content Store, user roles, branches, workareas, and so on).
This guide is primarily intended for TeamSite administrators and Master users, web
server administrators, and system administrators. Users of this manual should be
familiar with basic UNIX commands and be able to use a text editor such as emacs or vi.
Many of the operations described in this manual require root access to the system on
which you are installing and the TeamSite Content Server. If you do not have root
access, consult your UNIX system administrator.
Notation Conventions
This manual uses the following notation conventions:
Table 1 Notation conventions

Convention Definition and Usage
Bold Text that appears in a GUI element (for example, a menu item,
button, or element of a dialog box) and command names are
shown in bold. For example:
Click Edit File in the Button Bar.
Italic Book titles appear in italics.
Terms are italicized the first time they are introduced.
Important information may be italicized for emphasis.
Monospaced Commands, command-line output, and file names are in
monospaced type. For example:
The iwextattr command-line tool enables you to set and look
up extended attributes on a file.
Monospaced Monospaced italics are used for command-line
italic variables.TeamSiteFor example:
TeamSiteTeamSiteiwckrole role user
means that you must insert the values of role and user
yourself.

About This Guide
Table 1 Notation conventions (Continued)

Convention Definition and Usage
Monospaced Monospaced bold represents user input. The % character that
bold appears before a line of user input represents the command
prompt and should not be typed. Your system may not use this
command prompt. For example:
% iwextattr -s project=proj1
//IWSERVER/default/main/dev/WORKAREA/andre/products/
index.html
Monospaced Monospaced bold italic text is used to indicate a variable in
bold italic user input. For example:
% iwextattr -s project=projectname workareavpath
means that you must insert the values of projectname and
workareavpath when you enter this command.
[] Square brackets surrounding a command-line argument mean
that the argument is optional.
| Vertical bars separating command-line arguments mean that
only one of the arguments can be used.
Online Documentation Errata

Updates and corrections to this and other Interwoven product documentation are
available in PDF format at the following Web site:
https://support.interwoven.com/library/manuals/manuals.asp
Interwoven, Inc. 12
Chapter 1
Installation Prerequisites
This chapter describes the server hardware requirements that must be met before you
begin the installation procedure. See the TeamSite Release Notes for details about
software requirements and compatibility with other Interwoven products.
Server Hardware Requirements

Before beginning the TeamSite installation, ensure that the system that will host the
TeamSite server includes the hardware described in the following sections.
Disk Space
The following table lists the permanent and temporary storage requirements for the
TeamSite software when installing from CD-ROM. During installation, additional
temporary storage is required. Following installation, only the permanent storage is
needed.
Table 2 Disk space required for TeamSite installation

New
Item Upgrade
Installation
iw-home directory (permanent space 3.5 GB 1.8 GB
requirement)
Additional temporary space (typically in 800 MB 800 MB
/tmp; needed only during installation
procedure)
Additionally, if you install from the download package rather than from the CD-ROM,
you need 700MB to download and expand the package
You will need additional disk space for your Content Store. The Content Store is a large
directory structure where TeamSite stores your content files and metadata files. The
Content Store requires five to 10 times the total amount of disk space you expect your
content files to consume (for example, if you plan to manage 2 GB of content in
TeamSite, the Content Store should have at least 10 GB of disk space available).
The installation program prompts you for the location of the Content Store; ensure that
this location has room for at least five times the size of the content you plan to store

Chapter 1: Installation Prerequisites
there. For ease of maintenance, the Content Store should be installed to its own
partition.
CPUs and Memory

This section contains recommendations for the number of system CPUs and the amount
of system RAM.
CPU and RAM recommendations for a system running the TeamSite server are based on
the activity level of users who are concurrently using TeamSite, the total number of
licensed TeamSite users, and the size of the Content Store.
CPU and RAM recommendations for the system running the Interwoven Search server
are based on the type of content being searched (such as documents, data records, or
extended attributes), the frequency of query operations, and the required query response
time.
CPU and RAM recommendations also are based on whether the TeamSite and Search
servers run on the same system or separate systems.
The following sections show the CPU and RAM recommendations for:
A system running just the TeamSite server
A system running just the Interwoven Search server
A system running both the TeamSite and Interwoven Search servers
All CPUs should be at least 1.2 GHz.
Interwoven, Inc. 14
System Running Just the TeamSite Server
Table 3 CPU and memory requirements: TeamSite server

Usage
Heavy 1
Moderate 2
Light 3
15 concurrent users 2 CPUs 2 CPUs 1 CPU

100 total licensed
users 4 GB RAM 2 GB RAM 2 GB RAM
2 GB total content
50 concurrent users 4 CPUs 2 CPUs 2 CPUs
300 total licensed
5 GB total content
1000 total licensed
15 GB total content
3000 total licensed
50 GB total content
1. Numerous Get Latest, Submit, Publish, or compare operations; ongoing Web site or
directory navigation; frequent data record generation; frequent development of
workflows, presentation templates, and other file editing.
2. Occasional Get Latest, Submit, Publish, or compare operations; ongoing Web site or
directory navigation; occasional data record generation or file editing; few
development activities.
3. Infrequent Get Latest, Submit, Publish, or compare operations; occasional Web site
or directory navigation; occasional data record generation or file editing; no

System Running Just the Interwoven Search Server
Table 4 CPU and memory requirements: Search server

Content Type
Documents Data Records Extended Attributes
Response Time < 5 sec < 3 sec < 5 sec < 3 sec < 5 sec < 3 sec
N/A 1 CPU N/A 1 CPU N/A 1 CPU
100 1 GB 1 GB 1 GB
RAM RAM RAM
Queries N/A 1 CPU 1 CPU 2 CPU 1 CPU 2 CPU
per Hour 1000 1 GB 1 GB 4 GB 2 GB 4 GB
RAM RAM RAM RAM RAM
1 CPU 2 CPUs 2 CPUs N/A 2 CPUs N/A
2000 2 GB 4 GB 4 GB 4 GB
RAM RAM RAM RAM
System Running the TeamSite and Interwoven Search Servers
Table 5 CPU and memory requirements: TeamSite and Search servers

Usage
Heavy 1
Moderate 2
Light 3

100 total licensed
2 GB total content
300 total licensed
5 GB total content
150 concurrent users Contact 8 CPUs 4 CPUs
1000 total licensed Interwoven
users 8 GB RAM 4 GB RAM
15 GB total content
300 concurrent users Contact Contact 8 CPUs
3000 total licensed Interwoven Interwoven
users 8 GB RAM
50 GB total content
1. Numerous Get Latest, Submit, Publish, or compare operations; ongoing Web site or
directory navigation; frequent data record generation; frequent development of
workflows, presentation templates, and other file editing.
2. Occasional Get Latest, Submit, Publish, or compare operations; ongoing Web site or
directory navigation; occasional data record generation or file editing; few
3. Infrequent Get Latest, Submit, Publish, or compare operations; occasional Web site
or directory navigation; occasional data record generation or file editing; no
Interwoven, Inc. 16
Inodes
If the TeamSite Content Store is placed on a file system which enables you to
dynamically increase the number of inodes (for example, Veritas or NetApp), use the
default setting and add more inodes if needed.
If the TeamSite Content Store is placed on a file system that requires the total number of
inodes to be set when the file system is created (for example, UFS), use the newfs
command as follows:
newfs -i 1024 filesystem
where 1024 represents the bytes per inode, and filesystem is the path to your TeamSite
Content Store (for example, /local/iw-store).
Disk Configuration
For maximum disk space efficiency, the TeamSite Content Store should be installed on
drives formatted with a 1024 byte block or fragment size. For ease of maintenance, you
may want to install the Content Store on its own partition.
It is recommended that you use RAID 0+1 to configure your environment. RAID 5 can
also be used for environments with a relatively low number of writes as a percentage of
total accesses. Because TeamSite environments generally have a large percentage of
writes, RAID 0+1 should provide better overall performance. In addition to using RAID
configurations, it is recommended that you use the fastest available SCSI controllers
(160 MB/second transfer rate) and SCSI drives (10,000 RPM).
NOTES
Software RAID solutions are not recommended because they are very
CPU-intensive.
Installing TeamSite on a Primary Domain Controller (PDC) or a Backup Domain
Controller (BDC) is not supported. This can cause poor overall performance,
problems with local login access, and workflow issues.
Connecting Through the File System Interface

To connect to TeamSite using the file system interface, users must have a network
connection and the ability to interact with a networked file system (for example, FTP,
NFS, PCNFS, Samba server, FTP client, Windows networking). Before installing and
configuring any of these protocols, you should be familiar enough with them to perform
basic configuration and startup procedures. For more information, see “Accessing
TeamSite Using the File System Interface” on page 103.

Interwoven, Inc. 18
Chapter 2
Installing TeamSite
This chapter describes the process for installing, upgrading, and licensing TeamSite.
The following topics are included in this chapter:
Installing a Service Pack Release
Installing a Base Release
What Gets Installed?
Installing ReportCenter as a Standalone Module
Required Input for TeamSite and Search Installations
Installing TeamSite
Installing Interwoven Search
Licensing TeamSite
Upgrading from a Pre-6.7.1 TeamSite Release
Uninstalling TeamSite and Search
Installing a Service Pack Release

This section describes how to install TeamSite 6.7.1 Service Pack 1 and Interwoven
Search 2.1 Service Pack 1.
NOTE
TeamSite 6.7.1 must be installed as described starting in the section “Installing a Base
Release” before you install TeamSite 6.7.1 Service Pack 1 as described here. Likewise,
Interwoven Search 2.1 must be installed as described starting in the section “Installing a
Base Release” before you install Interwoven Search 2.1 Service Pack 1 as described
here.

Chapter 2: Installing TeamSite
Installation Order
If you are installing or upgrading to the TeamSite 6.7.1 and Search 2.1 base releases and
service packs, the overall installation order must be the following:
1. Base TeamSite 6.7.1 release
2. Base Search 2.1 release
3. TeamSite 6.7.1 Service Pack 1
4. Search 2.1 Service Pack 1
If TeamSite 6.7.1 and Search 2.1 are already installed on your system and you are only
upgrading to Service Pack 1 for TeamSite and Search, the installation order must be the
following:
1. TeamSite 6.7.1 Service Pack 1
2. Search 2.1 Service Pack 1
Attempting to install Search modules together with TeamSite modules in any other order
will result in either a failed installation or the inability to uninstall and then reinstall
releases correctly.
TeamSite and Search Compatibility

If Search is installed on your TeamSite system, you must ensure that the TeamSite and
Search releases match in one of the following ways. These are the only supported
combinations of TeamSite and Search. If you upgrade TeamSite, you must also upgrade
Search in the order described in “Installation Order”. See “Installing Interwoven Search”
on page 60 for additional information.
TeamSite 6.7, Search 2.0
TeamSite 6.7.1, Search 2.1
TeamSite 6.7.1 Service Pack 1, Search 2.1 Service Pack 1
Installing the TeamSite Service Pack

1. Log in to the Interwoven Support site and download the installation package:
https://support.interwoven.com
2. Save the installation package to any location on your local system.
NOTE
Multi-byte characters are not permitted in the installation package path.
3. Change user to root.
Interwoven, Inc. 20
4. Extract and untar the contents of the package:

gunzip -c package_file_name | tar xvfp -
5. Navigate into the TeamSiteSP directory.

6. You can use GUI mode if you are installing locally; you must use console mode if
installing remotely. To run the installation process in GUI mode, enable GUI mode
and run install.sh:
xhost +
./install.sh
To install in console mode, run install.sh with the following options:

install.sh -i console
7. In GUI mode, click Next. In console mode, press the Enter key on your keyboard.
TeamSite installs all necessary software modules. Depending on your system
configuration, this step could be time consuming, and some modules could require
responses from you.
8. Reboot the system after the installation is complete.
The system starts up in the English locale. If you want to run it in a different locale:
a. Stop iwserver.
b. Change the locale settings on the system to the desired value.
c. Comment out the server_locale line under the [iwserver] section in the
iw.cfg
d. Restart iwserver.
NOTE
The base release and the service pack must run under the same locale.
NOTE
The service pack installs the Apache Derby database software, which is another
database you can use for the event subsystem. See the TeamSite Administration Guide for
information about configuring a Derby database.
Installing the Search Service Pack

Search is an optional module. Perform the following steps to install the latest version of
Search:
1. Log in to the Interwoven Support site and download the installation package:
https://support.interwoven.com
2. Save the package to any location on your local system.

NOTE
Multi-byte characters are not permitted in the installation package path.

4. Extract and untar the contents of the package:
gunzip -c package_file_name | tar xvfp -
5. Navigate into the SearchSP directory.

6. You can use GUI mode if you are installing locally; you must use console mode if
installing remotely. To run the installation process in GUI mode, enable GUI mode
and run install.sh:
xhost +
./install.sh
To install in console mode, run install.sh with the following option:

install.sh -i console
7. In GUI mode, click Next. In console mode, press the Enter key on your keyboard.
Follow the installation procedure.
8. Reboot the system after the installation is complete.
The system starts up in the English locale. If you want to run it in a different locale:
a. Stop the index and search servers by issuing:
/etc/init.d/iw.tsindex stop
/etc/init.d/iw.tssearch stop
b. Edit the iw.search.locale property in

iwsearch-home/etc/search.properties
NOTE
The base release and the service pack must run under the same locale.
Installing a Base Release

The rest of this chapter describes how to install and uninstall the TeamSite 6.7.1 and
Interwoven Search 2.1 base releases. In this context, “base release” refers to any release
other than a patch or service pack.
NOTE
TeamSite 6.7.1 must be installed as described here before you install TeamSite 6.7.1
Service Pack 1 as described in “Installing a Service Pack Release”. Likewise, Interwoven
Search 2.1 must be installed as described here before you install Interwoven Search 2.1
Service Pack 1 as described in “Installing a Service Pack Release”.
Interwoven, Inc. 22
Required Linux Downloads

Before installing TeamSite 6.7.1 on Linux, you must download and compile uvfs
version 2.0 from the following location:
http://sourceforge.net/projects/uvfs
Compile the uvfs module on the same system that hosts the TeamSite installation to
insure compatibility, and ensure that the files are located somewhere on the TeamSite
server system. During the TeamSite installation procedure, you will be prompted to
specify the location of the files so that the TeamSite installer can install them in
iw-home/kernel.
Required Solaris Patch

TeamSite installation on Solaris 10 requires Solaris 10 patch 118833-18. The patch can
be downloaded from:
http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
The TeamSite installation program checks for the presence of this patch. If it is not
detected, you can choose to exit the TeamSite installation program and download the
patch, or continue with the TeamSite installation without the patch. If you continue
without the patch, you must install it before rebooting the system after the TeamSite
installation program finishes installing TeamSite. If you do not install the patch,
TeamSite will not function.
TeamSite Licensing
On UNIX systems, the TeamSite license file TS.Lic must be readable by the user iwts
(the iwts user replaces root as the owner of most TeamSite processes starting with
TeamSite 6.7.1). If you are upgrading from TeamSite 6.7.0, ownership of the existing
TS.Lic file is updated automatically by the TeamSite installation program. If you are
performing a new TeamSite 6.7.1 installation (as opposed to an upgrade) and you install
TS.Lic after the TeamSite installation completes, you might have to manually reset
permissions on TS.Lic so that it is readable by iwts.
What Gets Installed?

The following sections briefly introduce some of the major components and files that
are installed by the TeamSite installation program. The inclusion or location of many of
these components differs from previous versions of TeamSite.

TeamSite Components
The TeamSite installation program automatically installs the following components and
their supporting files:
TeamSite Content Server (iwserver)
ContentCenter Core Toolkit
ReportCenter (formerly Report Server or TeamSite Reporting). This is an optional
module; during TeamSite installation, you can choose not to install ReportCenter.
TeamSite end-user browser interfaces (described in Chapter 5, “Configuring
TeamSite Clients”):
ContentCenter Standard
ContentCenter Professional
TeamSite Content Store (formerly the backing store or MultiStore)
TeamSite Administration GUI
Interwoven Content Transformation Services
VisualAnnotate (English locales only; formerly had its own installation program)
VisualPreview (formerly SmartContext Editor or SCE)
Local File Manager (formerly Launch Pad)
ContentServices SOAP Server
FormsPublisher (formerly TeamSite Templating, which had its own installation
program)
Samba (optional)
Interwoven, Inc. 24
Default File Locations
By default, TeamSite is installed in the following locations (you may select alternate
locations for some of these files during the installation process).
Table 6 TeamSite installation locations

Default Directory Contents
/Interwoven/TeamSite Default location of TeamSite program files. The location of
this directory may be changed during installation. This
directory is referred to throughout this manual as iw-home.
/iw-store Default location of the TeamSite Content Store (this is
where TeamSite stores files and metadata for workareas
and editions). This directory can consume large amounts of
disk space. You can change the location of this directory
during installation or when the server is stopped. To find
where this directory is located, use the command-line tool
iwgetstore (see TeamSite Command-Line Tools).
Note: The contents of this directory should never be edited
by hand in any way. Tampering with this directory can
irreparably corrupt the data stored in TeamSite.
/iwserver Local file system mount projection directory. Clients
mount to this directory to access content files. No actual
data is stored in this directory, and its location cannot be
changed.
/iwmnt NFS server mount point. This directory is used to access
content files when working directly from the server. The
location of this directory can be changed; however, Web
server aliases must be updated to reflect this.
/.iwmnt NFS server mount point. This is a noncaching alias used by
the Web server. The location of this directory can be
changed; however, the Web server alias must be updated to
reflect this change.
/Interwoven/iwinstall Directory for managing all Interwoven software on the
system. This directory should never be altered, moved, or
removed by users.
Retaining Essential Installation Information

The /Interwoven/iwinstall directory contains essential metadata about the currently
installed release. If you alter any of this information, future upgrades or full installations
could fail. For this reason, it is highly recommended that you do not alter or delete any
files in /Interwoven/iwinstall.
Application Server
The Apache Tomcat application server is included with TeamSite and is installed when
you perform an installation as described in “Installing TeamSite” on page 32. TeamSite

also supports the IBM WebSphere and BEA WebLogic application servers. See
“Configuring Application Servers” on page 129 for details about configuring TeamSite to
use either of these application servers.
Log Files
The TeamSite installation program installs a number of log files that contain
information about the success or failure of the installation procedure, maintain an
inventory of the TeamSite modules and Interwoven products that are installed, and
monitor the TeamSite Content Server and UIs. These files are described in the sections
that follow.
Installation Log Files
The TeamSite installation log files are created one level up from the TeamSite directory
in the iwinstall/log directory. For example, if you accepted the default installation
directory (/Interwoven/TeamSite), the following log files are placed in the
/Interwoven/iwinstall/log directory:
productname_timestampglobal_result.xml—Summary of each module’s

installation status.
productname_timestampinstall.properties—Installer properties and a list of
your responses to each installation prompt.
productname_timestampinstall_log.log—Detailed log of install framework and
driver.
timestampdelayed_actions.xml—Summary of post-installation actions.
where timestamp represents the last modification date using the format hhmmMMDDYYYY.
For example, 042003182007 means that the log was created at 4:20AM on March 18,
2007.
Module Log Files
The installation program creates an XML-format log file for each module that is part of
TeamSite. The modules are as follows:
ant ccwapp customtk transformtk tsupgrade

cccoretk csiface ecmconnectortk tsadmin vannotate
ccprotk csjni iwservletd tsreport vpreviewtk
ccreportingtk cssoapsrvr iwwebd tsserver workflowmodelertk
ccstdtk customsptk jdk tstemplating
Interwoven, Inc. 26
Each module has a corresponding log file that is by default located in

/Interwoven/iwinstall/modules/module_name/log/. The module name uses the
format: timestampInterwoven_moduleName_InstallLog.xml. For example:
042011182006Interwoven_iwwebd_InstallLog.xml
where the timestamp notes the last modification date using the format: hhmmMMDDYYYY.
For example, 042003182007 means that the log was created at 4:20AM on March 18,
2007.
Product Log Files
The installation program creates an XML-format log file for each Interwoven product
that it installs. The product log file containing details of the product driver is named
Interwoven_TeamSite_releaseNumber_InstallLog.xml, and is located by default in
/Interwoven/iwinstall/products/productName/log/.
TeamSite Log Files
These text-format files log activities performed by the TeamSite Content Server
and UIs. The location of these files is specified during the installation procedure. The
default location is iw-home/local/logs.
These files are:

eventsubd.log
iwevents.log
iwserver.log
iwtrace.log
iwutild.log
/iwui/servletd_err.log
/iwui/servletd_out.log
The iwui directory can include several additional log files. Refer to the TeamSite
Administration Guide for more information about these log files. Depending on your
system setup, additional log files could be located in /var/adm.
Password Syntax
The TeamSite and Search installers cannot parse specified password strings containing
more than one dollar sign ($). For example, if you specify the database password in
step 24 on page 40 such that it contains two dollar signs (for example, asd$fjkl$dd), the
password is not set correctly in the corresponding configuration file. To correct this, you
must edit the configuration file manually.

Interwoven Search
Interwoven Search, which also includes indexing features, is installed separately from
TeamSite. To install Interwoven Search, you perform a procedure similar to the
TeamSite installation procedure. See “Installing Interwoven Search” on page 60 for
details.
Installing ReportCenter as a Standalone Module

When you install TeamSite, you are also prompted to install and configure ReportCenter
(see step 27 on page 55). If you choose not to install ReportCenter during a TeamSite
installation, you can go back later and install it as a standalone module as follows:
1. Obtain a ReportCenter license key from Interwoven Support or an Interwoven sales
representative.
2. Log in as root on the system where you want to install ReportCenter.
Set the PATH environment variable to:
dir_name/TeamSite/InstallerData/jre/binwhere dir_name is the directory
where you unpacked the TeamSite installation package.
3. Change directories to the location of the TeamSite installer.The following is a
typical installer location, although the location on your system could be different.
TS670packagelocation/TeamSite/InstallerData/modules/tsreport/Disk1/
InstData/NoVM
4. Execute the following command:

./tsreport.bin -f iwinstall/log/
TeamSitelatest_timestampinstall.properties
5. The first ReportCenter installation screen is displayed as shown in step 26 on

page 55. Follow the directions in the installation documentation from there.
Required Input for TeamSite and Search

Installations
The following tables describe the information for which you are prompted during
TeamSite and Interwoven Search installations.
Interwoven, Inc. 28
TeamSite Information
Table 7 Information required for TeamSite installation
Default
Information Step Notes
Provided?
Location of TeamSite step 8 on page 35 Yes Referred to as iw-home
program files. step 11 on throughout documentation.
page 46
TeamSite license file. step 9 on page 35 No The file must be named
TS.lic and reside in
step 12 on
iw-home/etc.
page 47
Location of Content step 12 on Yes
Store. page 36
step 15 on
page 48
Web server ports: HTTP, step 13 on Yes
HTTPS, Servlet, Proxy, page 37
and Web Server. step 15 on
page 48
Location of TeamSite log step 15 on Yes
files. page 38
step 17 on
page 50
TeamSite mount point. step 16 on Yes
page 38
step 18 on
page 50
Web server selection. step 17 on Yes Choices are Apache or
page 38 Other.
step 19 on
page 51
Location of Apache step 18 on Yes Required only if you
configuration file. page 38 selected Apache in the
step 20 on previous step.
page 51
Location of Apache bin step 19 on Yes Required only if you
directory. page 39 selected Apache earlier.
step 21 on
page 52
Whether to install Samba. step 20 on Yes
page 39
step 22 on
page 52


Default
Provided?
Windows workgroup. step 21 on Yes Required only if you
page 39 selected Samba in the
step 23 on previous step.
page 53
Event subsystem ports: step 22 on Yes
OpenJMS server, JNDI page 39
server, and utility step 23 on
daemon. page 53
Event subsystem database step 23 on Yes
type. page 39
step 24 on
page 54
Event subsystem database step 24 on No Required only if a database
information: server name, page 40 was selected in the previous
listen port, database step 25 on step.
name, administrator page 54
name, and administrator
password.
Location of event step 25 on No Required only for mssql and
subsystem database page 40 db2.
drivers. step 26 on
page 55
ReportCenter license key. step 26 on No Required only if installing
page 40 ReportCenter at this time.
step 27 on ReportCenter can optionally
page 55 be installed later as a
separate module.
ReportCenter database step 27 on Yes Required only if installing
type. page 41 ReportCenter at this time.
step 28 on
page 56
Location of ReportCenter step 28 on No Required only for mssql and
database drivers. page 41 db2.
step 29 on
page 56
ReportCenter database step 29 on No Required only if installing
information: server name, page 41 ReportCenter at this time
listen port, database step 31 on and if the ReportCenter
name, administrator page 57 database type is db2 or
name, and administrator mssql.
password.
Crystal Enterprise system step 30 on No Root location is on the
information: host name page 41 Crystal Enterprise server,
and root path where step 32 on not the TeamSite server.
TeamSite reports are page 57
located.
Interwoven, Inc. 30

Default
Provided?
Crystal Enterprise step 31 on No Refers to the system on
database information: page 42 which Crystal Enterprise
datasource name and step 33 on (not TeamSite) is installed.
database name. page 58
Crystal Enterprise step 32 on Yes Choices are LDAP or
authentication method. page 42 Enterprise.
step 34 on
page 58
ContentServices license step 33 on No You can optionally proceed
key. page 42 without a license key and
step 35 on install one after completing
page 59 the TeamSite installation.
VisualAnnotate step 34 on No Only applies to English
administrator email page 42 locales.
address. step 36 on
page 59

Search Information
Table 8 Information required for Interwoven Search installation
Default
Information Step Provided Notes
?
Location of Interwoven step 7 on page 62 Yes
Search program files. step 8 on page 67
Name of the TeamSite step 8 on page 62 Yes
server. step 9 on page 67
Whether to enable Search, step 9 on page 63 Yes You must enable at least
indexing, or both. step 10 on page 68 one.
Search server port and file step 10 on page 63 Some Required only if Search
system information: search step 11 on page 68 was enabled in the
server port, search agent previous step. Defaults
port, search agent callback provided for all except
port, file system location location of indexed
containing indexed branches.
TeamSite branches.
Index server port and file step 11 on page 63 Some Required only if indexing
stem information: index step 12 on page 69 was enabled in an earlier
server port, index agent step. Defaults provided for
port, index agent callback all except location of
port, file system location indexed branches.
containing indexed
TeamSite branches.
Whether to enable step 12 on page 64 Yes Required only if indexing
incremental updates. step 13 on page 70 was enabled in an earlier
step.
Event subsystem JNDI port. step 13 on page 64 Yes Required only if
step 14 on page 70 incremental updates were
enabled in the previous
step. This is the same
value that was entered in
step 23 on page 53.
Indexing server host name step 14 on page 64 Some Required only if you
and port. step 15 on page 71 enabled search and did not
enable indexing in an
earlier step. Default port
number is provided.
Installing TeamSite
The sections that follow describe how to install the TeamSite base release using console
mode (Interactive text-based prompts from within a terminal window) and graphical
mode (interactive GUI-based prompts). If you are installing a service pack, see
“Installing the TeamSite Service Pack” on page 20.
Interwoven, Inc. 32
NOTE
Graphical mode is available only when you are installing directly on the system that
hosts the TeamSite server (that is, when you are logged into the console). It is not
available when you are installing from a remote system.
Before starting the installation program, ensure that your system satisfies the hardware
and software requirements described in the Chapter 1, “Installation Prerequisites”. The
installation process is recorded in a series of log files located in the iwinstall directory
as described in the “Installation Log Files” on page 26 section.
NOTES
If you are upgrading your current TeamSite implementation, proceed to “Upgrading
from a Pre-6.7.1 TeamSite Release” on page 73.
If you plan to install Interwoven Search (available as a separately installed module),
there are several critical factors to be aware of regarding installation order and
compatibility with TeamSite. See “Installation Order” on page 20 and “TeamSite and
Search Compatibility” on page 20 for more information.
Installing Using Console Mode

Complete the following procedure to install TeamSite using the text-based console
mode. This is the only installation mode available if you are installing from a remote
system.
1. Log in as root on the system where you want to install the TeamSite server.
Do not use sudo su - to gain root access when installing TeamSite. Using
sudo su - instead of su - may cause problems with shutdown, startup, or
installation operations.
2. If you are installing on a Solaris 10 system, you must perform the installation in a
global zone.
It is recommended that you download the Solaris patch cluster from the following
location:
http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/J2SE
The TeamSite installation program checks for the presence of these patches as
described in step 6. If you intend to install these patches, you must do so before you
start the TeamSite installation program.
3. Either:
Download the installation tar file (IWOVts-sol-6.7.1.0-Build#####.tar.gz)
to a temporary directory where it can be expanded. This temporary directory
will not be the installation directory. You will be prompted to select the location
for the program files by the installation program. Go to step 4 and continue the
installation from there.

Insert the TeamSite CD-ROM. Locate the install.sh installation program at

the top level of the CD-ROM contents. Go to step 5 and continue the installation
from there.
4. Uncompress and expand the IWOVts-sol-6.7.1.0-Build#####.tar.gz file by
running the following command:
# gunzip -c IWOVts-sol-6.7.1.0-Build#####.tar.gz | tar xvpf -
This command creates the TeamSite directory and populates it with subdirectories
and files used by the installation program. After the tar file is expanded, change to
the TeamSite directory:
# cd TeamSite
5. Run the following command to start the TeamSite installation program:

# ./install.sh -i console
Note: If you are installing from a remote system, the installation executes in console
mode by default (even if you do not specify the -i console option).
The following introductory text displays:
Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
Launching installer...
Preparing CONSOLE Mode Installation...
Introduction
This is the TeamSite 6.7.1.0 installation program.
Respond to each prompt and press Enter to proceed to the next step in
the installation. If you want to change something on a previous step,
type 'back'.
You may cancel this installation at any time by typing 'quit'.
PRESS <ENTER> TO CONTINUE:
Press Enter.
6. If the installation program detects an older version of TeamSite on your system, its
release number and location are displayed. If this happens, see step 14 on page 75
for more information.
If the installation program does not detect an older version of TeamSite on your
system, and if the latest J2SE patches are not installed, the following information
displays:
Warning
-------
/var/sadm/install_data/J2SE_Solaris*Recommended_log not found.
It is highly recommended to install J2SE Solaris Patch Cluster prior to

running this program.
Interwoven, Inc. 34
The Patch Cluster can be downloaded from:

This Cluster includes the most important patches that help to avoid the
most critical bugs and failures related to the functionality of the
Java platform on the Solaris Operating System which have been reported
and fixed to date.
Type 'quit' to quit this installation and install the Cluster Patch.
Press 'Enter' to begin the installation without installing the Cluster
Patch.
If you intend to install the patches, quit the installation program, perform the patch
installation, and restart the installation program. If you do not intend to install the
patches, press Enter to continue the installation.
7. The license agreement text is displayed. Continue to press Enter to scroll through
the entire agreement until you reach this text:
DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N)?
To accept the terms, enter Y and press Enter. To decline, enter N and press Enter.
8. You are prompted to select the TeamSite Product Files (iw-home) directory:
This is the directory where Interwoven TeamSite 6.7.1.0 program files will be
installed.
Enter the directory for the Interwoven TeamSite 6.7.1.0 program files:
Default Install Folder: /Interwoven/TeamSite
ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE
DEFAULT
Press Enter to accept the default (/Interwoven/TeamSite) or enter a different path
and press Enter.
9. Instructions for obtaining a TeamSite license are displayed:
Important License Information
-----------------------------
Please read before continuing:
TeamSite 6.7.1 requires a new license.
The new license must be provided in form of license file called TS.lic.
If you didn't obtain the license file yet, perform the following steps:
Visit Interwoven support site license generation page at

https://support.interwoven.com/supportlogin2.asp and use

the following information to fill in the license generation form:

====================
DOMAIN=your_domain_name
HOSTNAME=your_host_name
PRODUCT=TS
CPUS=
====================
The new license file TS.lic will be emailed to the registered

Interwoven support contact email address as an attachment.
Obtain the file from the email and copy it into a directory
accessible on this system.
If you have not yet obtained and installed a TeamSite license file, do so now by
following the instructions shown onscreen. When you finish, press Enter.
10. You are prompted to enter the location of the license file:
License File
------------
Enter a full path of a license file on your system.
License File: (DEFAULT: /Interwoven/TeamSite/etc/TS.lic):
The TeamSite license file must be named TS.lic, and it must reside in a readable
location on the TeamSite server. Enter that location and press Enter (or just press
Enter to specify the default location iw-home/etc).
11. If the license file is valid, you are prompted to proceed:
Information
-----------
File /Interwoven/TeamSite/etc/TS.lic was validated successfully and it

contains a valid license.
12. Press Enter. You are prompted for the location of the TeamSite Content Store:
Enter the directory for your Content Store:
content store location (DEFAULT: /iw-store):
The Content Store is a large directory that contains the content files managed in
TeamSite, and metadata files. Ensure that the location of the Content Store is at least
Interwoven, Inc. 36
five times the size of the content you wish to manage with TeamSite. For ease of
maintenance, the Content Store should be installed to its own partition.
Refer to the TeamSite Administration Guide for detailed information on creating and
maintaining additional Content Stores.
Press Enter to accept the Content Store location (/iw-store), or enter a different
location and press Enter.
NOTE
If you specify an alternate location for the Content Store, you must use ASCII
characters. Do not use the iw-home location for the Content Store location; specify a
different location.
13. You are prompted for a series of port numbers; the first is the HTTP port. TeamSite
uses two Web servers:
The Interwoven Web server—Installed with TeamSite, and used to render the
TeamSite GUIs. By default, it is assigned port 80 for HTTP connections and
port 443 for HTTPS (secure) connections.
If you do not use port 80 for the Interwoven Web server, users must explicitly
specify the alternate port number in the URL each time they access the
TeamSite GUI.
The non-Interwoven Web server (for example, Apache)—Used to render the
files stored in the TeamSite Content Store. By default, it is assigned port 81 and
labeled webserver. If this Web server is using a port other than 81, it is
reconfigured to use port 81 (or whatever port you specify in this step).
NOTE
In some earlier releases of TeamSite, port 80 was assigned to the customer
(non-Interwoven) Web server by default. At the time, this Web server rendered both
the TeamSite UIs and content files.
The prompt for HTTP port is as follows:

Web Ports
---------
The Interwoven Web server (installed with TeamSite): Renders the

TeamSite UIs (using HTTP and HTTPS ports). The non-Interwoven Web
server (IIS, Apache or similar): Renders the content stored in the
TeamSite Content Store (using Web Server port). Enter the port numbers
used by the Interwoven Web Daemon:
HTTP (DEFAULT: 80):
Press Enter to accept the default port, or enter a different port number and press
Enter.

14. You are prompted for additional port numbers.

HTTPS (DEFAULT: 443):
Servlet (DEFAULT: 8080):
Proxy (DEFAULT: 1080):
Web Server (DEFAULT: 81):
At each prompt, press Enter to accept the default port, or enter a different port
number and press Enter.
15. You are prompted for the location of the TeamSite log files:
Enter the directory where you want the TeamSite log files located. If
this directory does not exist, installer will attempt to create it.
Log Location (DEFAULT: /Interwoven/TeamSite/local/logs):
NOTE
The location specified in this step is for the log files for TeamSite Content Server
and UI log files (iwserver.log, iwtrace.log, iwui/*.log). Do not confuse this
location with the installation and inventory log files that are located in the
iwinstall directory as described on page 26.
Press Enter to accept the default location for the log files, or enter a different
location and press Enter.
16. You are prompted for the TeamSite mount point:
Enter the mount point that you want to use to access the content stored
in your Content Store.
Mount Location (DEFAULT: /iwmnt):
Press Enter to accept the default mount point, or enter a different location and press
Enter.
17. You are prompted to confirm that you are using the Apache Web server:
Are you using Apache as your content Web Server (1=YES, 2=NO)?
If you are using Apache, you will configure it in the next screen. If
you are using another Web server, you must configure it after
completing the installation. Details are included in the TeamSite
Installation Guide.
->1- YES
2- OTHER
Press Enter to accept the default value of 1 (that is, you are using an Apache Web
server), or enter 2 (no, you are not using Apache) and press Enter.
18. If you are using Apache, you are prompted for the location of the configuration files
(if you are using another Web server, go to step 20 and continue from there):
The TeamSite installation program must modify your Apache httpd.conf
file. Where is this file located?
apache configuration directory (DEFAULT: /etc/apache):
Press Enter to accept the default location of the Apache Web server configuration
file, or enter a different location and press Enter.
Interwoven, Inc. 38
19. You are prompted for the location of the Apache bin directory:
The TeamSite installation program must know the location of your Apache
bin directory. Where is this directory located?
apache bin directory (DEFAULT: /usr/apache/bin):
Press Enter to accept the default location of the Apache binary files, or enter a
different location and press Enter.
20. You are prompted whether you want to install Samba to enable Windows PCs to
connect to your Solaris TeamSite server:
If you plan to connect to Interwoven TeamSite from a PC running Windows
and you do not have Samba installed, you will need to install it now.
Do you want to install Samba (1=YES, 2=NO)?
->1- Samba
2- No Samba
Press Enter to accept the default value of 1 (install Samba), or enter 2 (do not install
Samba) and press Enter.
21. If you enter 1 (install Samba), you are prompted for a workgroup name:
Which Windows workgroup do you want the Interwoven TeamSite server to
appear in?
WORKGROUP (DEFAULT: interwoven):
Press Enter to accept the default workgroup name, or enter a different name and
press Enter.
22. You are prompted to enter information about Event Subsystem and Utility Daemon
ports:
Enter the OpenJMS server port number, JNDI server port number and
Utility Daemon port number.
OpenJMS Server Port Number: (DEFAULT: 3030):
JNDI Server Port Number: (DEFAULT: 3035):
Utility Daemon HTTPS Port Number: (DEFAULT: 6689):

Press Enter to accept the default ports used by the event subsystem, or enter
different values and press Enter. If you specify a port that is invalid or busy, you are
prompted to enter a different port number.
23. You are prompted to enter information about the database used by the Event
Subsystem:
Select database type to use with the Event Subsystem.
->1- default
2- oracle
3- mssql
4- db2
5- MySQL
ENTER A COMMA-SEPARATED LIST OF NUMBERS REPRESENTING THE

DESIRED CHOICES, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:

If you select default, the event subsystem will store event information in a flat file
rather than in a database. It is strongly recommended that you select a database
instead of default, so that event information can be stored and processed in a
higher performing and scalable manner making use of full database functionality.
If you select default, you are prompted for information about the ReportCenter
license key. Go to step 26 and continue from there.
24. If you select a database rather than default, you are prompted for information
about the database configuration:
Enter the databse server name, database listen port, database name,
database admin user name and password.
Database Server Name: (DEFAULT: ):
Database Listen Port: (DEFAULT: 1433):
Database Name: (DEFAULT: ):
User Name: (DEFAULT: ):
User Password: (DEFAULT: ):
Enter the name of the server that hosts the event subsystem database (Database
Server Name), the port used by the database (Database Listen Port), the name of the
database as assigned by the database administrator (Database Name), the ID of the
database administrator (User Name), and the database administrator password (User
Password).
25. If you selected default, oracle, or MySQL in step 23, you are prompted for
information about the ReportCenter license key. Go to step 26 and continue the
installation procedure from there.
If you selected mssql or db2 in step 23, you are prompted for information about the
database drivers directory:
Enter a directory where the database drivers are located.
Enter a Directory: (DEFAULT: ):
Enter or the location of the drivers used by the event subsystem database and press
Enter. For mssql, the location must contain the files mssqlserver.jar, msbase.jar,
and msutil.jar. For db2, the location must contain the db2jcc.jar file.
26. You are prompted for the ReportCenter license key:
If you plan to use TeamSite Report Server, a license key is required.
Enter the license key, or press Enter to continue without a license
key.
License Key (DEFAULT: ):
If you plan to use ReportCenter, enter the ReportCenter license key you received
from Interwoven and press Enter. Go to step 27 and continue from there.
NOTE
If you do not have a ReportCenter license key, you can complete the TeamSite
installation and then install ReportCenter at a later time. See “Installing
ReportCenter as a Standalone Module” on page 28 for more information.
Interwoven, Inc. 40
If you do not plan to use ReportCenter, press Enter without entering a license key.
Go to step 30 and continue from there.
27. You are prompted for information about the type of database used by ReportCenter:
Select the database vendor for the reporting database.
->1- oracle
2- db2
3- mssql
ENTER A COMMA-SEPARATED LIST OF NUMBERS REPRESENTING THE

DESIRED CHOICES, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:
Enter the number corresponding to the type of database used by ReportCenter and
press Enter.
28. If you specify oracle, the Database Configuration screen is displayed. Go to step 29
and continue from there.
If you specify db2 or mssql, you are prompted to enter the location of the database
drivers:
Enter a directory where the database drivers are located.
Enter a Directory: (DEFAULT: ):
Enter the location of the drivers used by the ReportCenter database and press Enter.
For mssql, the location must contain the files mssqlserver.jar, msbase.jar, and
msutil.jar. For db2, the location must contain the db2jcc.jar file.
29. You are prompted for ReportCenter database configuration information:

Enter the database server name, database name, database listen port,
database admin user name and password. You can continue without making
entries.
Database Server Name: (DEFAULT: ):
Database Name: (DEFAULT: ):
Database Listen Port: (DEFAULT: ):
User Name: (DEFAULT: ):
User Password: (DEFAULT: ):
Enter the name of the server that hosts the ReportCenter database (Database Server
Name), the name of the database as assigned by the database administrator
(Database Name), the port used by the database (Database Listen Port), the ID of the
Password).
30. You are prompted for information about the system that hosts Crystal Enterprise:
Enter the following information:
The name of the Crystal Enterprise CMS server or cluster (Host Name).
The path to the root folder containing the TeamSite reports on your
Crystal Enterprise server (Root Path)

Crystal Enterprise Host Name (DEFAULT: ):

Crystal Reports Root Path (DEFAULT: ):
Enter the name of the system that hosts Crystal Enterprise (Crystal Enterprise Host
Name) and the directory on the Crystal Enterprise system where TeamSite reports
are stored (Crystal Reports Root Path). Press Enter.
31. You are prompted for information about the Crystal Enterprise report database:
Crystal Report Database Information

-----------------------------------
Enter the following information:

In the DataSourceName field, enter the name of the database connection
on the Crystal Enterprise system.
In the DBName field, enter the name of the database on the Crystal
Enterprise system as assigned by the database administrator.
DataSourceName (DEFAULT: ):
DBName (DEFAULT: ):
Enter the name of the database connection on the Crystal Enterprise system
(DataSourceName) and the name of the database on the Crystal Enterprise system as
assigned by the database administrator (DBName). Press Enter.
32. You are prompted for authentication method information:
Please choose the default authentication method for accessing Crystal
Enterprise Reports.
->1- LDAP
2- Enterprise
ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO

ACCEPT THE DEFAULT:
Select the authentication method and press Enter.
33. Several messages display about launching the installer for ContentServices SOAP.
After they display you are prompted for a SOAP server license key:
If you plan to use ContentService SOAP server, a license key is
required. You can obtain the license key from the license.txt file in
the Interwoven ContentService Soap Client package. Enter the license
key, or press "enter" to continue without a license key.
Press Enter to continue without the license key, or enter the key and press Enter.
34. If you are installing on an English locale system several messages display about
launching the installer for VisualAnnotate. After they display you are prompted to
enter a VisualAnnotate administrator email address:
Enter VisualAnnotate Admin Email Address (DEFAULT: ):
Interwoven, Inc. 42
The email address is used by the Send Support Email link on the VisualAnnotate
toolbar and error dialogs so that end-users can communicate errors to their TeamSite
administrator.
Enter the email address of the TeamSite administrator (or VisualAnnotate
administrator if they differ) and press Enter.
NOTE
If you are installing on a non-English locale system, VisualAnnotate is not
supported and you do not perform the VisualAnnotate portion of this step.
35. The installation program begins copying files to your system. If ReportCenter is not
installed and configured, a notice is displayed containing instructions for the
installation and configuration. If you need to install ReportCenter, see “Installing
ReportCenter as a Standalone Module” on page 28.
When finished, the installer displays the following confirmation:
TeamSite has been successfully installed into:
/Interwoven/TeamSite
PRESS ENTER TO EXIT THE INSTALLER:
Press Enter to complete the installation program, then reboot your system.
NOTE
It is recommended that you use the shutdown -i6 command (and not the reboot
command) to reboot the system. This command ensures that the necessary shutdown
scripts execute during rebooting. In some cases, you might see error messages
indicating that shutdown scripts were not run. You can ignore these messages if you
used the shutdown -i6 command.
Installing Using Graphical Mode

NOTE
The screens shown in this section pertain to TeamSite 6.7.1 even though some contain
the designation “6.7.0.0.”
Complete the following procedure to install TeamSite using the graphical interface.
1. Open a terminal window on the system where you want to install the TeamSite
server (graphical mode is not supported when installing from a remote Solaris
system).
2. As a non-root user, run the following command to enable root access to the X11
display:
% xhost +

NOTE
Failure to set xhost + could cause the installation to abort at any time.
3. Log in as root.
NOTE
Do not use sudo su - to gain root access when installing TeamSite. Using
sudo su - instead of su - may cause problems with shutdown, startup, or
installation operations.
global zone.
It is recommended that you download the Solaris patch cluster from the following
location:
The TeamSite installation program checks for the presence of these patches as
described in step 8. If you intend to install these patches, you must do so before you
start the TeamSite installation program.
5. Either:
Download the installation tar file (IWOVts-sol-6.7.1.0-Build#####.tar.gz)
from there.
6. Uncompress and expand the IWOVts-sol-6.7.0.0-Build#####.tar.gz file by
# gunzip -c IWOVts-sol-6.7.1.0-Build####.tar.gz | tar xvpf -
# cd TeamSite

# ./install.sh
NOTE
If the DISPLAY environment variable is not defined or if you invoke install.sh
from a remote system, the installation starts in console mode, not graphical mode.
Interwoven, Inc. 44
The installer is launched and the Introduction window displays. The message could
differ slightly from the one shown here depending on which system patches are
installed:
Figure 1 Introduction screen
8. Click Next. If the latest J2SE patches are not installed, information about them is
displayed:
Figure 2 J2SE patches screen
9. If you intend to install the patches, quit the installation program, perform the patch
installation, and restart the installation program. If you do not intend to install the
patches, press Enter to continue the installation.
The License Agreement window displays:

Figure 3 License Agreement screen
10. If you agree with the terms of the license, click the I accept... button and then click
Next. If you do not agree with the terms, click Cancel or Previous.
If the installation program detects an older version of TeamSite on your system, its
release number and location are displayed. If this happens, see step 14 on page 75
for more information.
If the installation program does not detect an older version of TeamSite on your
system, the Product Files screen displays:
Figure 4 Product file location screen
11. Click Next to accept the default installation location for the TeamSite program files
(/Interwoven/TeamSite) or click Choose to select another location.
Interwoven, Inc. 46
NOTE
If you specify an alternate location for the program files or the Content Store (in
step 15), you must use ASCII characters.
The License Information screen displays:

Figure 5 License Information screen
12. If you have not yet obtained and installed a TeamSite license file, do so now by
following the instructions shown onscreen. When you finish, click Next and the
License File screen displays:
Figure 6 License File screen
13. The TeamSite license file must be named TS.lic, and it must reside in a readable
location on the TeamSite server. Enter that location and press Enter (or just press
Enter to specify the default location iw-home/etc).
If the license file is valid, you are prompted to proceed by clicking Install:

Figure 7 License validation screen
14. The Content Store screen displays prompting you for the location of the default
Content Store.
Figure 8 Content Store location screen
15. Click Next to accept the default location for the TeamSite Content Store
(/iw-store) or click Choose to select another location.
NOTE
For ease of maintenance, the Content Store should be located on its own partition.
Do not use the iw-home location for the Content Store location; specify a different
location.
The Web Ports screen displays, prompting you for the port numbers used by the
Interwoven Web Daemon.
Interwoven, Inc. 48
Figure 9 Web Ports screen
Interwoven Web server ports
non-Interwoven Web server port

(also known as content Web server
or customer Web server)
NOTE
TeamSite uses two Web servers:
The Interwoven Web server—Installed with TeamSite and used to render the
TeamSite GUIs. By default, it is assigned port 80 for HTTP connections and port
443 for HTTPS (secure) connections.
The non-Interwoven Web server (for example, Apache)—Used to render the content
stored in the TeamSite Content Store. By default, it is assigned port 81 and labeled
Web Server. If this Web server is using a port other than 81, it is reconfigured to use
port 81 (or whatever port you specify in this step).
Important: If you do not use port 80 for the Interwoven Web server, users must
explicitly specify the alternate port number in the URL each time they access the
TeamSite GUI.
NOTE
In some earlier releases of TeamSite, port 80 was assigned to the customer
(non-Interwoven) Web server by default. At the time, this Web server rendered the
TeamSite GUIs and content files.
16. Click Next to accept the default values, or edit the values and click Next.
If any of the ports are already being used, you are prompted to either change them
by clicking Previous and returning to the Web Daemon Configuration screen, or
clicking Continue.
After selecting the ports, the Log Files screen displays:

Figure 10 Log file location screen
17. Enter the directory where you want TeamSite log files installed, or click Next to
accept the default location (iw-home/local/logs).
NOTE
The location specified in this step is for the log files for TeamSite Content Server
and UI log files (iwserver.log, iwtrace.log, iwui/*.log). Do not confuse this
location with the install and inventory log files that are located in the iwinstall
directory as described on page 26.
After you select the log file location, the Mount Location screen displays:
Figure 11 Mount Location screen
18. Click Next to accept the default mount point (/iwmnt) or click Choose to select
another location. You are prompted to confirm that you want to use Apache as your
content Web server.
Interwoven, Inc. 50
Figure 12 Web Server confirmation screen
19. Click Next to confirm that you want to use Apache as your content Web server, or
select No (you are not using Apache) and click Next.
If you are using another Web server, continue from step 22.
If you are using Apache, the Apache Configuration Location screen displays,
prompting you for the location of the configuration files:
Figure 13 Apache Configuration Location screen
20. Click Next to accept the default location of the Apache Web server configuration
file, or enter a different location and click Next. You are prompted for the location
of the Apache bin directory.

Figure 14 Apache Bin Location screen
21. Click Next to accept the default location of the Apache binary files, or enter a
different location and click Next.
The Windows File Sharing screen displays:
Figure 15 Windows File Sharing screen
22. Click Next to install Samba (which enables Windows clients to connect to your
Solaris TeamSite server).
If you install Samba, the Windows Workgroup screen displays prompting you for a
workgroup name (the remainder of the Samba installation is automatic):
Interwoven, Inc. 52
Figure 16 Windows Workgroup screen
23. Click Next to accept the default workgroup name, or enter a different name and
click Next. The Event Subsystem And Utility Daemon Ports screen displays:
Figure 17 Event Subsystem And Utility Daemon Ports screen
Click Next to accept the default ports used by the event subsystem and utility
daemon, or edit the values and click Next. If you specify a port that is invalid or
busy, you are prompted to enter a different port number.
After you select the event subsystem and utility daemon ports, the Database Type
screen is displayed.

Figure 18 Event Subsystem Database Type screen
24. Select the type of database used by the event subsystem. If you select default, the
event subsystem will store event information in a flat file rather than in a database.
It is strongly recommended that you select a database instead of default, so that
event information can be stored and processed in a higher performing and scalable
manner making use of full database functionality. If you select default, the
ReportCenter License Key screen is displayed. Go to step 26 and continue the
installation procedure from there.
If you select a database rather than default, the Database Configuration screen is
displayed.
Figure 19 Event Subsystem Database Configuration screen
25. Enter the name of the server that hosts the event subsystem database (Database
Password).
If you selected default, oracle, or MySQL in step 24, the ReportCenter License Key
screen is displayed. Go to step 27 and continue the installation procedure from there.
Interwoven, Inc. 54
If you selected mssql or db2 in step 24, the Database Drivers Directory screen is
displayed.
Figure 20 Database Drivers Directory screen
26. Enter or browse to the location of the drivers used by the event subsystem database.
Click Install. The ReportCenter License Key screen is displayed.

Figure 21 ReportCenter License Key screen
27. If you plan to use ReportCenter, enter the ReportCenter license key you received
from Interwoven and click Next. Go to step 28 and continue the installation
procedure from there.
NOTE
If you do not have a ReportCenter license key, you can complete the TeamSite
installation and then install ReportCenter at a later time. See “Installing
ReportCenter as a Standalone Module” on page 28 for more information.

If you do not plan to use ReportCenter, click Next without entering a license key. Go
to step 32 and continue the installation procedure from there.
28. The Database Type screen is displayed for ReportCenter.
Figure 22 Report Center Database Type screen
Select the type of database used by ReportCenter. If you select oracle, the Database
Configuration screen is displayed. Go to step 31 and continue the installation from
there. If you select db2 or mssql, you are prompted to enter the location of the
database drivers. Go to step 29 and continue the installation from there.
29. The Database Drivers Directory screen is displayed.
Figure 23 ReportCenter Database Drivers Directory screen
30. Enter the location of the drivers used by the ReportCenter database and click Next.
The Database Configuration screen is displayed.
Interwoven, Inc. 56
Figure 24 ReportCenter Database Configuration screen
31. Enter the name of the server that hosts the ReportCenter database (Database Server
Password).
Click Install. The Crystal Enterprise Report Information screen is displayed.
Figure 25 Crystal Enterprise Report Information screen
32. Enter the name of the system that hosts Crystal Enterprise (Crystal Enterprise Host
are stored (Crystal Reports Root Path).
Click Next. The Crystal Enterprise Report Database Information screen is
displayed.

Figure 26 Crystal Enterprise Report Database Information screen
33. Enter the name of the database connection on the Crystal Enterprise system
assigned by the database administrator (DBName).
Click Next. The Authentication Method screen is displayed.
Figure 27 Authentication Method screen
34. Select the authentication method and click Install. The ContentServices License
Key screen displays, prompting you for a SOAP server license key.
Interwoven, Inc. 58
Figure 28 ContentServices License Key screen
35. Do one of the following:

If you are not going to use the ContentServices SOAP server, click Install.
If you are going to use the ContentServices SOAP server, and you already have
the license key (the license key is located in the license.txt file which is
created by the ContentServices SDK client installation program), enter it in the
License Key field and click Install.
If you are going to use the ContentServices SOAP server, and you do not have
the license key, click Install. After completing the TeamSite installation
procedure, license the SOAP server as described in the ContentServices SDK
Client documentation. The document is called quick_install_cssdk.html and
it is located in the cssdksamples.zip file on the product CD.
After confirming your SOAP server selection, if you are installing on an English
locale system the VisualAnnotate Admin Email screen displays:
Figure 29 VisualAnnotate Administrator Email screen
36. Enter the email address of the person or group who will be administering your
TeamSite installation and click Install.

The email address is used by the Send Support Email link on the VisualAnnotate
toolbar and error dialogs so that end-users can communicate errors to their TeamSite
administrator.
NOTE
If you are installing on a non-English locale system, VisualAnnotate is not
supported and you do not perform the VisualAnnotate portion of this step.
37. A number of configuration and module preparation steps are performed, and
program files are copied to your system. If ReportCenter is not installed and
configured, a notice is displayed containing instructions for the installation and
configuration. If you need to install ReportCenter, see “Installing ReportCenter as a
Standalone Module” on page 28.
38. When finished, the Install Complete screen displays. Click Done, then reboot the
system.
NOTE
Installing Interwoven Search

If Interwoven Search is already installed on your system and you are upgrading to a
newer release, see:
“Installation Order” on page 20
“TeamSite and Search Compatibility” on page 20
“If Search is Installed” on page 73
The sections that follow describe how to install the Interwoven Search base product
using console mode (Interactive text-based prompts from within a terminal window) and
graphical mode (interactive GUI-based prompts). If you are installing a Search service
pack, see “Installing the Search Service Pack” on page 21.
NOTE
Graphical mode is available only when you are installing directly on the system that
hosts the search server (that is, when you are logged into the console). It is not available
when you are installing from a remote system.
Interwoven Search is installed as a separate module from TeamSite. If you choose to

install Search, you must install TeamSite and reboot your system prior to installing
Interwoven, Inc. 60
search. During the search installation, the installer checks for port availability. By
installing TeamSite first and rebooting the system, you ensure that the search installer
will detect any problems if you attempt to configure search to use a port already used by
TeamSite.
Enabling Incremental Updates

During the search installation, you are prompted to select whether to enable incremental
updates (step 13 on page 70). If you choose not to enable incremental updates during the
search installation, you can go back after the installation and configure search to enable
them. To do so, modify the following properties in the file
iwsearch-home/etc/search.properties on the system where search is installed:
In the java.naming.provider.url=tcp://host:port/ property, set host to the

host name of the machine where TeamSite is installed, and set port to the JNDI
server port of the TeamSite event system.
Ensure that the iw.index.events.enable property is set to true (that is, the line
iw.index.events.enable=true is in the file).
You must restart the search and indexing server(s) for these changes to take effect.
Installing Using Console Mode

Complete the following procedure to install Interwoven Search using the text-based
console mode. This is the only installation mode available if you are installing from a
remote system.
1. Log in as root on the system where you want to install the search server.
Do not use sudo su - to gain root access when installing search. Using sudo su -
instead of su - may cause problems with shutdown, startup, or installation
operations.
global zone.
Either:
Download the installation tar file
(IWOVtssrh-sol-2.1.0.0-Build#####.tar.gz) to a temporary directory where
it can be expanded. This temporary directory will not be the installation
directory. You will be prompted to select the location for the program files by
the installation program. Go to step 3 and continue the installation from there.
Insert the search CD-ROM. Locate the install.sh installation program at the
top level of the CD-ROM contents. Go to step 4 and continue the installation
from there.

3. Uncompress and expand the IWOVtssrh-sol-2.1.0.0-Build#####.tar.gz file by

# gunzip -c IWOVtssrh-sol-2.1.0.0-Build#####.tar.gz | tar xvpf -
This command creates the Search directory and populates it with subdirectories and
files used by the installation program. After the tar file is expanded, change to the
Search directory:
# cd Search
4. Run the following command to start the search installation program:

# ./install.sh -i console
NOTE
If you are installing from a remote system, the installation executes in console mode
by default (even if you do not specify the -i console option).
5. The following introductory text displays:

This is the Interwoven Search 2.1.0.0 installation program.
Respond to each prompt and press Enter to proceed to the next step in
the installation. If you want to change something on a prevous step,
type ‘back’.
You may cancel this installation at any time by typing ‘quit’.
Press Enter.
6. The license agreement text is displayed. Continue to press Enter to scroll through
the entire agreement until you reach this prompt:
DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N)?
To accept the terms, enter Y and press Enter. To decline, enter N and press Enter.
7. You are prompted to select the Search Product Files directory:
This is the directory where Interwoven Search 2.1.0.0 program files will be
installed.
Enter the directory for the Interwoven Search 2.1.0.0 program files:
Default Install Folder: /Interwoven/Search
ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE
DEFAULT
Press Enter to accept the default (/Interwoven/Search) or enter a different path
and press Enter.
8. You are prompted for the name of the TeamSite server:
Enter TeamSite server host name.
TeamSite Server Host: (DEFAULT: localhost):
If you are installing search on the same system as TeamSite, press Enter to select
the default localhost value. If you are installing search on a separate system, enter
the name of the system where TeamSite is installed and press Enter.
Interwoven, Inc. 62
9. You are prompted to specify which search features to enable:

Select functionality to enable on this server. You have to make at
least one choice. By default <Enter> both, Search and Index will be
enabled.
->1- Enable Search?
->2- Enable Index?
ENTER A COMMA-SEPARATED LIST OF NUMBERS REPRESENTING THE DESIRED
CHOICES, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:
To enable both search and indexing, press Enter. To enable just search, enter 1 and
press Enter. To enable just indexing, enter 2 and press Enter.
10. If you did not enable search, you are prompted for information about index server
ports and the location of the shared file system. Go to step 11 and continue from
there.
If you enabled search, you are prompted for information about search server ports
and the location of the shared file system:
Enter Search server port, Search Agent main port, Search Agent callback
port and the location of shared filesystem for Index data.
Search Server Port Number: (DEFAULT: 6720):
Search Agent Main Port Number: (DEFAULT: 6721):

Search Agent Callback Port Number: (DEFAULT: 6722):
Shared Filesystem Location: (DEFAULT: ):
Enter the following information, pressing Enter after each entry: the port number of
the search server (Search Server Port Number), the port number on which the search
server listens to its query agents (Search Agent Main Port Number), the port number
on which the search server listens for callback connections from its query agents
(Search Agent Callback Port Number), and the location of the file system containing
the indexes for TeamSite branches (Shared Filesystem Location).
The shared file system location is the directory where the search indices (or the
Verity collections, if present) are stored. Both the index server and search server
need read access to this directory. The index server also needs write access to this
directory.
The index server and search server can be installed on different machines, in which
case the folder where the collections are created needs to be a shared file system.
However, most typical installations have the index server and search server on a
single machine (a different machine from the TeamSite server). In this setup, the
shared file system location can be a directory on the index/search machine as long
as there is enough disk space available.
Depending on the type of content and the frequency of change, typical index size
can be from 10% to 35% of the backing store size after the baseline indexing. Index
size could be significantly different depending on your system configuration.
11. If you did not enable indexing in step 9, you are prompted for information about the
index server host and port. Go to step 14 and continue from there.
If you enabled indexing in step 9, you are prompted for information about index
server ports and the location of the shared file system:

Enter Index server port, Index Agent main port, Index Agent callback
port and location of shared filesystem for Index data.
Index Server Port Number: (DEFAULT: 6715)
Index Agent Main Port Number: (DEFAULT: 6716):

Index Agent Callback Port Number: (DEFAULT: 6717):
Shared Filesystem Location: (DEFAULT: /):
Enter the following information, pressing Enter after each entry: the port number of
the index server (Index Server Port Number), the port number on which the index
server listens to its indexing agents (Index Agent Main Port Number), the port
number on which the index server listens for callback connections from its indexing
agents (Index Agent Callback Port Number), and the location of the file system
containing the indexes for TeamSite branches (Shared Filesystem Location). If you
are installing the search and index servers on the same system, the Shared
Filesystem Location that you enter here should be identical to the location you
entered in step 10 on page 63.
12. You are prompted to indicate whether incremental updates are enabled:
Enabling incremental updates will cause Index server to listen to JMS
events rather than ignore them.
Enable Incremental Updates? <Y/N> (DEFAULT: Y):
Select whether to enable incremental updates and press Enter. If you enable
incremental updates, the index server automatically updates indexes to reflect any
changes submitted to an indexed branch.
13. If you did not enable incremental updates and you did not enable indexing, you are
prompted for information about the index server host and port (go to step 14), or the
installation is complete (go to step 15).
If you enabled incremental updates, you are prompted for event subsystem
information:
Enter Event Subsystem JNDI server port number. This service is
installed on the TeamSite host.
Event Subsystem JNDI Server Port Number: (DEFAULT: 3035):
Enter the event subsystem port number and press Enter. This is the same JNDI port
number that you specified in step 23 on page 53.
14. If you enabled search but not indexing in step 9, you are prompted for information
about the index server host and port:
Enter Index server host and port number.
Index Server Host Name: (DEFAULT: ):
Index Server Port Number: (DEFAULT: 6715):
Enter the name of the indexing server and the port number on which it listens for
requests from its users. Press Enter after each entry.
15. The installation program configures and installs the search program files on your
system. When the installation is finished, you are prompted to exit the installer:
PRESS <ENTER> TO EXIT THE INSTALLER:
Press Enter. It is not necessary to reboot the system following a search installation.
Interwoven, Inc. 64
Installing Using Graphical Mode

NOTE
The screens shown in this section pertain to Search 2.1 even though some contain the
designation “1.0.0.0.”
Perform the following steps to install Interwoven Search using graphical mode:
1. As a non-root user on the system where you want to install the search server, run the
following command to enable root access to the X11 display:
% xhost +
2. Log in as root on the system where you want to install the search server. If you are
installing on a Solaris 10 system, you must perform the installation in a global zone.
3. Either:
Go to the Interwoven download site and download the installation file
(IWOVtssrh-sol-2.1.0.0-Build#####.tar.gz) to a temporary directory on a
local drive. This temporary directory will not be the installation directory. You
will be prompted to select the location for the program files by the installation
program. Go to step 8 and continue the installation from there.
Insert the Search installation CD-ROM. Locate the install.sh installation
program at the top level of the CD-ROM contents. Go to step 8 and continue the
4. From the temporary directory, uncompress and expand the
IWOVtssrh-sol-2.1.0.0-Build#####.tar.gz file by running the following
command:
# gunzip -c IWOVtssrh-sol-2.1.0.0-Build#####.tar.gz
A Search subdirectory is created, into which the contents of the search installation
package are expanded.
5. Navigate to the Search directory and execute the following command:
# ./install.sh
The Introduction screen displays.

Figure 30 Introduction screen
6. Click Install to continue. The License Agreement screen is displayed.

Figure 31 License Agreement screen
7. Click Next if you agree with the terms.Click Previous or Cancel if you do not agree
with the terms.
The Product Files screen is displayed prompting you for the location where you
want to install the search program files.
Interwoven, Inc. 66
Figure 32 Product Files location screen
8. Click Install to accept the default installation location for the search program files
(/Interwoven/Search) or click Choose to select another location.
NOTE
If you specify an alternate location for the program files (in the next step), you must
use ASCII characters.
After specifying a program file location, you are prompted for the location of the
TeamSite server.
Figure 33 TeamSite Server Host screen
9. If you are installing search on the same system as TeamSite, select the default
localhost value. If you are installing search on a separate system, enter the name of
the system where TeamSite is installed.
Click Install. The Functionality to Enable screen is displayed.

Figure 34 Functionality to Enable screen
10. Enable search, indexing, or both (you must enable at least one). If you enable
search, you will be asked for information about search ports and file system in
subsequent steps. If you enable indexing, you will be asked for information about
indexing ports, file system, and incremental updates in subsequent steps.
Click Install.
If you enabled search, the Search Server Ports and Shared Filesystem Location
screen is displayed. Go to step 11 and continue the installation from there.
If you did not enable search, the Index Server Ports and Shared Filesystem Location
screen is displayed. Go to step 12 and continue the installation from there.
Figure 35 Search Server Ports and Shared Filesystem Location screen
11. Enter the port number of the search server (Search Server Port Number), the port
number on which the search server listens to its agents (Search Agent Main Port
Number), the port number on which the search server listens for callback
connections from its agents (Search Agent Callback Port Number), and the location
of the file system containing the indexes for TeamSite branches (Shared Filesystem
Location).
Interwoven, Inc. 68
The shared file system location is the directory where the search indices (or the
Verity collections, if present) are stored. Both the index server and search server
need read access to this directory. The index server also needs write access to this
directory.
The index server and search server can be installed on different machines, in which
case the folder where the collections are created needs to be a shared file system.
However, most typical installations have the index server and search server on a
single machine (a different machine from the TeamSite server). In this setup, the
shared file system location can be a directory on the index/search machine as long
as there is enough disk space available.
Depending on the type of content and the frequency of change, typical index size
can be from 10% to 35% of the backing store size after the baseline indexing. Index
size could be significantly different depending on your system configuration.
Click Install.
If you enabled indexing in step 10, the Index Server Ports and Shared Filesystem
Location screen is displayed. Go to step 12 and continue the installation from there.
If you did not enable indexing in step 10, the Index Server Host and Port screen is
displayed. Go to step 15 and continue the installation from there.
12. The Index Server Ports and Shared Filesystem Location screen appears:
Figure 36 Index Server Ports and Shared Filesystem Location screen
Enter the port number of the index server (Index Server Port Number), the port
number on which the index server listens to its indexing agents (Index Agent Main
Port Number), the port number on which the index server listens for callback
connections from its indexing agents (Index Agent Callback Port Number), and the
location of the file system containing the indexes for TeamSite branches (Shared
Filesystem Location). If you are installing the search and index servers on the same
system, the Shared Filesystem Location that you enter here should be identical to
the location you entered in step 11.
Click Install. The Enable Incremental Updates screen is displayed.

Figure 37 Enable Incremental Updates screen
13. Select whether to enable incremental updates. If you enable incremental updates,
the index server automatically updates indexes to reflect any changes submitted to
an indexed branch. Click Install.
If you enabled incremental updates, the Event Subsystem JNDI Server Port screen is
displayed. Go to step 14 and continue the installation from there.
If you did not enable incremental updates, either the Index Server Host and Port
screen or the Install Complete screen is displayed. Go to either step 15 or step 16
and continue the installation from there.
14. The Event Subsystem JNDI Server Port screen appears:
Figure 38 Event Subsystem JNDI Server Port screen
Enter the Event Subsystem port number. This is the same JNDI port number that
you specified in step 23 on page 53.
Click Install.
If you enabled search but not indexing in step 10 on page 68, the Index Server Host
and Port screen is displayed. Go to step 15 and continue the installation from there.
Otherwise, go to step 16 and continue from there.
Interwoven, Inc. 70
15. The Index Server Host and Port screen appears:

Figure 39 Index Server Host and Port screen
Enter the name of the indexing server and the port number on which it listens for
requests from its users. Click Install.
16. The installation program configures and installs the search program files on your
system. When the installation is finished, the Install Complete screen is displayed.
Figure 40 Installation Complete screen
Click Done. It is not necessary to reboot the system following a search installation.
NOTE
If you installed Search on a separate server from TeamSite, you must add the following
entry to the last section of iw-home/cssdk/cssdk.cfg on the TeamSite server so that the
TeamSite and Search servers can communicate with each other.
search.server.host: SearchServerHostName
search.server.port: SearchServerPortNumber
search.server.maxConnectionLimit: 10

Licensing TeamSite
To license TeamSite, you must install a valid license file before or during TeamSite
installation. The TeamSite installation program validates the license during the
TeamSite installation procedure.
The TeamSite license file must be named TS.lic, and it must reside in a readable
location on the system that hosts the TeamSite server. The default location for the
TeamSite license file is iw-home/etc.
To obtain a TeamSite license file, go to the Interwoven support site license generation
page at https://support.interwoven.com/supportlogin2.asp and fill in the
following information about the system on which you are installing TeamSite:
Domain name
Host name
Product for which you are requesting a license (for TeamSite, the designation is TS)
Number of CPUs on your system
If a valid installation file is not installed on your system before you begin a TeamSite
installation, the TeamSite installation program prompts you to go to the Interwoven
support site to obtain a license. The prompt contains all the information about your
system that you need when requesting a TeamSite license. You do not need to exit the
TeamSite installation procedure to obtain and install a TeamSite license.
Troubleshooting Licensing Issues

If the TeamSite server fails to run after you have installed a TeamSite license file:
Use the tsisvalid command-line utility (located in iw-home/bin) to verify that the
license is valid:
% tsisvalid path_to_license_file
If the license file is valid, the word valid is displayed in the output.
The TeamSite installation program also creates a license status report file called
tsisvalid.log in iw-home/install. To update that log with license information, or
to create a new log file, issue the following command:
% tsisvalid -l path_to_log_file
If your license key is invalid, tsisvalid will print a report of possible reasons why
it was not able to validate the license.
Look for diagnostic messages in the iwserver.log and iwtrace.log files (located
by default in iw-home/local/logs.
Interwoven, Inc. 72
Upgrading from a Pre-6.7.1 TeamSite Release

The following upgrade paths are supported for upgrading to TeamSite 6.7.1. Contact an
Interwoven representative if you need to upgrade from a TeamSite release not listed
here.
TeamSite 6.7 to TeamSite 6.7.1
TeamSite 6.5 Service Pack 2 to TeamSite 6.7.1
TeamSite 6.1 Service Pack 2 to TeamSite 6.7.1
If Search is Installed
If Search is installed on the system that hosts TeamSite, you must:
Shut down the search and index servers before you upgrade to TeamSite 6.7.1.
After you upgrade to TeamSite 6.7.1, upgrade Search to a compatible release as
described in “TeamSite and Search Compatibility” on page 20.
Restart the search and index servers after the TeamSite and Search upgrades are
complete.
Changes to iw.cfg
The configuration of several TeamSite features is now controlled by the User Interface
Toolkit (UITK) rather than the main TeamSite configuration file iw.cfg. See the
TeamSite Release Notes for details about these features.
Starting with TeamSite 6.7, iw.cfg is created as iw.cfg.example so that any

customizations you made to iw.cfg prior to a TeamSite 6.7 installation are retained.
You can open and read the iw.cfg.example file (and refer to the TeamSite
Administration Guide) to determine if there are new settings that you would like to
implement. If there are, you can copy them into your iw.cfg file.
Refer to “Post-upgrade Considerations” on page 79 for details about other configuration

files that may be affected by the upgrade procedure.
Upgrade Procedure
NOTE
The screens shown in this section pertain to TeamSite 6.7.1 even though some contain
the designation “6.7.0.0.”

Perform the following procedure to upgrade to TeamSite 6.7.1:

1. If necessary, upgrade your operating system and Web server to releases that are
supported by TeamSite 6.7.1. For details see the TeamSite Release Notes.
2. Log on to the TeamSite host system as root.
NOTE
Do not use sudo su - to gain root access when installing TeamSite. Using sudo su
- instead of su - may cause problems with shutdown, startup, or upgrade
operations.
3. Back up your TeamSite iw-store directory, and your existing TeamSite

configuration files, roles files, and any customized site-specific files. These files
include the following:
/etc/iw.cfg
iw-home/local/config/templates.cfg
iw-home/local/config/autoprivate.cfg
iw-home/conf/roles/tsusers.xml
iw-home/conf/roles/tsroles.xml
iw-home/conf/roles/*.uid
iw-home/conf/tsgroups.xml
Any server start or stop scripts in the /etc/init.d directory

Any other customized files such as custom login screens or a custom-configured
iw-home/private/bin/iwetcboot file
4. Stop the TeamSite server with the following command:

# /etc/init.d/iw.server stop_all
5. Stop the Web server that supports TeamSite.

global zone. Either:
Download the installation tar file (IWOVts-sol-6.7.1.0.Build#####.tar.gz)
from there.
7. Uncompress and expand the IWOVts-sol-6.7.1.0.Build#####.tar.gz file by
# gunzip -c IWOVts-sol-6.7.1.0.Build#####.tar.gz | tar xvpf -
Interwoven, Inc. 74
# cd TeamSite

# ./install.sh
9. The installer is launched and the Introduction window displays.

10. Click Next. When the installation program locates an existing TeamSite installation,
it displays the Previous Installation Detected screen showing the TeamSite version
and the directory where it is installed.
11. Click Next. The License Information screen displays instructions for obtaining a
TeamSite license. If you have not yet obtained and installed a TeamSite license file,
do so now by following the instructions shown onscreen. When you finish, click
Next and the License File window displays.
12. The TeamSite license file must be named TS.Lic, and it must reside in a readable
location on the TeamSite server. The TS.Lic file also must be readable by the user
iwts(the iwts user replaces root as the owner of most TeamSite processes starting
with TeamSite 6.7.1). If you are upgrading from TeamSite 6.7.0, ownership of
the existing TS.Lic file is updated automatically by the TeamSite installation
program. To install TS.lic in the default location (iw-home/etc), click Next.
13. If the license if is valid, an Information screen prompts you to proceed by clicking
Install.
14. The installation program checks module versions in the existing installation to
ensure that they are compatible with the new modules being installed.
If all modules are compatible, click Install and continue the upgrade from the next
step.
If there are incompatibilities between new and currently installed modules, they are
displayed together with the following message:
The following error occurred. The installation will now quit.
The module incompatibilities make installation of TeamSite 6.7.1 impossible at this

time. Note which modules are incompatible and click Next (in graphical mode) or
press Enter (in console mode) to abort the installation. You must update the
currently installed modules to correct the displayed incompatibilities before
attempting another TeamSite 6.7.1 installation.
15. The Web Ports screen displays, prompting you for the port numbers used by the
Interwoven Web Daemon.
TeamSite uses two Web servers:
The Interwoven Web server—Installed with TeamSite, and used to render the
TeamSite UIs. By default, it is assigned port 80 for HTTP connections and port
443 for HTTPS (secure) connections.

If you do not use port 80 for the Interwoven Web server, users must explicitly
specify the alternate port number in the URL each time they access the
TeamSite UI.
The non-Interwoven Web server (for example, IIS)—Used to render the content
stored in the TeamSite Content Store. By default, it is assigned port 81 and
labeled Web Server. If this Web server is using a port other than 81, either it
must be reconfigured to use port 81, or you must specify the port number that it
uses in this step.
NOTE
In some earlier releases of TeamSite, port 80 was assigned to the existing
(non-Interwoven) Web server by default. At the time, this Web server rendered the
TeamSite UIs and content files.
16. Click Next to accept the default values, or edit the values and then click Next.
If any of the ports are already being used, you are prompted to either change them
by clicking Previous and returning to the Web Daemon Configuration screen, or
clicking Continue to force the busy port process to give up the port.
After selecting the ports, the Web Server screen displays.
17. Either:
Click Next to confirm that you are using an Apache Content Web Server.
The Apache Configuration window displays.
Select No and click Next (skip to step 20).
18. Press Enter to accept the default location of the Apache Web server configuration
file, or enter a different location and press Enter.
You are prompted for the location of the Apache bin directory.
19. Press Enter to accept the default location of the Apache binary files, or enter a
different location and press Enter.
You are then prompted whether to install Samba to enable Windows PCs to connect
to your Solaris TeamSite server.
20. Press Enter to accept the default (install Samba), or select No (do not install Samba)
and press Enter.
If you chose not to install Samba, skip to step 22.
If you chose to install Samba, you are prompted for a workgroup name.
21. Press Enter to accept the default workgroup name (interwoven), or enter a different
name and press Enter.
The Event Subsystem And Utility Daemon Ports screen is displayed.
22. Click Next to accept the default ports used by the event subsystem and utility
daemon, or edit the values and click Next. If you specify a port that is invalid or
busy, you are prompted to enter a different port number.
Interwoven, Inc. 76
After you select the event subsystem and utility daemon ports, the Database Type
screen is displayed.
23. Select the type of database used by the event subsystem. If you select default, the
event subsystem will store event information in a flat file rather than in a database.
It is strongly recommended that you select a database instead of default, so that
event information can be stored and processed in a higher performing and scalable
manner making use of full database functionality. If you select default, the
TeamSite Report Server License Key screen is displayed. Go to step 26 and continue
the installation procedure from there.
If you select a database rather than default, the Database Configuration screen is
displayed.
24. Enter the name of the server that hosts the event subsystem database (Database
Password).
If you selected default, oracle, or MySQL in step 23, the ReportCenter License Key
screen is displayed. Go to step 26 and continue the installation procedure from there.
If you selected mssql or db2 in step 23, the Database Drivers Directory screen is
displayed.
25. Enter or browse to the location of the drivers used by the event subsystem database.
Click Install. The TeamSite ReportCenter License Key screen is displayed.

26. If you plan to use ReportCenter, enter the ReportCenter license key you received
from Interwoven and click Next. Go to step 27 and continue the installation
procedure from there.
If you do not plan to use ReportCenter, click Next without entering a license key. Go
to step 31 and continue the installation procedure from there.
27. The Database Type screen is displayed for ReportCenter.
Select the type of database used by ReportCenter. If you select db2 or mssql, you are
also prompted to enter the location of the database drivers. Click Next. The
Database Configuration screen is displayed.
28. Enter the name of the server that hosts the ReportCenter database (Database Server
Password).
Click Install. The Crystal Enterprise Report Information screen is displayed.

NOTE
This screen might not display if the installer determines that Crystal Enterprise is
already configured.
29. Enter the name of the system that hosts Crystal Enterprise (Crystal Enterprise Host
are stored (Crystal Reports Root Path).
Click Next. The Crystal Enterprise Report Database Information screen is
displayed.
NOTE
already configured.
30. Enter the name of the database connection on the Crystal Enterprise system
assigned by the database administrator (DBName).
Click Next. The Authentication Method screen is displayed.
NOTE
already configured.
31. An Information screen is displayed containing instructions for converting user and
group permissions to support the configurable roles and delegated administration
features of TeamSite 6.7.1. See Appendix C, “Migrating Roles and Permissions” for
details about this conversion, which is performed following the TeamSite
installation. Click Next to continue installing TeamSite.
If you did not configure TeamSite Reporting, an Information screen containing
post-installation configuration steps is displayed. Click Next to continue installing
TeamSite.
32. A number of configuration and module preparation steps are performed, and
program files are copied to your system. When finished, the Install Complete screen
displays. If there were any compilation errors, they are described onscreen.
33. Click Done, then reboot the system.
NOTE
Interwoven, Inc. 78
Post-upgrade Considerations
This section describes the following areas to keep in mind following an upgrade from a
pre-6.7.1 TeamSite release:
Content and Permission Migration
Configuration Files
Web Server Configuration
Workflow Roles
If you upgraded to TeamSite 6.7.1 from 6.7.0, you must manually merge the
WorkflowUser and WorkflowAdmin roles from roles.xml.example to your existing
roles.xml file. If you do not merge these roles, Workflow Modeler and related
TeamSite features will not work correctly.
Content and Permission Migration
TeamSite 6.7 introduced the concept of configurable roles and delegated administration.
Under this arrangement, the Author, Editor, Reviewer, and Administrator roles can be
configured to include or exclude some capabilities. Additionally, users can now have
different roles on different branches, and you can create entirely new roles with nearly
any capability for your site.
To support these new capabilities, starting with release 6.7 TeamSite uses a different
model to establish user and group permissions, roles, and group memberships. To take
advantage of these capabilities, you must migrate your existing permissions and roles to
the new model. See Appendix C, “Migrating Roles and Permissions” for details about
performing this migration.
Configuration Files
The TeamSite upgrade program does not overwrite your old configuration files. Instead,
it creates a backup (.tsupgrade.bak) version of certain files that you can use as an
archive, or use to manually integrate your customizations into the TeamSite
environment. The files include:
httpd.conf.template—The TeamSite upgrade process creates an
httpd.conf.template.tsupgrade.bak file based on httpd.conf.template. This
file contains the default contents of the previous TeamSite release, plus any custom
entries that you (or other Interwoven applications) added to the file. This file is
created in iw-home/iw-webd/conf.
An additional file, httpd.conf.template.example, is also provided starting with
TeamSite 6.7. This file resides in iw-home/iw-webd/conf.
You must manually merge any customizations from
httpd.conf.template.tsupgrade.bak into httpd.conf.template.example. You

can use diff or any file comparison utility on the new and old versions of the files
to determine the differences. You can then apply the appropriate changes to the new
file.
After merging the files, rename httpd.conf.template.example to
httpd.conf.template.
Be careful to note changes that apply to the configuration of other Interwoven

products including—but not limited to—DataDeploy and TeamSite FrontOffice. If
you do not merge these changes, the associated products will not operate.
The updates to httpd.conf.template require that the TeamSite 6.7 and later
changes to rewrite.conf.template be applied as described in the next bullet.
After updating httpd.conf.template, issue iw-home/bin/iwreset -ui.
rewrite.conf.template—The TeamSite upgrade process creates a
rewrite.conf.template.tsupgrade.bak file based on rewrite.conf.template.
This file contains the default contents of the previous TeamSite release, plus any
custom entries that you (or other Interwoven applications) added to the file. This file
is created in iw-home/iw-webd/conf.
An additional file, rewrite.conf.template.example, is also provided starting with
TeamSite 6.7. This file resides in iw-home/iw-webd/conf.
You must manually merge any customizations from
rewrite.conf.template.tsupgrade.bak into rewrite.conf.template.example.
You can use diff or any file comparison utility on the new and old versions of the
files to determine the differences. You can then apply the appropriate changes to the
new file.
After merging the files, rename rewrite.conf.template.example to
rewrite.conf.template.
After updating rewrite.conf.template, issue iw-home/bin/iwreset -ui.

The WebDesk Web application (and the corresponding GUI) is no longer part of
TeamSite. It has been replaced by a Web application named ContentCenter (which
has two interfaces: Standard and Professional). The new rewrite.conf.template
has rules that forward requests from the old WebDesk “iw” context to the new
ContentCenter “iw-cc” context (for backward compatibility). Therefore, both
products are referenced in the new configuration files.
Also included are changes that apply to the configuration of other Interwoven
products including—but not limited to—DataDeploy and TeamSite FrontOffice. If
you do not merge these changes, the associated products will not operate.
available_templates.cfg—If the available_templates.cfg file is detected by
the upgrade program, the file is not modified. Instead, the new version of the file
(that is, the default TeamSite 6.7.1 available_templates.cfg file) is installed as
available_templates.cfg.example.
If you want to use any of the new templates that are part the 6.7.1 release, you must
manually modify your existing available_templates.cfg file to reference the new
templates.
Interwoven, Inc. 80
If the available_templates.cfg file is not detected by the upgrade program, the

default TeamSite 6.7.1 version of available_templates.cfg file is installed.
iw.cfg—The event subsystem requires that the ew_enable variable be set to true in
the iw.cfg file. Verify that this entry exists in iw.cfg. If it does not, add
ew_enable=true.
VisualFormat files—If VisualFormat is installed on your system, restore

ewebeditproevents.js and manually merge locale0409.xml with the file
locale0409b.xml, from version 4.2.0.11 of VisualFormat, supplied as part of
TeamSite 6.7.1.
toolkits.xml—The toolkits.xml file packaged in TeamSite 6.7.1 includes
enhancements necessary for the successful operation of this release in languages
other than English. The installation process respects modifications you may have
made to previous versions of toolkits.xml by not over writing this file.
To ensure that these enhancements are migrated to your existing version of
toolkits.xml, located in iw-home/local/config/lib/content_center, merge
any customizations previously made by you to toolkits.xml (typically, there will
be none, unless you have the customer_samples toolkit enabled) into the
toolkits.xml.example file delivered with this release (you can use diff or any file
comparison utility to determine any differences).
NOTE
Depending on which version of TeamSite was originally installed on your system,
there could be differences between the original toolkits.xml file delivered with
your previous TeamSite release and the toolkits.xml.example file delivered with
this release. Ignore any differences except those that you made to toolkits.xml.
Rename toolkits.xml to toolkits.xml.old. Then, rename

toolkits.xml.example to toolkits.xml.
After updating toolkits.xml appropriately, issue

iw-home/iw-perl/bin/iwperl iw-home/bin/make_toolkit.ipl.
search.properties—The search.properties file packaged in TeamSite 6.7.1

includes enhancements necessary for the successful operation of this release. The
installation process respects modifications you may have made to previous versions
of search.properties by not over writing this file.
To ensure that these enhancements are migrated to your existing version of
search.properties, located in iwsearch-home/etc, merge any customizations
previously made to search.properties into the search.properties.example file
delivered with this service pack (you can use diff or any file comparison utility to
determine any differences).
NOTE
Do not add new or remove existing properties from search.properties.example.
Merge only the values that you previously customized in search.properties.

Rename search.properties to search.properties.old. Then, rename

search.properties.example to search.properties.
NOTE
The file search.private.properties was also included with TeamSite starting
with TeamSite 6.5 Service Pack 1. This file should not be modified.
After updating search.properties appropriately, restart your index and search

servers so that they use the new configuration values:
1. Issue:
/etc/init.d/iw.tsindex stop (if you have not already done this)
/etc/init.d/iw.tsindex start
2. Issue:
/etc/init.d/iw.tssearch stop (if you have not already done this)
/etc/init.d/iw.tssearch start
Web Server Configuration
Several Web server configuration changes have been made starting with TeamSite 6.0.
After completing the upgrade procedure, proceed to the next chapter and perform the
Web server configuration.
Perl Scripts and Libraries
Starting with TeamSite 6.1, iw-perl is based on Perl 5.8.2. Following an upgrade from a
pre-6.1 release of TeamSite, your original iw-perl directory is moved to
iw-perl.oldiw-perl.# (where # is the ID of the process performing the directory move
operation; it is possible to have multiple iw-perl.# directories if you perform multiple
upgrades). Any scripting modifications or module additions made to the original
iw-perl directory are preserved in those locations.
To restore any custom Perl scripts or modules following an upgrade from a pre-6.1
release of TeamSite, you must retrieve them from iw-perl.oldiw-perl.# and move
them back to their original location(s). You must also ensure that they are compatible
with Perl 5.8.2 standards.
If you are upgrading from TeamSite 6.1 to this release, the iw-perl directory is not
renamed, and you do not need to check for differences or merge changes.
Uninstalling TeamSite and Search

If you intend to uninstall the base product, first uninstall any service packs and patches
before you uninstall the base product. All installed service packs and patches must be
Interwoven, Inc. 82
uninstalled in the reverse order of their installation (the most recently installed service
pack or patch must be uninstalled first, the next most recent second, and so on).
Service Pack Uninstallation

2. TeamSite:
a. Navigate to iwinstall/products/TeamSite/TS671SP1/UninstallData.
b. Start the Service Pack 1 uninstallation process:
./TS671SP1
The service pack is removed from the system.

Search:
a. Navigate to iwinstall/products/Search/Search21SP1/UninstallData.
b. Start the Service Pack 1 uninstallation process:
./Search21SP1
The service pack is removed from the system.

3. Reboot the system.
Base Release Uninstallation

If you intend to reinstall TeamSite after uninstalling it, it is highly recommended that
you back up your TeamSite iw-store directory and your existing TeamSite
configuration files, roles files, and any customized site-specific files. If necessary, you
can then merge the backup files with the new versions to retain site-specific
customizations. Files to back up include the following:
iw-home/etc/iw.cfg
iw-home/local/config/templates.cfg
iw-home/local/config/autoprivate.cfg
iw-home/conf/roles/tsusers.xml
iw-home/conf/roles/tsroles.xml
iw-home/conf/roles/*.uid
iw-home/conf/tsgroups.xml
Any server start or stop scripts in the /etc/init.d directory

Any other customized files such as custom login screens or a custom-configured
iw-home/private/bin/iwetcboot file
Complete the following procedures to uninstall TeamSite and Interwoven Search.

NOTE
The TeamSite and Search uninstallers rely on information in the
/Interwoven/iwinstall directory. Therefore, do not modify or remove files in that
directory.
TeamSite
If you do not have the required X11 environment or DISPLAY variable set, or if you are
uninstalling remotely, the uninstallation automatically runs in console mode.
1. Log on to your TeamSite host system as root.
2. Stop the TeamSite server with the following command:
3. Change to the uninstaller directory:

# cd /Interwoven/iwinstall/products/TeamSite/UninstallerData
Notes: The installation directory iwinstall is typically located one level up from
iw-home (/Interwoven/TeamSite by default). If you installed TeamSite in a
non-default location, locate iw-home by issuing the iwgethome command.
4. Start the uninstallation program with the following command:
# ./TeamSite
By default, the uninstall program runs in graphical mode. To specify console mode,
use the following command:
# ./TeamSite -console
5. You are prompted to press Enter when the uninstallation is complete.

6. If you need to uninstall Interwoven Search, proceed to the next section. If not,
reboot the system.
NOTE
Interwoven, Inc. 84
Search
If you do not have the required X11 environment or DISPLAY variable set, or if you are
uninstalling remotely, the uninstallation automatically runs in console mode.
1. Log on to your search host system as root.
2. Stop the search server with the following command:
3. Change to the uninstaller directory:

# cd /Interwoven/iwinstall/products/Search/UninstallerData
Note: The installation directory iwinstall is typically located one level up from
iw-home (/Interwoven/TeamSite by default). If you installed TeamSite in a
non-default location, locate iw-home by issuing the iwgethome command.
4. Start the uninstallation program with the following command:
# ./Search
By default, the uninstall program runs in graphical mode. To specify console mode,
use the following command:
# ./Search -console
5. You are prompted to press Enter when the uninstallation is complete.

6. Reboot the system.
NOTE

Interwoven, Inc. 86
Chapter 3
Configuring Web Servers
This chapter describes how to configure your system’s Web server after you have
installed or upgraded TeamSite. Configuration procedures for the following Web servers
are included:
Apache Web Server
IBM HTTP Server
Sun iPlanet Web Server
The chapter contains information about the following topics:

Interwoven Web Server Port Number
Configuring the iw-mount Alias
Configuring CGI Programs
Enabling Server-Side Include Requests
Stopping and Restarting the Web Server
Redirecting NSAPI HTTPS Requests
Interwoven Web Server Port Number

You must provide the Interwoven Web server (iwwebd) port number value during
installation. The default values are 80 for HTTP and 443 for HTTPS. These port
numbers are recorded in /etc/iw.cfg as follows (assuming the default values):
[iwwebd]
http_port=80
https_port=443
When the installation program configures iwwebd, the port number value also gets
recorded in the iwwebd configuration file iw-home/iw-webd/conf/iwwebd.conf as
follows:
Listen 80
Listen 443
The number values assigned to http_port and https_port in iw.cfg and iwwebd.conf
must match. (Specifying the HTTPS port is not required if you are not using HTTPS.)

Chapter 3: Configuring Web Servers
The installation program also requires that you provide a default port number for the
customer Web server. The default value for this port is 81. This port number is recorded
in /etc/iw.cfg as follows (assuming the default value of 81):
[iwproxy]
customer_webserver_port=81
Configuring the iw-mount Alias

The iw-mount alias enables your Web server to access the NFS server mount point. If
you are upgrading from a pre-6.0 release, the iw-mount alias now incorporates the
functionality of the former iw, iw-bin, and iw-icons aliases. The process for
configuring iw-mount varies depending on the type of Web server you are using.
Configuration details are in the following sections.
Configuring iw-mount for iPlanet

Complete the following procedure to configure iw-mount using the iPlanet Server
Administrator (you can also manually edit the obj.conf file using a text editor):
1. Open the Server Administrator.
2. In the Manage Servers section of the Server Administrator, select the appropriate
server name and click Manage.
The Server Administrator returns the status of the selected server.
Figure 41 iPlanet Server Manager
Content
Management
link
3. At the top of the Server Administrator, click the Content Mgmt tab. The Content
Management screen displays.
4. On the left panel of the Server Administrator, click the Additional Document
Directories link.
Interwoven, Inc. 88
Figure 42 iPlanet Content Management screen
Additional
Document
Directories
link
The Additional Document Directories panel displays.

5. In the Additional Document Directories screen, make the following entries:
In the URL Prefix field, enter iw-mount/
In the Map To Directory field, enter /.iwmnt/
Figure 43 Configuring iw-mount in iPlanet
6. Click OK, and save your changes when prompted.
Configuring iw-mount for Apache

To configure the iw-mount alias for Apache, enter the following section in the
httpd.conf file:
<Directory "/.iwmnt">
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny

Allow from all

</Directory>
Alias /iw-mount/ /.iwmnt/
During the TeamSite installation, if you selected a location other than root (/) for iwmnt,
you must specify it in httpd.conf. For example, if you specified /var for the .iwmnt
location, the httpd.conf entry would be:
<Directory "/var/.iwmnt">
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
</Directory>
Alias /iw-mount/ /var/.iwmnt/
Configuring CGI Programs

If your system will be executing CGI programs in TeamSite workareas, you must edit
the httpd.conf file as described in this section. After making the required edits, you
must restart the Web server for the changes to take effect. If you reinstall your Web
server or lose your automatically modified configuration files, you can refer to the
installation log to duplicate the changes previously made.
Add the following section to the obj.conf file:

<Object ppath="/.iwmnt/*/cgi-bin/*">
ObjectType fn="force-type" type="magnus-internal/cgi"
Service fn="send-cgi"
</Object>
For Apache, perform the following steps:

1. Add the ExecCGI directive to the Directory section in the httpd.conf file as shown
below:
Options Indexes FollowSymLinks ExecCGI
AllowOverride None
Order allow,deny
Allow from all
</Directory>
2. Add the following section:
<Location ~ "/iw-mount/.*/cgi-bin/.*">
SetHandler cgi-script
</Location>
Interwoven, Inc. 90
Enabling Server-Side Include Requests

If your Web site does not use SSIs, you do not need to enable them.
If your Web site uses SSIs, you must configure your Web server to use server-side
includes by specifying that it parse .shtml files. For more information on this process,
consult the NCSA server-side include tutorial at:
http://hoohoo.ncsa.uiuc.edu/docs/tutorials/includes.html
If you choose to enable VisualPreview for SSIs, you must install the redirector module
as described in the following section. The installation steps vary depending on the type
of Web server you are using.
Installing the Redirector Module for iPlanet

1. Open the obj.conf file in a text editor.
The obj.conf file is part of the iPlanet product and is typically found in the
following location: /webserver_install_dir/https_servername/config.
2. In the Init section, add the two Init directives as follows, substituting the path
name to the iwrewrite.nsapi.solaris.so file as appropriate for your installation.
First entry (all on one line):
Init fn="load-modules"
shlib="/installation_directory/iw-home/lib/iwrewrite.nsapi.solaris
.so" funcs="iwrewrite"
Second entry:
Init fn="iwrewrite"
3. In the default object description, add the following NameTrans as the first
NameTrans function, preceding all others:
NameTrans fn="iwrewrite"
4. In the default object description, add the following PathCheck as the last
PathCheck function:
PathCheck fn="iwrewrite"
Installing the Redirector Module for Apache

If you are using an Apache Web server, there are two different types of redirector
modules available. The type of module you use depends on your configuration and is
determined by the procedure that follows. Complete the procedure to install and
configure the appropriate redirector module for Apache:
1. Determine if mod_so is enabled by running the following directive:
# apache-home/bin/httpd -l

2. Look for mod_so.c in the output, then do one of the following:

If mod_so.c is in the output, proceed to Step 3.
If mod_so.c is not in the output, run the following configuration directive to
configure and build Apache with mod_so:
# ./configure --enable-shared=max --prefix=//path_to_apache_home
# make
# make install
3. Determine if your Apache Web server has a mod_ssl patch by running the following
command:
httpd -V
4. Look for -D EAPI in the output.

If the output contains -D EAPI, use the mod_iw_ts_rewrite_eapi.so module.
If the output does not contain -D EAPI, use the mod_iw_ts_rewrite.so module.
5. Edit the LoadModule section of the httpd.conf file as follows:
If you are using the mod_iw_ts_rewrite_eapi.so redirector module:
LoadModule iw_ts_rewrite_module
iw-home/lib/mod_iw_ts_rewrite_eapi.so
If you are using the mod_iw_ts_rewrite.so redirector module:

LoadModule iw_ts_rewrite_module iw-home/lib/mod_iw_ts_rewrite.so
NOTE
On IHS servers, the system will fail if the redirector module mod_iw_ts_rewrite is
not loaded as the last module in the configuration. To avoid this, add the following
as the last entry in the httpd.conf file:
LoadModule iw_ts_rewrite_module iw-home/lib/mod_iw_ts_rewrite.so

AddModule mod_iw_ts_rewrite.c
6. Enable relative SSIs in .shtml files as follows:

a. Add the Includes statement to the Directory section of the httpd.conf file as
shown in the following example:
Options Indexes FollowSymLinks ExecCGI Includes
AllowOverride None
Order allow,deny
Allow from all
</Directory>
b. Add or uncomment the <If Module mod_mime.c> section in the httpd.conf
file as follows:
<If Module mod_mime.c>
AddType text/html .shtml
AddHandler server-parsed .shtml
</IfModule>
Interwoven, Inc. 92
7. Edit the end of the AddModule section of the httpd.conf file as follows:
AddModule mod_iw_ts_rewrite.c
Web Server Plug-ins and VisualPreview

The VisualPreview functionality in the ContentCenter GUIs requires that your content
Web server use a plug-in that sets the x-iw-ts-vpath response header.
In some cases, the URL sent by iwproxy in its request to the content Web server (also
known as the “customer Web server” and the “origin server”) does not reflect the vpath
of the underlying document in the file system. For example, the following directory
URL:
http://iis-dev.example.com:84/iw-mount/ar0/main/br0/STAGING/products/
may be translated by the origin server to display the file:

/ar0/main/br0/STAGING/products/index.html
Because this translation is done internally by the content Web server, there is no way for
iwproxy to know what vpath it should use when displaying the VisualPreview toolbar.
However, it is possible to use the plug-in interface of most Web servers to set a response
header that contains the vpath of the file actually used to serve the request. To address
this, (starting with release 6.0) includes the x-iw-ts-vpath response header. When set,
it is used by iwproxy to build a VisualPreview toolbar that references the given
(hex-escaped) vpath.
The plug-in for your content Web server that sets the x-iw-ts-vpath response header is
available as follows:
If you are using Apache or iPlanet, the required module source code is distributed
with TeamSite 6.1.
If you are using another Web server, you need to create a custom plug-in that sets
the x-iw-ts-vpath header. That response header must contain the URL-escaped,
natively encoded vpath that corresponds to the current request.
Detailed information about using these plug-ins is contained in the following sections.
NSAPI Plug-ins
Starting with TeamSite 6.0, the existing NSAPI Web server plug-ins implement the
x-iw-ts-vpath response header. If you are upgrading to TeamSite 6.7 and currently use
the NSAPI plug-in, note that for the x-iw-ts-vpath feature to work, the NSAPI plug-in
needs an additional callback registered, as documented in “Installing the Redirector
Module for iPlanet” on page 91.

Apache Plug-ins
includes two Apache modules that set the x-iw-ts-vpath response header for your
content Web server:
mod_iw_ts_vpath (for Apache 1.3)
mod_a2_iw_ts_vpath (for Apache 2.0)
These modules are shipped as source, under iw-home/src/apache/. To compile them,

use the apxs utility included with your installation of Apache.
There may be precompiled binaries available from Interwoven Support for common
configurations (for example, Apache 1.3.28 with mod_ssl on Solaris 2.8).
Custom Plug-ins
If you are using a content Web server other than IIS, HTTP, Apache, iPlanet, or Sun
ONE, it should be possible for you to write a custom plug-in that sets the
x-iw-ts-vpath response header. You can reference the source for each of the Apache
modules (which is only a few lines of code).
Most Web servers have some sort of “hook” for determining whether the current user is
allowed to see the requested file (that is, the file the Web server has decided to use to
service the request). The custom plug-in needs to be able to:
Determine what the mapped /iw-mount/ path is. For example:
The ISAPI (Windows) plug-in assumes that /iw-mount/ has been mapped to a
drive letter.
The Apache plug-ins run an internal subrequest in the server to find out to
which path /iw-mount/ maps.
Strip the leading /.iwmnt (or similar) from the path.
Hex-escape the vpath.
Set a response header called x-iw-ts-vpath.
Stopping and Restarting the Web Server

Before you activate your configuration changes by rebooting your Web server, ensure
that the docroot lines in the [iwproxy_remap] section of the iw.cfg file do not end with
a trailing slash. For example:
Interwoven, Inc. 94
[iwproxy_remap]
extranet_branch=/main/extranet
global_default_map=/
[extranet_branch]
_docroot=/htdocs No trailing slash allowed
/icons/=/icons/
/images/=/multimedia/img/ Trailing slashes allowed
After ensuring that all _docroot trailing slashes in the [iwproxy_remap] section are
deleted, stop and restart your Web server.
Redirecting NSAPI HTTPS Requests

You can configure to redirect HTTPS requests from so they are served from the Web
daemon (iwwebd) over HTTP. To do this, your system must contain two Web servers:
A secure Web server set up to process HTTPS requests.
A non-secure server of any type that processes Web daemon HTTP requests.
NOTE
HTTPS requests redirected to the Web daemon no longer have HTTPS security.
To redirect HTTPS requests, set the following directive in the [nsapi] section of your
iw.cfg file:
redirect_https_to_http=yes
When redirection is enabled, all HTTPS requests originating from the browser and
received by the secure server’s NSAPI plugin are redirected to the web daemon. The
web daemon then sends the requests to the non-secure server just as it would any request
originating from the browser. For example, if the NSAPI plugin on the secure server
receives an HTTPS request for a file in a area such as:
https://teamsite_host/iw-mount/branch1/STAGING/bio.html
where teamsite_host specifies the host name (such as www.example.com), then the
request is redirected to the web daemon as follows:
http://teamsite_host:iwwebd_port/iw-mount/branch1/STAGING/bio.html
where iwwebd_port specifies the port number.
During the redirection process, some browsers will display a message warning that the
request is being sent to an insecure document. This is normal browser behavior. If you
see such a message, click OK to proceed.

Redirecting to an Index Page

Your Web server can be configured so that when end-users navigate to a root workarea
using VisualPreview, the server forwards them to an index page. For example, if you go
to http://www.acme.com, the server forwards the request to
http://www.acme.com/index.html.
This is an issue in the Content module of the ContentCenter Standard interface, because
if users click a workarea name (as shown) instead of the Browse link, TeamSite
navigates to the workarea in VisualPreview mode and displays the index of the Web site.
Figure 44 ContentCenter Standard Content module
If you do not configure your Web server to redirect to an index page, most Web servers
display a 404 error. For more information, see the connection discussion at the end of
the “Customizing GUI Behavior” chapter in the User Interface Customization Guide.
Where to Go From Here

After completing the Web server configuration, do one of the following:
If you installed Samba, configure it to work with TeamSite as described in the next
chapter; otherwise:
Continue the initial configuration by creating at least one TeamSite client as described
in Chapter 5, “Configuring TeamSite Clients”.
Interwoven, Inc. 96
Chapter 4
Configuring Samba
The TeamSite installation program includes the option to install Samba, a network
protocol that makes it possible for PCs to mount UNIX drives as Windows networked
drives. Samba is a server-side solution that does not require client software. This makes
TeamSite easy to administer because your system administrator does not need to update
and correct issues with client computers.
Editing the iw.smb.conf File

The default TeamSite Samba configuration file is iw-home/samba/lib/iw.smb.conf. If
you had Samba installed before performing the TeamSite installation, the file may be in
/usr/local/samba/etc/smb.conf or /usr/local/samba/lib/smb.conf.
To configure Samba to work with TeamSite, edit your Samba configuration file as
follows:
1. Set the following global option to grant access privileges on a user-by-user basis:
security = user
2. Add the following section to your Samba configuration file (the settings are
described in the table that follows):
[iwmain]
comment = directory main branch of TeamSite file system
public = no
create mode = 0775
force create mode = 0775
force directory mode = 0775
writable = yes
locking = no
share modes = no
preserve case = yes
short preserve case = yes
path = /iwmnt/default/main

Chapter 4: Configuring Samba
The following table describes the directives from the [iwmain] section:
Table 9 Samba configuration directives

Directive Description
public=no Specifies that authentication is required to view the
contents of the Samba mount.
create mode=0775 Sets UNIX permissions on all newly created files to
0775.
force create mode=0775 Sets the minimum UNIX permissions on all newly
created files to 0775.
force directory Sets the minimum UNIX permissions on all newly
mode=0775 created directories to 0775.
writable=yes Enables users to write to the Samba mount
(writable=no disables the ability to do writes using
Samba).
locking=no Turns off locking. Locking must be turned off because
TeamSite has its own locking.
share modes=no Turns off SMB deny modes.
preserve case=yes Keeps the original case of file names.
short preserve Keeps the case of 8.3 filenames rather than displaying
case=yes them as all uppercase.
path=/iwmnt/default/ma The directory to be mounted.
in
3. Save and close the iw.smb.conf file.

4. Restart Samba for your changes to take effect. The following example shows the
commands for Samba as distributed with TeamSite. If you have a different version
of Samba, the commands could be slightly different.
% /etc/init.d/iw.samba stop
% /etc/init.d/iw.samba start
To mount any other TeamSite area:

1. Copy and paste the [iwmain] section in your Samba configuration file.
2. Change the name of the section from [iwmain] to a unique identifier.
3. Edit the path line to point to the area to be mounted.
4. Restart Samba for your changes to take effect.
Verify that Samba is running, then continue the initial configuration by creating at least
one TeamSite client as described in the next chapter.
Interwoven, Inc. 98
Troubleshooting Samba
If Samba is not running, ensure that the version of Samba that is installed with
TeamSite provides a link between /usr/local/samba/lib/smb.conf and
iw-home/samba/lib/iw.smb.conf.
If the /usr/local/samba/lib directory does not exist, complete the following

procedure:
1. Create the directory:
% mkdir -p /usr/local/samba/lib
2. Create the iw.smb.conf file if it does not already exist:

% cp ìwgethome`/samba/lib/iw.smb.conf.ex
ìwgethome`/samba/lib/iw.smb.conf
3. Link the file:

% ln -s ìwgethome`/samba/lib/iw.smb.conf /usr/local/samba/lib/
smb.conf
4. Test the parameters:

% ìwgethome`/samba/bin/testparm
5. Start iw.samba:

Interwoven, Inc. 100

Chapter 5
Configuring TeamSite Clients
After installing TeamSite and configuring your Web server, you need to configure at
least one TeamSite client. You can use either the graphical user interface or the file
system interface for client access.
Accessing TeamSite Using the Graphical User

Interface
The TeamSite graphical user interfaces can be accessed using a supported Web browser.
Refer to the TeamSite Release Notes for the latest information about supported browsers.
To log in, you must be a TeamSite user. If you have not yet added users to TeamSite or
changed your own user status, you should do so now (see Chapter 5 of the TeamSite
Administration Guide). If you do not add users or change your own user status, you can
log in using the host system’s rootAdministrator user name and password for all user
roles.
1. To access TeamSite from a client computer, open your Web browser and enter either
of the following URLs for the ContentCenter interfaces:
http://server_hostname
http://server_hostname/iw-cc
where server_hostname is the name of your TeamSite server (for example,

teamsite1.example.com). You may want to bookmark this URL for future use. The
TeamSite login screen displays.
2. Enter your user name and password. By default, TeamSite accepts the host system’s
root user name and password for all user roles.
3. Click Login.
Installing Local File Manager

Before you can edit files using TeamSite, you or your end-users must install and
possibly configure Local File Manager (formerly known as the LaunchPad applet) on
each client system that will access TeamSite.

Chapter 5: Configuring TeamSite Clients
Your client system associates different applications with different file types, so that
when you double-click on a file, it knows what application to use to open it. You will
only need to configure Local File Manager preferences for file types if they are different
from your system preferences.
For example, you may have a browser set to open HTML files in your system
preferences, but want to use a text editor to edit HTML files from TeamSite. In that
case, you would need to set preferences for HTML files in Local File Manager.
Complete the following procedure to install and configure Local File Manager.
1. Select a file to edit within TeamSite:
If you are already using an older version of LaunchPad, you are prompted to
upgrade to the new Local File Manager.
If you have not used LaunchPad before (that is, this is a new TeamSite
installation), you are prompted to install Local File Manager.
2. The File Association window displays. Unless you are familiar with DDE settings
for your editing application, it is usually safest to copy all necessary information
from an existing setting by clicking Copy From.
3. The Extensions window displays. Locate an entry that uses the editing application
that you want to use and click the extension within that entry, then click OK.
All the necessary information is copied into the File Type window.
4. Edit the Description of type and the Associated extension boxes as necessary (the
file extension must begin with a period, for example, .html, .jpg, .gif).
NOTE
You can only configure one extension per entry. For example, although you might
want to use the same editor for .htm and .html files, you must create two different
entries.
5. Click OK.
The new file type displays in the File Types window.
6. Click OK.
Viewing Online Documentation

After logging in to any of the TeamSite interfaces, you can access the online user
documentation as follows:
ContentCenter Standard—Click the Help link (top right) or the series of topic links
in the How Do I module. Many of the screens also have links to context-sensitive
help topics.
ContentCenter Professional—Click the Help link (top right).

NOTE
Help links in both ContentCenter UIs are context-sensitive and display only information
related to the current screen. To access other topics, you can use the Contents, Index,
and Search links at the top right of each topic.
Accessing TeamSite Using the File System

Interface
The file system interface enables you to manage your content in TeamSite as if it were
on a mounted drive on the network. The file system interface is used primarily for file
management functions such as moving and copying files, and it can also be used to edit
files. It also allows the use of link checkers and scripts that need to be able to access or
create files. In addition, most TeamSite operations can be performed from a UNIX
command-line interface (see the TeamSite Command-Line Tools manual).
Windows Clients
The first time you access your TeamSite server from a Windows client, you may need to
mount the TeamSite server as a network drive. The following procedure describes how
to access TeamSite with:
A networked computer using Samba or a NFS client
A networked computer with FTP
To access TeamSite from Windows via Samba, use Windows Explorer to locate the
TeamSite server.
1. Click Start > Search > For Files or Folders.
2. Click the Search for other items: Computers option.
3. Type the name of the TeamSite server in the Computer Name field.
4. Click Search Now.
5. Double-click the name of the TeamSite server when it appears in the list.
The server window displays.
6. Double-click the TeamSite mount point directory (usually iwmain) and navigate
through the TeamSite directory structure to find your workarea.
Within your workarea, you can edit, move, or rename TeamSite files as you would
any other files. You can also drag and drop files and directories from your local hard
drive to directories in your workarea.

Creating Shortcuts from Windows Clients
To simplify future access to your workarea or to commonly used directories in your

workarea, create a shortcut to the directory or directories you access frequently and put
it on your desktop.
Troubleshooting Windows Networking

If your Windows clients cannot find the TeamSite server through Windows Networking,
check to see if you have NetBEUI installed. If you do, uninstall it if possible as follows:
1. Select Start > Settings > Control Panels.
2. Double-click the Network control panel icon.
3. Select the Protocols tab.
4. From the list of adapters and their associated protocols, find the local client Ethernet
card adapter. If NetBEUI precedes TCP/IP in the list of bound protocols, you will
need to remove it.
5. To remove NetBEUI, select the NetBEUI protocol in the list, then click Remove.
6. Close the remaining Network dialog windows.
7. Reboot your computer.
After rebooting, the client Ethernet card will use TCP/IP to send and receive network
transmissions. You will now be able to use the Windows Start > Find > Computer
utility to locate the TeamSite server.
You can also use the Advanced tab of the protocol settings to specify TCP/IP as the
default protocol binding for Windows Networking, but this solution is not as reliable
because it might be upset as network cards are changed and protocols are added and
removed.
Configuring PDC
You can configure TeamSite to use the Windows Primary Domain Controller (PDC) for
name and password authentication. This configuration eliminates the need for users to
enter their passwords manually whenever they connect to the TeamSite server.

To use the Windows PDC for authentication, modify your Samba configuration as
follows:
1. In the [global] section iw.smb.conf, modify or add the following:
# Select a Windows PDC for your password server
password server = DNS_name_of_your_PDC
# Use share level security
security = server
# Use password encryption
encrypt passwords = yes
2. Stop and restart Samba:
% /etc/init.d/iw.samba stop
NFS Clients
If you are using an NFS client, follow your program’s setup instructions to mount
/iwserver on the TeamSite server as a networked drive. If you can, you should modify
the client configuration to NFS Version 2 and turn off NFS locking (sharing) on the
client. If you do not turn off locking, operations might freeze for long periods of time.
FTP Clients
If you are using an FTP client, follow your program’s setup instructions to install the
software. Log in to the TeamSite server using your UNIX login and password and
navigate to your workarea, located at:
/iwmnt/default/main/branchpath/WORKAREA/workareaname
Macintosh Clients
NOTE
The following instructions are for Classic MacOS (pre-10.0).
To use the TeamSite file system interface for Macintosh, you need to have an
AppleShare server set up for the server that is running TeamSite as follows:
1. In the Chooser, select AppleShare.
2. Select the name of the TeamSite server. Click OK.
3. If you are asked for your username and password, enter your TeamSite username
and password, and click OK.

4. Select the items you want to use, and click OK.

The TeamSite server is displayed on your desktop.
For additional AppleShare server recommendations, contact Interwoven Client

Services.
UNIX Clients
NOTE
UNIX client information also applies to Mac OS X, although the command syntax is
slightly different.
To access the TeamSite server using UNIX clients, log in to the TeamSite server using
your TeamSite username and password.
If you have UNIX clients that will be accessing the TeamSite file system, you can mount
the TeamSite directory, or configure the client machine to automatically mount the file
system at boot time.
To mount the TeamSite directory, issue the following commands:

% mkdir /iwmnt
% mount -overs=2 servername:/iwserver /iwmnt
where servername is the name of the server on which TeamSite is running.
Alternatively, you can mount a subdirectory of iwserver, for example, a specific branch
or workarea. To mount a workarea, issue the following commands:
% mkdir /iwmnt
% mount -overs=2
servername:/iwserver/default/branchpath/WORKAREA/workareaname /iwmnt
where servername is the name of the server on which TeamSite is running, branchpath
is the path of the branch your workarea is on (for example, main/intranet), and
workareaname is the name of your workarea.
To set up a Solaris client (including the TeamSite server itself) to mount the TeamSite
directory at boot time, edit the /etc/vfstab file to include the following line:
servername:/iwserver - /iwmnt nfs - yes vers=2,bg
To set up an AIX or Linux client (including the TeamSite server itself) to mount the
TeamSite directory at boot time, edit the /etc/filesystems or etc/fstab, respectively.
After configuring client access, transfer your content files into TeamSite as described in
the next chapter.

FormsPublisher Clients
TeamSite FormsPublisher requires the installation of the VisualFormat software on
client systems when VisualFormat is used for formatting text areas. When a user on a
client system opens a data capture form that contains a VisualFormat field, they are
prompted to install VisualFormat by clicking Install. After clicking Install, they need to
respond Yes in the security warning dialog boxes to complete the installation.
VisualFormat is only supported on client systems using a Windows operating system.


Chapter 6
Loading Content Files
The TeamSite installation program automatically creates the main branch. It contains a
staging area and an empty initial edition. Before you start using TeamSite for
production, you must transfer your content files into TeamSite.
Populating TeamSite with your content involves the following general steps. Detailed
procedures for each step are in the sections that follow.
Creating a Content Store
Creating a Subbranch
Creating a Workarea
Populating the Initial Workarea
Submitting Files to the Staging Area
Publishing an Edition
The procedures described in this chapter use the ContentCenter Professional interface.
A table showing the equivalent commands for the WebDesk Pro interface is on
page 139, and an introduction to ContentCenter is on page 118.
Creating a Content Store

The following sections provide an overview of Content Stores and describe how to
create one or more Content Stores on your system.
Content Store Overview

The Content Store, called the backing store in older versions of TeamSite, is a large
directory structure created by the TeamSite installation program that contains TeamSite
files and metadata. By default, the Content Store is located in /local/iw-store.
Up to eight Content Stores are supported for each TeamSite server. These Content
Stores can be located on different file systems, local to the TeamSite server machine.

Chapter 6: Loading Content Files
Dividing your existing Content Store into multiple Content Stores (possibly on different
file systems) enables you to simplify data management, including faster data backup. It
also avoids having your Content Stores grow to unmanageable sizes.
NOTE
You can migrate data to your new stores any way you choose, but the data between the
stores is completely independent and may not be migrated to other stores using
inter-branch copying. Copies remain branch-specific and cannot be used at the Content
Store level.
Content Stores have a corresponding archive in the VPATH. In older versions of

TeamSite, there was only one archive named default with a corresponding Content
Store called iw-store/default. MultiStore functionality allows for multiple Content
Stores with user-assigned names. Each Content Store is similar to the default archive
in that it contains a single root branch called main and is independent of any other store
controlled by the server. All mounted Content Stores are assigned a unique store ID
number and maintain their own set of inodes that are stored persistently inside each
Content Store.
Content Stores which are named using multibyte characters must be created by editing
the iw.cfg file. For detailed information, see “Defining Content Stores in the iw.cfg File”
on page 111.
Supported File Objects
TeamSite Content Stores support the following file objects:

Files
Directories
Symbolic links
Creating Multiple Content Stores

Multiple Content Stores can be created using two different methods depending on where
you want to locate them, and whether you want to use multibyte characters in their
names.
To define Content Stores by editing the iw.cfg file, complete the procedure described in
the next section. To create Content Stores using the iwstoreadm CLT, complete the
procedure described in “Creating Content Stores using a CLT” on page 113.
Editing the iw.cfg file defines Content Stores with entries in the [iwserver] section of
the iw.cfg file. This procedure:
Accepts multibyte characters for the store name (though the path to the store must
use ASCII characters).

Creates the new Content Store in any location.

Allows you to add a descriptive comment to the Content Store. This comment
displays when the active Content Stores are listed from the command line or display
in the TeamSite user interfaces.
Must be activated by using the iwstoreadm CLT with the -a option.
Another alternative is to use the iwstoreadm CLT, which creates and activates new
Content Stores when issued with the -a option. This procedure:
Accepts ASCII characters for store names.
Creates the new Content Store in the default location (typically /local/iw-store).
Does not allow for a descriptive comment to be added to the Content Store.
Defining Content Stores in the iw.cfg File
As previously mentioned, the advantages of defining Content Stores in the iw.cfg file
include the ability to use multibyte characters in store names and to locate the Content
Store in a directory other than /local/iw-store.
User-defined Content Stores that are named using multibyte characters must have a
corresponding entry in the iw.cfg file. While the name of the Content Store can be
defined in multibyte characters, the Content Store location must be defined using ASCII
characters. All Content Store data is stored in UTF-8 encoding.
Complete the following procedure to create Content Stores defined in the iw.cfg file:
1. Ensure that you are logged in as the user root and that root has the Master role
enabled in iw-home/conf/roles/tsusers.xml.
2. Open the iw.cfg file in a text editor. By default, the iw.cfg file is located in
/etc.
3. If you are using multibyte characters for the store name, specify the encoding of
your iw.cfg file by creating the following entry as the first line in the file—it must
be the first line or it will be ignored.
[iwcfg]
encoding=locale_name
where locale_name is one of the following locales:
iso-8859-1 (German)
euc-jp (Japanese)
shift-jis (Japanese)
For example:
[iwcfg]
encoding=shift-jis

NOTE
The locale entry must match the encoding of your text editor. Refer to the TeamSite
Administration Guide for details about text editor encodings.
4. Append the following entry to the [iwserver] section to define additional Content
Stores:
store_directory_store_name=absolute_path_to_backing_store
For example:
store_directory_salesAsia=/local/salesAsia
NOTE
The absolute_path_to_backing_store must be in ASCII while the store_name
and the optional descriptive_comment (described in step 5) can be in high-ASCII
or multibyte characters.
5. Optionally, add a comment to the [iwserver] section below the Content Store you
just defined:
store_comment_store_name=descriptive_comment
For example:
store_comment_salesAsia=Store for Demo
The completed entry, should look like this:

[iwserver]
existing iwserver entries
store_directory_salesAsia=/local/salesAsia
store_comment_salesAsia=Store for Demo
6. Save and close the iw.cfg file.
7. Run the iwreset CLT to have the TeamSite server read the changes to the iw.cfg
file.
8. Run the iwstoreadm CLT with the -a option to create the newly defined Content
Store:
% iwstoreadm -a salesAsia
The iwstoreadm CLT checks the iw.cfg file to see if a store_directory or

store_comment entry exists, when it finds these entries, their definitions are used to
create the Content Store.
The system then activates and mounts the new Content Store.

9. Run the iwstoreadm CLT with the -l option to list all active Content Stores:
% iwstoreadm -l
The system displays the following:

Name Store Directory ID Comment
---- --------------- -- -------
default local/iw-store/default 0x64
salesAsia /local/salesAsia 0x65 Store for Demo
NOTES
You can repeat the procedure to create any number of Content Stores, but you can
only have eight active at one time.
When using multiple Content Stores, you cannot relocate Content Stores (iw-store)
by editing the /etc/defaultiwhome file.
You can edit the store_directory_storename entries to move Content Stores
defined in iw.cfg.
Creating Content Stores using a CLT
The following procedure describes the creation of Content Stores from the command
line using iwstoreadm. It also describes viewing the newly created Content Stores in the
command window.
1. Ensure that you are logged in as the user root and that root has the Master role
enabled in iw-home/conf/roles/tsusers.xml.
2. Issue the iwstoreadm -a store_name command to create a new store. For example:
% iwstoreadm -a store1
store1 is created in /local/iw-store, mounted, and activated.

3. Type the following command to list the active Content Stores:
% iwstoreadm -l
The following listing displays:

Name Store Directory ID Comment
---- --------------- -- -------
default /local/iw-store/default 0x64
store1 /local/iw-store/store1 0x65

Viewing Content Stores

To view a Content Store in ContentCenter Professional, highlight the Content Store:
Figure 45 Content Store screen
Click Properties to view the properties of the store:
Figure 46 Content Store Properties screen
All Content Stores (including the system-generated default) contain a Main branch that
contains a staging area, edition, and workarea:

Figure 47 Content Store Main branch
Creating a Subbranch
Interwoven recommends that all development take place on subbranches. The main
branch is not usually used for development for several reasons. First, it requires a user
with Master privileges to administer. In addition, if you are using TeamSite to develop
multiple Web sites, development of one Web site on the main branch and other Web
sites on subbranches may create a false hierarchy of branches—the subbranch does not
necessarily have any relationship to the parent branch.
To create a subbranch using ContentCenter Professional:

1. Log in to TeamSite as a user having the Master role on the branch in which the
subbranch will be created.
2. From the Branch view where you want to create the new branch, click the New
Branch link.
Because there is only one edition on the parent branch (the empty INITIAL edition),
this subbranch is based on that edition.
3. Complete the form that displays in the right pane:
a. Enter the name of the branch in the Name field. Do not use spaces or the
following characters in the branch name:
\ / : * ? " < > |
Do not name a branch WORKAREA, STAGING, or EDITION.

b. Optionally, add comments in the Description box (comments cannot be
changed).

c. If you want to assign the branch to someone else, change your username (which
displays by default in the Owner field) to the owner’s name.
d. If you want this branch to have multiple Administrators, select Add Group in
the Sharing field and type the name of the group who will be able to administer
this branch in the Group box.
The Administrator(s) of this branch can create workareas and subbranches. For
more information on Administrator privileges, see Chapter 5 in the TeamSite
Administration Guide.
e. Select the type of locking to be used on this branch.
f. In the Based On field, enter the name of the edition to be used as a starting
point. The edition must be from the parent branch.
g. Click OK.
Your newly created branch will contain no workareas, one staging area, and one empty
edition called INITIAL.
You can also use the iwmkbr command-line tool to create a new branch (see the TeamSite
Command-Line Tools manual for details).
Creating a Workarea
To create a workarea using ContentCenter Professional:
1. Click the name of the subbranch you just created to navigate into the branch.
2. From the Branch view where you want to create the new workarea, click the New
Workarea link.
Because there is only an empty edition on this branch, TeamSite creates an empty
workarea.
3. Complete the form that displays in the right pane:
a. Type the name you want to give the workarea in the Name field.
Avoid using spaces and punctuation characters in workarea names. Workarea
names should consist only of alphanumeric characters, hyphens, and
underscores.
b. Add any comments in the Description box.
c. Type the username of the workarea’s owner in the Owner box.
d. If you want a group to be able to share this workarea, select Group in the
Sharing field and type the name of the group in the Group box. If you want this
workarea to be private, so that only the owner can modify files in it, leave the
default group (None) selected.
e. Type or browse to the edition to use as the basis for the workarea.
f. Click OK.

You can also use the iwmkwa command-line tool (see the TeamSite Command-Line Tools
manual for details).
Populating the Initial Workarea

To populate an initial workarea:
1. From the UNIX file system (using telnet, NFS, or Samba), log in as root.
2. Copy your content files into the new workarea (default location):
/iwmnt/default/main/branchname/WORKAREA/workareaname
where branchname is the name of the newly created subbranch and workareaname is
the name of the newly created workarea on the subbranch.
When copying files, use tar to maintain file permissions and timestamps (that is,
make a tar file of your content, copy the file into the workarea, then untar the file).
3. Navigate to the workarea and ensure the file permissions are correct before
submitting the files to the staging area; if not, set permissions on the content files.
Use chown and chgrp to limit access to files by changing the owners and groups for
these files. For more information on the chown and chgrp commands, consult a
UNIX reference manual.
Because TeamSite considers a change in permissions to be a change in the file,
TeamSite stores a new version of the file when you change its permissions (new
versions are created at the time files are submitted to the staging area). If you wait to
set permissions until after your files have been imported into a workarea and
submitted to the staging area, you can create a large number of extra versions and
unnecessarily clutter each file’s version history. To avoid creating unnecessary
versions, set permissions immediately after you populate the workarea (but before
you submit the files). You can create a submit filter to automate this process (see the
TeamSite Administration Guide) if you do not want to set permissions manually.
Submitting Files to the Staging Area

After populating your workarea with your content files, you can submit it to the staging
area. After your content files are in the staging area, you can publish an edition, which
will be the basis of all future workareas.
To submit the contents of your workarea to the staging area using ContentCenter
Professional:
1. Click the Workarea name to show the files and directories in the workarea.
2. Depending on how long the list of files and directories is, you might have to click
the All link at the bottom of the screen to ensure that all files and directories are
displayed. If you want to select all displayed files and directories, check the box
next to Name in the column headings.

3. Click Submit in the tool bar. The Submit window displays.

4. Enter the appropriate information and comments in the fields. Required fields have
an asterisk (*) after the field name. You can use two comments fields:
Submit Comments—These comments correspond to the entire Submit
operation.
Individual Comments—These comments correspond to the specified file and
may be duplicated.
5. Click Submit or Start.
You can also use the iwsubmit command-line tool to submit files to the staging area (see
the TeamSite Command-Line Tools manual for details).
Publishing an Edition
Publishing an edition creates a snapshot of the staging area at the time of publication.
These editions can be used as checkpoints. As part of your initial installation process,
you should create an edition to record the state of your content at the time that you
installed TeamSite. You can use this edition as the basis for the other workareas you
create on this branch.
To create a new edition from the contents of the staging area using ContentCenter
Professional:
1. From the Branch view, click the New Editions link.
2. Complete the form that displays in the right pane.
a. Enter the name of the edition.
b. Enter any comments you have in the Description field.
c. Click OK.
The contents of the staging area are published as an edition.
You can also use the iwpublish command-line tool to publish an edition (see the
TeamSite Command-Line Tools manual for details).
The ContentCenter Interfaces

This section introduces the ContentCenter Standard and ContentCenter Professional
interfaces, and describes the various modules, the information displayed in them, and if
they are configurable (by modifying TeamSite configuration files) or customizable (by
using the ContentServices User Interface ToolKit).

Displaying Workareas
Some modules in the ContentCenter interfaces display a list of workareas. This list of
workareas includes:
Workareas owned by the current user.
Shared workareas of which the current user is part of the sharing group.
The ContentCenter Standard modules that display this list include:

My Workareas
My Favorites
My Forms
Work in Progress
This list is also displayed in the My Workareas view in ContentCenter Professional.
Displaying Workarea Names

The names displayed for workareas in ContentCenter Standard are configurable (in case
your workarea naming convention is not intuitive to end-users). The workarea display
name can be configured to be one the following:
workarea name
branch name: workarea name (default)
branch name
workarea description
This applies to anywhere the workarea name displays, including:

My Workareas
My Favorites
New Forms
Work in Progress
File chooser (in the folder drop-down menu)
Task details
Directory listing
For example, the following graphic shows the branch name: workarea name format
used in the New Forms module of ContentCenter Standard (note that it is used in the
drop-down menu and in the listing in the background):

Figure 48 ContentCenter Standard New Forms module
Refer to the TeamSite User Interface Customization Guide for information about
changing the default configuration.
Clicking on Workarea Names

Clicking on the workarea name in the ContentCenter Standard My Workareas module
(or in a Task Detail screen) can be configured to display either the directory Web page
and VisualPreview or the directory listing page. If you want to configure the link to
display the index page and VisualPreview, consider the following two issues:
Your content Web server (for example, Apache) must be configured to redirect
requests for directories to a file (typically an index.html page). For detailed
information about this setting, refer to “Web Server Plug-ins and VisualPreview” on
page 93. Failure to configure this correctly can cause a Web server error, or your
Web server displaying a Web server-generated directory listing (not a TeamSite
directory listing) as follows:
Figure 49 Non-TeamSite browser directory listing
When your content Web server forwards directory requests to files, iwproxy will
need assistance to follow this forwarding (as described in “Web Server Plug-ins and
VisualPreview” on page 93). Failure to do this will result in the correct page being

displayed, but with VisualPreview acting like it is pointing at a directory (as shown
in the graphic). In ContentCenter Standard, VisualPreview displays a warning that it
could not follow the browser forward.
NOTE
Instead of reconfiguring iwproxy, you can redefine the underlying links that invoke
VisualPreview as described in the TeamSite User Interface Customization Guide.
Displaying Forms in the New Forms Module

Each workarea that displays in the New Forms module is populated with the forms
specified in templating.cfg. This file is located by default in iw-home/local/config.
Figure 50 ContentCenter Standard New Forms module
The category name=“intranet” and the

template name=“deptInfo” result in this
form being displayed in ContentCenter
In pre-6.0 versions of TeamSite, all sample templates were enabled for all branches and
a check was performed to ensure the form existed in the branch. Starting with TeamSite
6.0, you must modify your templating.cfg file to specify which templates are
available on each branch. Failure to do this will result in templates that are not available
for a workarea being displayed in the New Forms module. For detailed information
about configuring branch-specific forms, refer to the TeamSite Administration Guide.

Displaying Files in the Work in Progress Module

The following table shows whether a file displays in the Work In Progress module of
ContentCenter Standard for nine different file states. Whether a file displays in the Work
In Progress module is the same for all out-of-the-box TeamSite user roles.
Table 10 File status and display in ContentCenter Standard

Displayed in Work In Progress
File State
Module?
Modified by me, unlocked Yes
Modified by me, locked by me Yes
Modified by me, locked by someone else No
Modified by someone else, unlocked No
Modified by someone else, locked by me No
Modified by someone else, locked by someone else No
Unmodified, unlocked No
Unmodified, locked by me Yes
Unmodified, locked by someone else No
The files listed in the Work In Progress module look similar to the following graphic:
Figure 51 Files in ContentCenter Standard Work In Progress module
For detailed information about adding specific files to the Work In Progress module,
refer to the online help.
Displaying My Tasks
The ContentCenter Tasks module displays the following types of tasks:
My Tasks—Active user tasks owned by the current user.
Group Tasks—Active group tasks assigned to a group that the current user belongs
to, and which no other user has yet taken ownership of.

Figure 52 ContentCenter Standard Tasks module
For detailed information about assigning and completing tasks, refer to the online help.
Configuring Local File Manager

Local File Manager configuration is not directly exposed in ContentCenter Standard.
The rules for determining which editing program the Local File Manager uses are the
same as ContentCenter Professional and WebDesk Pro. If the user attempts to edit a file
in ContentCenter Standard that the Local File Manager cannot associate with an editing
program, the user is prompted to configure an editor. To prevent this dialog from being
displayed to your users, configure Local File Manager as described in “Installing Local
File Manager” on page 101.
Additionally, the My Local Files Setting dialog is available from the following URL:
http://server_name/iw-cc/localfilemgrsetup. To enable ContentCenter Standard
users to configure their own editing applications, you could:
Provide them with this URL.
Create a custom online help “How Do I” entry that references the URL. Creating
custom help entries is described in the TeamSite User Interface Customization Guide.
Workflow CGI Tasks and ContentCenter

Workflow CGI tasks can appear in two places in ContentCenter Standard:
Task details—If the workflow task is a CGI task, transitioning this task invokes its
CGI.
Wizards—If the user transitions a task, and the next task in the workflow is a CGI
task (as opposed to selecting either the New Job or Keep Work in Progress
options), its CGI task is immediately invoked.
When invoking workflow CGI tasks, ContentCenter Standard, by default, displays the
CGI interface in the same browser window (that is, it does not launch a new browser
window). In previous TeamSite releases, CGI tasks were opened in a new window,
which was closed at the end of the user-interaction with the CGI. You can edit your
CGIs to display in a new window when using ContentCenter Standard.

A CGI can determine which ContentCenter interface in was invoked from by reading
the window.opener Javascript object:
If the value is not null, it has been opened in ContentCenter Professional.
If the value is null, it has been opened in ContentCenter Standard.
Edit the CGI so that when it is invoked in ContentCenter Professional, it closes the
window and when it is invoked from ContentCenter Standard, it forwards to the
workflow feedback URL command.
For more information about the workflow feedback URL, refer to the TeamSite User
Interface Customization Guide.
Displaying Task Variables

By default, the ContentCenter interfaces display the Priority and Due Date task
variables:
Figure 53 ContentCenter Standard Task Details screen
Link to VisualPreview
Editing
Variables that cannot be
customized or changed
Default variables that

can be customized
NOTES
In both ContentCenter interfaces, if the task does not contain a value for the
specified variable, a read-only job variable value displays (if it exists).
In ContentCenter Standard (as shown), task variables are read-only.
In ContentCenter Professional, task variables can be edited.
You can customize which task variables are displayed in the Task Details screen using
the User Interface ToolKit (UITK). Refer to the TeamSite User Interface Customization
Guide for information about customizing task variables.

The Get Latest Operation in ContentCenter Standard

In ContentCenter Standard, users cannot explicitly perform a Get Latest operation (as
they can in ContentCenter Professional). In ContentCenter Standard, the Get Latest
operation is performed on a file whenever a user attempts to edit it. For new files that
are submitted from other workareas, the TeamSite administrator must either:
Perform a Get Latest using ContentCenter Professional.
Create and run an automated script at a regular interval to update all shared
workareas.
Resolving Task Conflicts

The TeamSite Content Server’s workflow engine does not allow a TeamSite Author to
own a submit task (unless they have also been configured as a TeamSite Editor,
Administrator, or Master). When an Author submits a file, the submit task is owned by
the owner of the workarea where the file is submitted. If a conflict occurs during a
submission, the submit task displays in that other user’s task list with an indication that
a conflict exists.
ContentCenter Standard users having the Editor, Administrator, or Master role(s) may
have a conflicting submit task in their Task list. Because the ContentCenter Standard
interface does not enable users to resolve conflicts, these users must use ContentCenter
Professional to resolve any conflicts.
Configuring Submit Workflow

All ContentCenter Standard wizards that contain a submit step read the list of available
workflows configured in the available_templates.cfg file for the user’s current
branch. This behavior is the same for submissions from ContentCenter Professional. If
only one workflow template is configured, the “select workflow” step is skipped and the
referenced workflow is initiated.
NOTE
There is no Submit Direct functionality in ContentCenter. TeamSite Editors,
Administrators, and Masters are presented with a submit workflow that has no approval
step.
After a user selects a workflow, the workflow instantiation screen displays inside a
wizard. The workflow instantiation screen displayed in ContentCenter Standard and
ContentCenter Professional are similar, but not identical.

Eliminating Tagging Steps in Wizards

Refer to the TeamSite User Interface Customization Guide for information about
modifying wizards.

Chapter 7
The iwui User
The TeamSite installation program creates a UI daemon user called iwui to restrict
access to the session cookie encryption password stored in
iw-home/private/etc/passphrase. The UI daemons (iwwebd and iwservletd) and
iwproxy must be able to read the password to issue and validate session cookies.
Currently, iwwebd and iwservletd run as iwui, and iwproxy runs as root. The iwui
user has no privileges except for being able to read the passphrase file:
-r------- 1 iwui adm 94 Aug 1 16:20 /usr/iw-home/private/etc/passphrase
The iwui user also has the following characteristics:

Member of the system group nobody—This ensures there are as few privileges
associated with this user as possible. Membership in other groups which own no
files on the system would be equivalent.
Owns the iwwebd and iwservletd processes—For more information about iwwebd
and iwservletd, see the TeamSite Administration Guide.
Is hardcoded as iwui in the iwsessionkeygen CLT—Therefore you should not
change the name of this user.
Impersonation user for Tomcat—Provides the ability for the user logged into the
browser interface to execute a program on the TeamSite server and have that
program behave as if it were run by the logged in user and not iwui, nobody, or
root.
By default, is assigned the next available user ID (UID) by the installation program:
Creating Interwoven TeamSite UI Daemons User (iwui)...
Please choose a UID for the new user, or press <Enter> to accept the
next available UID.
Home directory is iw-home.

If you do not want this system user to have a UID mixed in with your regular user
accounts, manually assign a UID during the installation (system accounts typically
have a lower UID).

Chapter 7: The iwui User

Appendix A
Configuring Application
Servers
This appendix describes how to configure the IBM WebSphere and BEA WebLogic
application servers to deploy Web applications such as TeamSite ContentCenter and
Event Subsystem. Procedures are divided into sections depending on whether the
procedure pertains to a specific Web application or to the application server in general.
Overview
Many TeamSite features rely on the proper deployment of Web applications. For
example, TeamSite’s ContentCenter user interfaces are defined by the content_center
Web application residing in iw-home/httpd/webapps. Likewise, Interwoven Search and
TeamSite ReportCenter may require the deployment of the eventsubsystem Web
application, which also resides in iw-home/httpd/webapps.
By default, TeamSite uses the Apache Tomcat Web application server to serve up
content_center, eventsubsystem, and all other Web applications. Tomcat is installed
automatically when TeamSite is installed.
To use WebSphere or WebLogic instead of Tomcat as the application server to deploy

the TeamSite ContentCenter or Event Subsystem Web applications, you must perform
the steps described in this appendix after a TeamSite installation has executed
successfully. It is not possible to install WebSphere or WebLogic instead of Tomcat
during a TeamSite installation. Instead, you must let the TeamSite (and Tomcat)
installation complete, and then reconfigure TeamSite with WebSphere or WebLogic as
described in the following sections.
NOTE
This appendix assumes that the WebSphere or WebLogic application server has already
been purchased from the relevant vendor and installed on your system. This appendix
discusses only how to configure these application servers to deploy the TeamSite
ContentCenter and Event Subsystem Web applications.

Appendix A: Configuring Application Servers
Release Compatibility
TeamSite 6.7 is compatible with the following application servers (in addition to
Apache Tomcat):
IBM WebSphere 6.1
BEA WebLogic 9.2
NOTE
The application server must reside on the same system that hosts the TeamSite server.
Configuration Procedures: Specific Web Apps

The following sections describe how to configure WebSphere and WebLogic to deploy
the content_center and eventsubsystem Web applications.
ContentCenter
Perform the following steps to deploy the content_center Web application through
WebSphere or WebLogic. Unless otherwise noted, each step applies to both WebSphere
and WebLogic.
1. Ensure that the TeamSite installation was successful by accessing it through one of
the ContentCenter interfaces. Enter the following URL in a browser. If the TeamSite
installation was successful, the default ContentCenter login page appears in the
browser.
http://hostname/iw-cc
2. On the system hosting the TeamSite server, navigate to the following directory:
iw-home/httpd/webapps/content_center
If you are configuring WebSphere, go to step 4.

If you are configuring WebLogic, go to step 3.
3. For WebLogic only: Force precompilation of JSPs by executing the following steps.
a. Create a new file called weblogic.xml in the content_center/WEB-INF
directory.

b. Add the following lines to weblogic.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app
PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-
jar.dtd">
<weblogic-web-app>
<jsp-descriptor>
<jsp-param>
<param-name>precompile</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
</weblogic-web-app>
4. Perform the following two cp commands to replace the current web.xml file in
content_center/WEB-INF directory with web_no_jsp.xml, retaining the web.xml
file name. Enter each cp command as a single line:
cp iw-home/httpd/webapps/content_center/WEB-INF/web.xml
iw-home/httpd/webapps/content_center/WEB-INF/web.xml.save
cp iw-home/httpd/webapps/content_center/WEB-INF/web_no_jsp.xml
iw-home/httpd/webapps/content_center/WEB-INF/web.xml
5. Shut down the Tomcat server that is installed and started as part of the default
TeamSite installation from the TeamSite location:
As root, determine the process ID of the Tomcat server and kill that process:
ps -aef | grep servletd
kill process_id
6. Copy the relevant Web application to the deployment directory of the application
server of choice as follows. Depending on whether WebSphere or WebLogic is
used, there are existing administration tools that deploy applications. Refer to the
documentation for each application server for details.
WebLogic:
a. Copy the content_center directory from the iw-home/httpd/webapps
directory to the deployment directory of the application server, keeping the
original content_center directory in iw-home/httpd/webapps.
b. In the deployment directory of the application server, rename the copied
content_center directory iw-cc.
c. Delete the jspc directory from iw-cc/WEB-INF/.

WebSphere:
a. Delete the jspc directory from
iw-home/httpd/webapps/content_center/WEB-INF/.
b. Execute the following command to create an iw-cc.war Web application in the

parent directory. This command assumes that you are currently in
iw-home/httpd/webapps/content_center, and that the parent directory is
iw-home/httpd/webapps.
jar cf ../iw-cc.war .

c. Copy the iw-cc.war Web application from the iw-home/httpd/webapps

directory to the deployment directory of the application server.
7. Modify the startup script of the application server.
WebLogic:
a. Based on your startup script, add the options shown below in bold font (starting
with -Djava.library.path and ending with -Dlog100.iwlogs) to the startup
script for starting the application server:
%JAVA_HOME%/bin/java %JAVA_VM% %MEM_ARGS%
%JAVA_OPTIONS%
-Djava.library.path=iw-home/cssdk:iw-home/lib:
bea_home/weblogic92/server/bin
-Diw_utild_client_cfg.path=iw-home/servletd/conf/iwutild_client.cf
g
-Dcssdk.cfg.path=iw-home/cssdk/cssdk.cfg
-Diw.client.config.path=iw-home/servletd/conf
-Dcssdk.ssl.key.location=iw-home/servletd/conf/ssl_cert
-Diw_ssl_cert.dir=iw-home/servletd/conf/ssl_cert
-Dlog100.iwlogs=iw-home/local/logs
-Dweblogic.Name=%SERVER_NAME%
-Dweblogic.ProductionModeEnabled=%WLS_PRODUCTION_MODE%
-Djava.security.policy="%WL_HOME%/server/lib/weblogic.policy"
%SERVER_CLASS%
b. Add the following to the CLASSPATH environment variable:
iw-home/tools/java/jre/lib/endorsed/xercesImpl.jar:
iw-home/tools/java/jre/lib/endorsed/xalan.jar:
iw-home/servletd/common/lib/commons-el.jar:
WebSphere:
You might need to navigate through the administration console as follows to make
the changes described below:
Servers > Application Servers > server1
Java and Process management > Process Definition > Java Virtual Machine
a. Using the administration console, update the Generic JVM Arguments field of
the server to include:
g

b. Using the administration console, update the Classpath field of the server to
include:
iw-home/tools/java/jre/lib/endorsed/xercesImpl.jar
iw-home/tools/java/jre/lib/endorsed/xalan.jar
iw-home/servletd/common/lib/commons-el.jar
c. Save the master configuration file.

8. Before running the script to start the server, make sure that the following paths are
added to the library path for the relevant application server:
iw-home/bin:iw-home/lib:iw-home/cssdk:iw-home/servletd/common/lib:iw-h
ome/servletd/common/endorsed:iw-home/servletd/bin:iw-home/httpd/webapp
s/content_center/WEB-INF/lib
9. Change the port of the application server so that it is started on port 8080:
WebLogic: Based on your configuration, you might need to change config.xml so
that ListenPort is set to 8080. Or, as an alternative, change the servlet_port entry
in the [teamsite_servlet_ui] section of iw.cfg so that it matches the ListenPort
setting of the application server.
WebSphere: Based on your configuration, you might need to change the following
files in the relevant locations so that the application server is started on port 8080:
cell location/config/cells/cellname/nodes/nodename/serverindex.xml
cell location/config/cells/cellname/virtualhosts.xml
Or, as an alternative, change the servlet_port entry in the [teamsite_servlet_ui]
section of iw.cfg so that it matches the ListenPort setting of the application server.
10. Start the application server and test it by accessing the ContentCenter interface
through a browser:
http://hostname/iw-cc
The ContentCenter login page should appear in the browser.

When using Websphere, if the application does not start it might be necessary to
have the following lines to the file java-ibm/jre/lib/security/java.security:
security.provider.1=com.ibm.jsse2.IBMJSSEPProvider2
security.provider.2=com.ibm.jsse.IBMJSSEPProvider
security.provider.3=com.ibm.cypto.provider.IBMJCE
Depending on your system configuration, this step might be necessary because the
IBM JSSE implementation does not support TrustManager, which implements rules
for certificate chain path validation starting in Java v1.4.2. The IBMJSSEProvider2
implementation provides the necessary TrustManager support. For more
information, see:
http://www-128.ibm.com/developerworks/java/jdk/security/142/secguides/
securityguide.win64.html.

Event Subsystem
Perform the following steps to deploy the eventsubsystem Web application through
WebSphere or WebLogic. Unless otherwise noted, each step applies to both WebSphere
and WebLogic.
1. On the system hosting the TeamSite server, navigate to the following directory:
iw-home/httpd/webapps/eventsubsystem
2. Shut down the Tomcat server from the TeamSite location:

As root, determine the process ID of the Tomcat server and kill that process:
ps -aef | grep servletd
kill process_id
3. Copy the relevant Web application to the deployment directory of the application
server of choice as follows. Depending on whether WebSphere or WebLogic is
used, there are existing administration tools that deploy applications. Refer to the
documentation for each application server for details.
WebLogic:
Copy the eventsubsystem directory from the iw-home/httpd/webapps directory to
the deployment directory of the application server.
WebSphere:
a. Execute the following command to create an eventsubsystem-as.war Web
application in the parent directory. This command assumes that you are
currently in iw-home/httpd/webapps/eventsubsystem, and that the parent
directory is iw-home/httpd/webapps.
jar cf ../eventsubsystem-as.war .
b. Copy the eventsubsystem-as.war Web application from the
iw-home/httpd/webapps directory to the deployment directory of the
application server.
4. Modify the startup script of the application server.
WebLogic:
a. Based on your startup script, add the options shown below in bold font (starting
with -Djava.library.path and ending with -Dlog100.iwlogs) to the startup:
%JAVA_HOME%/bin/java %JAVA_VM% %MEM_ARGS%
%JAVA_OPTIONS% -Djava.library.path=iw-home/cssdk:iw-home/lib:
bea_home/weblogic81/server/bin
g
-Diw.client.config.path=iw-home/servletd/conf
-Dweblogic.Name=%SERVER_NAME%

-Dweblogic.ProductionModeEnabled=%WLS_PRODUCTION_MODE%
-Djava.security.policy="%WL_HOME%/server/lib/weblogic.policy"
%SERVER_CLASS%
b. Add the following to the CLASSPATH environment variable:

iw-home/tools/java/jre/lib/endorsed/xercesImpl.jar:
iw-home/tools/java/jre/lib/endorsed/xalan.jar:
iw-home/httpd/webapps/content_center/WEB-INF/lib/jasper-runtime.ja
r:
iw-home/httpd/webapps/content_center/WEB-INF/lib/common100.jar:
iw-home/httpd/webapps/content_center/WEB-INF/lib/log100.jar:
iw-home/httpd/webapps/content_center/WEB-INF/lib/oscache-2.2.jar:
iw-home/httpd/webapps/content_center/WEB-INF/lib/commons-logging-a
pi.jar:
iw-home/httpd/webapps/content_center/WEB-INF/lib/log4j.jar:
iw-home/httpd/webapps/content_center/WEB-INF/lib/log4j-1.2.13.jar:
iw-home/httpd/webapps/content_center/WEB-INF/lib/commons-collection
s-2.1.1.jar:
iw-home/cssdk/cssdkiface.jar:
iw-home/cssdk/cssdkjni.jar:
WebSphere:
You might need to navigate through the administration console as follows to make
the changes described below:
Servers > Application Servers > server1
Additional Properties > Process Definition
Additional Properties > Java Virtual Machine
a. Using the administration console, update the Generic JVM Arguments field of
the server to include:
b. Using the administration console, update the Classpath field of the server to
include:
iw-home/tools/java/jre/lib/endorsed/xalan.jar
iw-home/tools/java/jre/lib/endorsed/xercesImpl.jar
iw-home/httpd/webapps/content_center/WEB-INF/lib/serverutils100.ja
r
iw-home/httpd/webapps/content_center/WEB-INF/lib/commons-collectio
ns-2.1.1.jar
iw-home/httpd/webapps/content_center/WEB-INF/lib/log4j.jar
iw-home/httpd/webapps/content_center/WEB-INF/lib/log4j-1.2.13.jar
iw-home/httpd/webapps/content_center/WEB-INF/lib/dom4j.jar
iw-home/cssdk/cssdkiface.jar
iw-home/cssdk/cssdkjni.jar:.
c. Save the master configuration file.

5. Before running the script to start the server, make sure that the following paths are
added to the library path for the relevant application server:
iw-home/cssdk/:iw-home/lib
6. Change the port of the application server so that it is started on port 8080:
WebLogic: Based on your configuration, you might need to change config.xml so
that ListenPort is set to 8080. Or, as an alternative, change the servlet_port entry
in the [teamsite_servlet_ui] section of iw.cfg so that it matches the ListenPort
setting of the application server.
WebSphere: Based on your configuration, you might need to change the following
files in the relevant locations so that the application server is started on port 8080:
cell location/config/cells/host/nodes/host/servers/servername/
server.xml
cell location/config/cells/host/virtualhosts.xml
Or, as an alternative, change the servlet_port entry in the [teamsite_servlet_ui]

section of iw.cfg so that it matches the ListenPort setting of the application server.
7. For WebLogic only: After deploying the eventsubsystem Web application, change
the default setting of the single-threaded pool size from 5 to 1 by putting the
following entry in the weblogic.xml file:
<container-descriptor>
<single-threaded-servlet-pool-size>1</single-threaded-servlet-pool-
size>
</container-descriptor>
8. Start the application server.
Configuration Procedures: Overall App Server

This section describes configuration procedures that affect all Web applications. You
must perform these procedures to ensure that all Web applications deploy through
WebSphere and WebLogic. Unless otherwise noted, each procedure applies to both
WebSphere and WebLogic.
Disabling Apache Auto-Startup

If you follow the instructions for restarting the TeamSite server in the TeamSite
Administration Guide (typically by issuing iwreset -a), the system may attempt to start
Apache instead of WebSphere or WebLogic. To avoid this problem, modify the
iwuiboot shell script that is used to start several UI services (iw-webd, iw-proxy,
iwservletd). To modify the file:
1. Make a backup copy of iw-home/private/bin/iwuiboot.

2. Open iw-home/private/bin/iwuiboot with a text editor.

3. Locate the line that reads echo "Interwoven Servlet Engine starting ..." (at
or near line 169).
4. Delete the line shown in step 3 and the subsequent lines up to, but not including, the
line that reads echo "$MYNAME: ---------- STARTED: `date`" 1>>$IWLOGFILE
2>&1). Approximately 18 lines will be deleted.
5. Save the file.
NOTE
This script is an internal script so changes may be overwritten by an upgrade or service
pack.
Edit ibm-web-ext.xmi (WebSphere only)

Add the following line to the file ibm-web-ext.xmi:
<jspAttributes xmi:id="JSPAttribute_113" name="jdkSourceLevel"
value="15"/>
The ibm-web-ext.xmi file resides in the following directory:

WAS-HOME/profiles/AppSrv01/config/cells/cellname/applications/appname/dep
loyments/appname.war/WEB-INF
A typical example of this path name on a TeamSite system is:

/opt/IBM/WebSphere/AppServer/profiles/SP1/config/cells/pulsarNode02Cell/a
pplications/iw-cc.ear/deployments/iw-cc/iw-cc.war/WEB-INF


Appendix B
WebDesk Pro Transition

Reference
The following table contains the menu items from WebDesk Pro and one or more
corresponding procedures in ContentCenter Professional. It is intended for TeamSite
Administrators (not to be confused with users configured with the Administrator role
within TeamSite) who are familiar with basic TeamSite administration functionality
from earlier releases. If you are new a TeamSite administrator, you can use this table in
conjunction with the TeamSite Administration Guide and the online help to configure
workareas, and import and manage files.
NOTE
There may be additional ways to accomplish the same task that are not shown in this
table.
Table 11 WebDesk Pro and ContentCenter Professional commands

WebDesk Pro Menu Item Procedure in ContentCenter Professional
Workarea view Content tab.
ToDo view Workflow tab.
Workarea File Menu
New File Content tab. File > New File.
VisualPreview New File.
New Directory Content tab. File > New Folder, or:
New Folder link in the Workarea view.
New Workarea Content tab. New Workarea link in Workareas view.
New Branch Content tab. New Branch link in Branch view.
New Data Record Content tab. File > New Form Entry.
New Job Workflow tab. Click New Job on right side of view title
bar, or:
Content tab. Actions > New Job.
Import Files Content tab. File > Import.
Generate Page Content tab. Actions > Generate Page.
Regenerate Page Content tab. Actions > Regenerate Page.

Appendix B: WebDesk Pro Transition Reference
Table 11 WebDesk Pro and ContentCenter Professional commands (Continued)

Rename Content tab. File > Rename.
VisualPreview More > Rename.
Move Content tab. File > Move.
VisualPreview More > Move.
Copy Content tab. Edit > Copy.
VisualPreview More > Copy.
Delete Content tab. File > Delete.
VisualPreview More > Delete.
Delete Data Record Content tab. File > Delete.
VisualPreview More > Delete.
Compare Any Content tab. Actions > Compare To (compares to any
other location).
Compare button in menu Content tab. Actions > Compare (compares to staging
bar area.
Publish Content tab, Branch view. New Edition link from
Actions area.
File Properties Content tab. File > Properties.
Properties link from Actions area for any selected item.
VisualPreview More > Properties.
Get Latest Content tab. Actions > Get Latest.
Get Latest button.
Submit Content tab. Actions > Submit.
Submit button.
VisualPreview Submit.
Assign Content tab. Actions > Assign.
Copy to Area Content tab. Edit > Copy To.
Logout Logout link in top right corner.
Workarea Edit Menu
Select All Content tab. Edit > Select All.
Check the checkbox in the column heading.
Select All Files Check the Name checkbox in the column heading.
Clear All Content tab. Edit > Clear All.
Clear the checkbox in the column heading.
Lock Content tab. Actions > Lock.
Unlock Content tab. Actions > Unlock.
Public From Properties dialog box, clear the Do Not Submit
checkbox for Private.


Private From Properties dialog box, check the Do Not Submit
checkbox for Private.
View File Content tab. Actions > View Source.
Edit File Content tab. Edit > Edit.
VisualPreview Edit.
Edit link from Actions area.
Edit Data Record Content tab. Edit > Edit.
VisualPreview Edit.
Edit link from Actions area.
Edit With Content tab. Edit > Edit With.
Download Content tab. File > Download.
Upload VisualPreview Upload.
My Local Files view, Upload button.
Set Home Page Use Favorites.
LaunchPad Setup My Local Files view, Settings link.
Workarea View Menu
List Locks Content tab. View > Locked Files and My Locked Files.
List Modified Content tab. View > Modified Files and My Modified
Files.
List Local Files Content tab. View > My Local Files.
Home Page Use Favorites link.
To Do List Workflow tab.
Workarea Content tab.
History Content tab. File > Versions.
VisualPreview More > Versions.
File Properties view, Versions link.
Submit Log Content tab, Branches, Editions, or Workareas view.
Submit Log from Actions area.
Update Log Content tab, Branches, Editions, or Workareas view.
Update Log from Actions area.
Search N/A
Reports N/A
Refresh Browser Refresh button.
File – To Do
New Job Workflow tab. New Job button.
Content tab. Actions > New Job.
View – To Do
Current Tasks Workflow tab, Tasks. In View list, select My Open Tasks.


Unassigned Tasks Workflow tab, Tasks. In View list, select Unassigned
Group Tasks.
My Jobs Workflow tab, Jobs. In View list, select My Jobs.
All Jobs Workflow tab, Jobs. In View list, select All Jobs.
SmartContext Editing Tab VisualPreview toolbar
Edit Edit.
Review More > Review.
Images More > Select Image.
Upload Upload.
New Record New Form.
Tag More > Tag.
Submit Submit.
Source Diff More > Source Differences.
Details More > Properties.
Assign More > Assign.
Visual Diff More > Visual Differences.
Undo Changes More > Undo Changes.
Check Links More > Check Links.
New File N/A
Frameset More > Edit > FrameSet directory.

Appendix C
Migrating Roles and

Permissions
TeamSite 6.7 introduced the concept of configurable roles and delegated administration.
Under this arrangement:
The out-of-the-box Author, Editor, Reviewer, Administrator, and Master roles can
be configured to include or exclude some capabilities.
Users can have different roles on different branches.
You can create entirely new roles with nearly any capability for your site.
See Chapter 5, “Defining Users and Roles,” in the TeamSite Administration Guide for
more information about roles starting with TeamSite release6.7.
To support these new capabilities, TeamSite 6.7 and later releases use a new model to
establish user and group permissions, roles, and group memberships. Before you can use
TeamSite 6.7 or later, you must migrate your existing permissions and roles to the
TeamSite 6.7 model.
Migration Overview
If you are upgrading from a pre-6.7 TeamSite release, migration to the TeamSite 6.7
model falls into two main categories: steps invoked automatically by the TeamSite
installation program starting with release 6.7, and steps that you must perform manually
following a TeamSite 6.7 or later installation. The following sections describe these
categories in more detail. See the subsequent section “Migration Procedure” for details
about performing the migration.
NOTE
Migration cannot be undone after it has been performed. Therefore, if you think that you
might need to revert to a pre-6.7 TeamSite release, you should back up all of your
Content Stores, TeamSite roles files, and TeamSite configuration files and store them in
a location that is not affected by the migration.

Appendix C: Migrating Roles and Permissions
Steps Invoked by the Installation Program

Starting with release 6.7, the TeamSite installation program invokes the iwusermigrate
command-line tool (CLT) during TeamSite installation. This CLT identifies TeamSite
users and their roles as configured in the pre-6.7 release.
If users and roles are defined in the pre-6.7 release by .uid files in the
iw-home/conf/roles directory, that information is read and recorded in
iw-home/conf/roles/tsusers.xml in the 6.7 or later release. If users and roles are
defined in LDAP (rather than in .uid files) in the pre-6.7 release, that information is
read and recorded in iw-home/conf/roles/tsldapuserscache.xml in the 6.7 or later
release. After TeamSite 6.7 or later is installed and started, this file is updated regularly
based on the entries in LDAP. See the to documentation for the iwldapuserscache CLT
in TeamSite Command-Line Tools for more information.
Users having the Master role have the ismaster attribute set to true in tsusers.xml or
tsldapuserscache.xml.
Steps to Invoke Manually

To finish the migration procedure you must run the iwaccessmigrate CLT manually
after TeamSite 6.7 or later is installed. This CLT performs the following tasks:
Reads additional user and role information.
Determines branch and workarea owner IDs and group-for-sharing IDs.
Creates an XML-format manifest report containing:
A list of users migrated to tsusers.xml or tsldapuserscache.xml.
Assignments of permission entries at every branch level based on owner and
group-for-sharing of branches and workareas and the users’ highest login roles.
Descriptions of TeamSite groups that are created for assigning group permission
entries.
Completes the migration to the TeamSite 6.7 model.
NOTE
It is also possible to generate the manifest file as a separate, pre- or post-migration step
without actually completing the migration. This scenario lets you examine the manifest
file before or after the migration to help determine the migration’s implications. You can
also edit the manifest file prior to finishing the migration to customize permissions and
roles before they are implemented. If you edit the manifest file, you can specify that it
be used as input when the final migration step executes. See the iwaccessmigrate
documentation in TeamSite Command-Line Tools for more information.

Migration Procedure
The following steps describe how to migrate pre-6.7 TeamSite permissions and roles to
the TeamSite 6.7 model. Perform these steps after the TeamSite 6.7 or later installation
program finishes and after you have rebooted the system. The steps described here
assume that the portions of the migration invoked automatically by the TeamSite 6.7
installation program have already executed, and that the TeamSite server (iwserver) is
running.
1. Issue the iwstat CLT to verify that the TeamSite 6.7 or later server is running and
to see which Content Stores are active and inactive:
# iwstat
It is possible to perform the migration when some Content Stores are active and
others are inactive, but this is not a recommended or supported practice. Only active
Content Stores can be migrated. Performing a second migration for Content Stores
that were inactive at the time of the original migration and were activated after the
fact is not a supported or documented procedure. If you need to perform the
migration while one or more Content Stores is inactive, it is highly recommended
that you contact an Interwoven representative prior to invoking the
iwaccessmigrate CLT to finish the migration.
2. Ensure that no users or programs attempt read or write operations on the content
store(s) for the rest of this migration procedure. For example, make sure that no
users, workflow jobs, background tasks, or cron jobs are able to access the content
store(s).
3. Run the iw-home/bin/iwaccessmigrate CLT:
To complete the entire migration with no further interim steps, issue the
command with no options. When iwaccessmigrate executes, it generates the
accessresults.xml manifest file in iw-home/local/logs and implements the
migration with no further interaction from you:
# iwaccessmigrate
Alternatively, to generate the accessresults.xml manifest file without

completing the migration, use the -m option:
# iwaccessmigrate -m
After reviewing and optionally modifying accessresults.xml, finish the

migration and implement the changes defined in accessresults.xml by issuing
iwaccessmigrate with the -f option:
# iwaccessmigrate -f iw-home/local/logs/accessresults.xml
4. In some pre-6.7 TeamSite releases, it was possible to customize roles using the UI
Toolkit. Any such custom roles were captured in roles_custom.xml. To migrate
these custom roles to the TeamSite 6.7 model, execute the following command:
# iw-home/install/migrate_customtk.ipl
5. Restart the TeamSite server:

# /etc/init.d/iw.server start


Index
Symbols configuring
CGI programs 90
.shtml files 91
disk space 17
iw-mount alias 88
A MIME types, Apache 92
accessing TeamSite 103 web servers 87
activating backing stores 113 connecting to TeamSite by FTP 17
Apache Content Store
configuring 87 default location 36
configuring MIME types 92 defined 36
location 48
conventions, notation 11
B copying files 117
backing store CPU requirements 14
activating 113 creating
ASCII characters 37 branches 115
comments 112 workareas 116
disk space 17
encoding of names 111
location 25
D
moving 113 database
multibyte characters 111 event subsystem 40, 54, 77
naming 37 default file locations 25
Backup Domain Controller (BDC) 17 disk configuration 17
branches disk space
creating 115 partitions 17
restrictions on names 115
setting locking model 116 E
editions
C initial 116
CGI tasks 123 new 118
configuring in ContentCenter GUIs 123 publishing 118
clients encoding
Microsoft network 103 of backing store names 111
NFS 105 of contents of iw.cfg 111
TeamSite 103 text editors 112
CLTs errata 12
iwreset 112 event subsystem
iwstoreadm 113 database 40, 54, 77
comments
publish 118
submit
individual file 118
keywords 118
submit operation 118

Index
F J
file system interface JavaScript 101
and FTP 103
network connection 17 L
using 17
files license keys
install log 33 troubleshooting 72
iwinstal_log.log 33 loading content 109
log 38 Local File Manager
parsing .shtml 91 about 103
submitting to the staging area 117 installing 103
TeamSite log 38 locations
TeamSite.bin 84 default program files 25
FTP locking model 116
and the file system interface 103 log files 38
clients, using 105
connecting to the TeamSite server 17 M
MIME types, configuring 92
H moving
High Availability backing stores 113
about 129, 139 multibyte characters
HTTPS requests, redirecting 95 in backing store names 111
I N
IBM HTTP Server 87 NetBEUI 104
incremental updates 61 network drive 103
initial edition 116 network file system 17
NFS
inode requirements 17
and the file system interface 17
install log location 33
installing clients 103, 105
FormsPublisher 19 server mount point 88
required access for 28, 33, 44, 61, 65 nobody 127
required information 28 notation conventions 11
search 61, 65
TeamSite 32 P
internationalization parsing .shtml files 91
text editor encoding 111 passwords
iPlanet web server enabling plain-text 104
aliases 95 Windows encrypted 104
configuring 87 pcnfsd
iw.cfg installing 39, 52, 76
activating change to 112 introduced 17
encoding of 111 port 80 75
iw-home port number
about 25 http server 75
iw-mount alias 88 web server 76
iwreset 112 ports
iwservletd 127 HTTP server 48
iwsessionkeygen 127 Interwoven Web Daemon 49
iw-store directory, backing up 74, 83 proxy 38
iwstoreadm 113 servletd 38
iwui user 127 web server 37, 38, 49, 87
iwwebd 127

Index
Primary Domain Controller (PDC) 17 T

program files tasks
location 66 CGI 123
program files, default location 25 ownership 125
proxy port 38 TeamSite
publishing editions accessing
about 118 through the file system 103
adding comments 118 through the GUI 101
first edition 118 troubleshooting 104
through the command line 118 CD-ROM 34, 44, 61, 74
through the TeamSite GUI 118 clients 101, 103
Content Store 36
R FormsPublisher 19
High Availability 129, 139
RAID configurations 17 see also High Availability
redirecting HTTPS requests 95 installation directory 34, 44, 75
redirector module log files 38
for SSIs, installing 91 mounting 103
introduced 91 populating 117
Reporting
Service Pack 1 83
standalone installation 28
requirements uninstalling 83
backing store 17 TeamSite.bin 84
CPU 14 text editor encodings 112
inode 17 troubleshooting, license keys 72
root access
and shutdown operations 33, 44, 61, 74 U
and startup operations 33, 44, 61, 74 uninstalling
gaining 33, 44, 61, 74 TeamSite 83
installing TeamSite 33, 44, 61, 74 TeamSite.bin 84
uninstalling TeamSite 83
S users
Samba iwui 127
connecting to the file system interface 17, 103 nobody 127
installing 39, 52, 76
SCSI controllers and drives 17 V
search VisualPreview
installing 61, 65 for SSIs 91
server-side includes 91 required plug-ins 93
Service Packs, uninstalling 83
servletd port 38
SSIs, enabling 91 W
staging area 116 web daemon 49
submit filtering 117 web servers
submit task, ownership 125 aliases 25
submitting, files to staging 117 configuring 87
Sun ONE web server iPlanet 95
aliases 95 port number 37, 49, 76, 87
supported web servers 87 stopping and starting 94
Sun ONE 95
supported 87
window.opener Javascript object 124
Windows networking 17

Index
workareas
creating 116
naming conventions 116
populating 117
private 116
shared 116
submitting to the staging area 117

Ts 671sp1 Install Unix v01 en

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Ts 671sp1 Install Unix v01 en

Încărcat de

Drepturi de autor:

Formate disponibile

TeamSite ®

Interwoven, ConfirmSite, ControlHub, DataDeploy, DeskSite,FileSite, iManage, LiveSite, MediaBin,

TeamSite Installation Guide

TeamSite Installation Guide 3

Installing Interwoven Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Troubleshooting Windows Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

TeamSite Installation Guide 5

Appendix C: Migrating Roles and Permissions 143

TeamSite Installation Guide 7

TeamSite Installation Guide 9

Figure 44 ContentCenter Standard Content module . . . . . . . . . . . . . . . . . . . . . . . . . .96

Table 1 Notation conventions

TeamSite Installation Guide 11

Table 1 Notation conventions (Continued)

Online Documentation Errata

Server Hardware Requirements

Table 2 Disk space required for TeamSite installation

TeamSite Installation Guide 13

CPUs and Memory

All CPUs should be at least 1.2 GHz.

System Running Just the TeamSite Server

Table 3 CPU and memory requirements: TeamSite server

15 concurrent users 2 CPUs 2 CPUs 1 CPU

TeamSite Installation Guide 15

System Running Just the Interwoven Search Server

Table 4 CPU and memory requirements: Search server

System Running the TeamSite and Interwoven Search Servers

Table 5 CPU and memory requirements: TeamSite and Search servers

15 concurrent users 4 CPUs 2 CPUs 2 CPUs

Connecting Through the File System Interface

TeamSite Installation Guide 17

Installing a Service Pack Release

TeamSite Installation Guide 19

TeamSite and Search Compatibility

Installing the TeamSite Service Pack

2. Save the installation package to any location on your local system.

3. Change user to root.

4. Extract and untar the contents of the package:

5. Navigate into the TeamSiteSP directory.

To install in console mode, run install.sh with the following options:

Installing the Search Service Pack

2. Save the package to any location on your local system.

TeamSite Installation Guide 21

3. Change user to root.

5. Navigate into the SearchSP directory.

To install in console mode, run install.sh with the following option:

b. Edit the iw.search.locale property in

Installing a Base Release

Required Linux Downloads

Required Solaris Patch

What Gets Installed?

TeamSite Installation Guide 23

Default File Locations

Table 6 TeamSite installation locations

Retaining Essential Installation Information

TeamSite Installation Guide 25

Installation Log Files

 productname_timestampglobal_result.xml—Summary of each module’s

Module Log Files

ant ccwapp customtk transformtk tsupgrade

Each module has a corresponding log file that is by default located in

Product Log Files

productname_timestampglobal_result.xml—Summary of each module’s

Insert the TeamSite CD-ROM. Locate the install.sh installation program at