Ts 671sp1 Install Win v01 en

TeamSite ®
Installation Guide
Release 6.7.1
Service Pack 1
Windows
®
© 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-010-01-EN
August 2007
Table of Contents
About This Guide 11
Notation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Path Name Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Online Documentation Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Chapter 1: Installation Prerequisites 15
Server Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
CPUs and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
System Running Just the TeamSite Server . . . . . . . . . . . . . . . . . . . . . . . . . . .17
System Running Just the Interwoven Search Server . . . . . . . . . . . . . . . . . . . .18
System Running the TeamSite and Interwoven Search Servers . . . . . . . . . . .18
Disk Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Connecting Through the File System Interface . . . . . . . . . . . . . . . . . . . . . . . . . .19
Chapter 2: Installing TeamSite 21
Installing a Service Pack Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Installation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
TeamSite and Search Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Installing the TeamSite Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Installing the Search Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Installing a Base Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
What Gets Installed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
TeamSite Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Default File Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Retaining Essential Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Installation Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Module Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Product Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
TeamSite Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Password Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Interwoven Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Installing ReportCenter as a Standalone Module. . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Required Input for TeamSite and Search Installations. . . . . . . . . . . . . . . . . . . . . . . .29
TeamSite Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Search Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Installing TeamSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Installing Using Graphical Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Installing Interwoven Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Enabling Incremental Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Installing Using Graphical Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
TeamSite Installation Guide 3

Contents
Licensing TeamSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Troubleshooting Licensing Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Upgrading from a Pre-6.7.1 TeamSite Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
If Search is Installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Changes to iw.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Upgrade Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Post-upgrade Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Workflow Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Content and Permission Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Web Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Perl Scripts and Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Uninstalling TeamSite and Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Service Pack Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Base Release Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Chapter 3: Configuring Web Servers 69
Running the IIS Configuration Script Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Interwoven Web Server Port Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Configuring the iw-mount Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Configuring iw-mount for IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Enabling Server-Side Include Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Installing the Redirector Module for IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Web Server Plug-ins and VisualPreview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
ISAPI Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
IBM HTTP Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Apache Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Custom Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Stopping and Restarting the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Redirecting NSAPI HTTPS Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Redirecting to an Index Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Chapter 4: Configuring TeamSite Clients 79
Accessing TeamSite Using the Graphical User Interface . . . . . . . . . . . . . . . . . . . . .79
Installing Local File Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Viewing Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Accessing TeamSite Using the File System Interface . . . . . . . . . . . . . . . . . . . . . . . .81
Windows Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Creating Shortcuts from Windows Clients . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Troubleshooting Windows Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Macintosh Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
UNIX Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
FormsPublisher Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Interwoven, Inc. 4
Contents
Chapter 5: Loading Content Files 85

Creating a Content Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Content Store Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Supported File Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
Creating Multiple Content Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
Defining Content Stores in the iw.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Creating Content Stores using a CLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Viewing Content Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Creating a Subbranch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Creating a Workarea . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Populating the Initial Workarea. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Submitting Files to the Staging Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Publishing an Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
The ContentCenter Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Displaying Workareas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Displaying Workarea Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Clicking on Workarea Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Displaying Forms in the New Forms Module . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Displaying Files in the Work in Progress Module . . . . . . . . . . . . . . . . . . . . . . . .98
Displaying My Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Configuring Local File Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Workflow CGI Tasks and ContentCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Displaying Task Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
The Get Latest Operation in ContentCenter Standard . . . . . . . . . . . . . . . . . . . .101
Resolving Task Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Configuring Submit Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Eliminating Tagging Steps in Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Appendix A: Configuring Application Servers 103
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Configuration Procedures: Specific Web Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
ContentCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Event Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
Configuration Procedures: Overall App Server. . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Edit ibm-web-ext.xmi (WebSphere only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Appendix B: WebDesk Pro Transition Reference 113
Appendix C: Migrating Roles and Permissions 117
Migration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Steps Invoked by the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Steps to Invoke Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Migration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Workflow Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Index 121

Contents
Interwoven, Inc. 6
List of Tables
Table 1 Notation conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 2 Disk space required for TeamSite installation . . . . . . . . . . . . . . . . . . . . 15
Table 3 CPU and memory requirements: TeamSite server . . . . . . . . . . . . . . . . . 17
Table 4 CPU and memory requirements: Search server . . . . . . . . . . . . . . . . . . . 18
Table 5 CPU and memory requirements: TeamSite and Search servers . . . . . . . 18
Table 6 TeamSite installation locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 7 Information required for TeamSite installation . . . . . . . . . . . . . . . . . . . 29
Table 8 Information required for Interwoven Search installation . . . . . . . . . . . . 31
Table 9 File status and display in ContentCenter Standard . . . . . . . . . . . . . . . . . 98
Table 10 WebDesk Pro and ContentCenter Professional commands. . . . . . . . . . 113

List of Tables
Interwoven, Inc. 8
List of Figures
Figure 1 Introduction screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Figure 2 License Agreement screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Figure 3 Product Files screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Figure 4 License Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Figure 5 License File screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Figure 6 Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Figure 7 Content Store location screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Figure 8 IIS default configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Figure 9 Web Ports screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Figure 10 Ports in use screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Figure 11 Event Subsystem And Utility Daemon Ports screen . . . . . . . . . . . . . . . . .38
Figure 12 Event subsystem Database Type screen . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Figure 13 Event subsystem Database Configuration screen . . . . . . . . . . . . . . . . . . . .39
Figure 14 Event subsystem Database Drivers Directory screen . . . . . . . . . . . . . . . . .40
Figure 15 ReportCenter License Key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Figure 16 ReportCenter Database Type screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Figure 17 ReportCenter Database Configuration screen . . . . . . . . . . . . . . . . . . . . . .41
Figure 18 Crystal Enterprise Report Information screen . . . . . . . . . . . . . . . . . . . . . .42
Figure 19 Crystal Enterprise Report Database Information screen. . . . . . . . . . . . . . .42
Figure 20 Authentication Method screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Figure 21 ContentServices License Key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Figure 22 VisualAnnotate Administrator Email screen . . . . . . . . . . . . . . . . . . . . . . .44
Figure 23 ReportCenter Installation Information screen . . . . . . . . . . . . . . . . . . . . . .44
Figure 24 Installation Complete screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Figure 26 Product Files location screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Figure 27 TeamSite Server Host screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Figure 28 Functionality to Enable screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Figure 29 Search Server Ports and Shared Filesystem Location screen . . . . . . . . . . .49
Figure 30 Index Server Ports and Shared Filesystem Location screen . . . . . . . . . . . .50
Figure 31 Enable Incremental Updates screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Figure 32 Event Subsystem JNDI Server Port screen. . . . . . . . . . . . . . . . . . . . . . . . .51
Figure 33 Index Server Host and Port screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Figure 36 IIS confirmation screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Figure 37 Web Ports screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Figure 38 Event Subsystem and Utility Daemon Ports screen . . . . . . . . . . . . . . . . . .57
Figure 39 Event Subsystem Database Type screen. . . . . . . . . . . . . . . . . . . . . . . . . . .58
Figure 40 Event Subsystem Database Configuration screen . . . . . . . . . . . . . . . . . . .58
Figure 41 Event Subsystem Database Drivers Directory screen. . . . . . . . . . . . . . . . .59
Figure 42 ReportCenter License Key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Figure 43 ReportCenter Database Type screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

List of Figures
Figure 44 ReportCenter Database Configuration screen . . . . . . . . . . . . . . . . . . . . . .60

Figure 45 Crystal Enterprise Report Information screen . . . . . . . . . . . . . . . . . . . . . .61
Figure 46 Crystal Enterprise Report Database Information screen. . . . . . . . . . . . . . .61
Figure 47 Crystal Enterprise Authentication Method screen . . . . . . . . . . . . . . . . . . .62
Figure 48 ContentServices License Key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Figure 50 Microsoft Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Figure 51 Management Console Web site menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Figure 52 Management Console Web site properties . . . . . . . . . . . . . . . . . . . . . . . . .73
Figure 53 Filter Properties dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Figure 54 ContentCenter Standard Content module . . . . . . . . . . . . . . . . . . . . . . . . . .77
Figure 55 Content Store screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Figure 56 Content Store Properties screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Figure 57 Content Store Main branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Figure 58 ContentCenter Standard New Forms module . . . . . . . . . . . . . . . . . . . . . . .96
Figure 59 Non-TeamSite browser directory listing. . . . . . . . . . . . . . . . . . . . . . . . . . .97
Figure 60 ContentCenter Standard New Forms module . . . . . . . . . . . . . . . . . . . . . . .98
Figure 61 Files in ContentCenter Standard Work In Progress module . . . . . . . . . . . .99
Figure 62 ContentCenter Standard Tasks module. . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Figure 63 ContentCenter Standard Task Details screen . . . . . . . . . . . . . . . . . . . . . .101
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 should be familiar with IIS web servers, and with basic Windows operations such
as adding users and modifying ACLs.
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.

About This Guide
Table 1 Notation conventions (Continued)

Convention Definition and Usage
Monospaced Monospaced italics are used for command-line variables.The
italic most common example of this is iw-home, which refers to the
directory where TeamSite is installed. For example:
iw-home\etc\iw.cfg
is the path to the main TeamSite configuration file, iw.cfg,
which is located in the etc directory under the TeamSite
installation directory.
iwckrole role user
means that you must insert the values of role and user
yourself.
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. 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.
Path Name Conventions

In most cases, you can specify path names using standard Windows naming conventions
(which enable you to include spaces in path names). However, in some situations it
might be necessary to use MS-DOS naming conventions, which stipulate that no single
file or directory name in a path can contain a space or more than eight characters. If you
encounter unexpected system behavior after entering a path name using Windows
naming conventions, enter the path name again using MS-DOS conventions. For
example, instead of:
>C:\Program Files\Interwoven\TeamSite
you can try:

>C:\PROGRA~1\INTERW~1\TEAMSI~1
You can use the dir /x command to display the long and short versions of the file
names in the current directory.
Interwoven, Inc. 12
About This Guide
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

About This Guide
Interwoven, Inc. 14
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 2.2 GB 1.1 GB
requirement)
Additional temporary space (typically in 800 MB 800 MB
C:\Document And Settings\user id\Local
Settings\Temp; needed only during
installation procedure)
Additionally, if you install from the download package rather than from the CD-ROM,
you need 730 MB 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).

Chapter 1: Installation Prerequisites
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
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 3.0 GHz.
Interwoven, Inc. 16
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 N/A 1 CPU N/A 1 CPU
per Hour 1000 1 GB 1 GB 1 GB
RAM RAM RAM
1 CPU 2 CPUs 2 CPUs N/A 2 CPUs N/A
2000 1 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 4 CPUs 4 CPUs
1000 total licensed Interwoven
users 8 GB RAM 4 GB RAM
15 GB total content
300 concurrent users Contact Contact 4 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. 18
Disk Configuration
For maximum disk space efficiency, the TeamSite Content Store should be installed on
drives formatted with a 1024 byte cluster 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.
TeamSite can only be installed on a Windows server if the server has been added to
a valid Windows domain.
The display setting on the Windows server must support at least 256 colors or the
TeamSite installation program cannot be started.
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 connect to the TeamSite-shared IFS volume through their
local domains. For more information, see “Accessing TeamSite Using the File System
Interface” on page 81.

Interwoven, Inc. 20
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 45 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.
Interwoven, Inc. 22
3. Double-click the package.

A command window displays the package contents as they are extracted. The
extracted contents are placed in a directory, TeamSiteSP.
4. Navigate into the TeamSiteSP directory and find install.bat.
5. Double-click install.bat to start the installation process.
6. Click Next. 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.
7. Reboot the system after the installation is complete.
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.
3. Double-click the package.

A command window displays the package contents as they are extracted. The
extracted contents are placed in a directory, SearchSP.
4. Navigate into the SearchSP directory and find install.bat.
5. Double-click install.bat to start the installation process.
6. Follow the installation procedure.
7. Reboot the system after the installation is complete.

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”.
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 4, “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)
Interwoven, Inc. 24
ContentServices SOAP Server

FormsPublisher (formerly TeamSite Templating, which had its own installation
program)
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
C:\Program Files\ Default location of TeamSite program files. The location of
Interwoven\TeamSite this directory may be changed during installation. This
directory is often installed in a location with a shorter path,
such as C:\Interwoven\TeamSite. With some system
configurations, this shorter path is necessary to allow
configuration of the iwperl and CGI areas. Wherever it is
located, this directory is referred to throughout this manual
as iw-home.
Note: The TeamSite installation defaults to the system root
drive. In this example, C:\ is used.
C:\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.
Y:\ Default location of the TeamSite Intelligent File System
volume.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 virtual
directories must be updated to reflect this.
C:\Program Files\ Directory for managing all Interwoven software on the
Interwoven\iwinstall 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 31. TeamSite
also supports the IBM WebSphere and BEA WebLogic application servers. See
“Configuring Application Servers” on page 103 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.
Interwoven, Inc. 26
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
Each module has a corresponding log file that is by default located in

C:\Program Files\Interwoven\iwinstall\modules\module_name\. 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 default location of these files is:
C:\Program Files\Interwoven\TeamSite\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.
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 20 on page 39 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 45 for
details.
Installing ReportCenter as a Standalone Module

When you install TeamSite, you are also prompted to install and configure ReportCenter
(see step 22 on page 40). 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 Administrator on the system where you want to install ReportCenter.
This is the same system that hosts the TeamSite server.
3. Set the PATH environment variable to:
dir_name\TeamSite\InstallerData\jre\bin
where dir_name is the directory where you unpacked the TeamSite installation
package.
4. 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.
top_level_unpacking_folder\TeamSite\InstallerData\modules\tsreport\
Disk1\InstData\NoVM
5. Execute the following command:

.\tsreport.exe -f iwinstall\log\
TeamSitelatest_timestampinstall.properties
6. The first ReportCenter installation screen is displayed as shown in step 21 on

page 40. Follow the directions in the installation documentation from there.
Interwoven, Inc. 28
Required Input for TeamSite and Search

Installations
The following tables describe the information for which you are prompted during
TeamSite and Interwoven Search installations.
TeamSite Information
Table 7 Information required for TeamSite installation
Default
Information Step Notes
Provided?
Location of TeamSite step 6 on page 33 Yes Referred to as iw-home
program files. throughout documentation.
TeamSite license file. step 9 on page 34 No The file must be named
TS.lic and reside in
iw-home\etc.
Location of Content step 14 on Yes
Store. page 36
Automatic vs. manual IIS step 15 on Yes Manual configuration is a
configuration. page 36 post-installation task and is
described in “Running the
IIS Configuration Script
Manually” on page 69.
Web server ports: HTTP, step 16 on Yes
HTTPS, Servlet, Proxy, page 36
and Web Server.
Event subsystem ports: step 17 on Yes
OpenJMS server, JNDI page 38
server, and utility
daemon.
Event subsystem database step 17 on Yes
type. page 38
Event subsystem database step 19 on No Required only if a database
information: server name, page 39 was selected in the previous
listen port, database step.
name, administrator
name, and administrator
password.
Location of event step 20 on No Required only for mssql and
subsystem database page 39 db2.
drivers.
ReportCenter license key. step 21 on No Required only if installing
page 40 ReportCenter at this time.
ReportCenter can optionally
be installed later as a
separate module.

Table 7 Information required for TeamSite installation (Continued)

Default
Information Step Notes
Provided?
ReportCenter database step 23 on Yes Required only if installing
type. page 41 ReportCenter at this time.
Location of ReportCenter step 23 on No Required only for mssql and
database drivers. page 41 db2.
ReportCenter database step 23 on No Required only if installing
information: server name, page 41 ReportCenter at this time
listen port, database and if the ReportCenter
name, administrator database type is db2 or
name, and administrator mssql.
password.
Crystal Enterprise system step 24 on No Root location is on the
information: host name page 41 Crystal Enterprise server,
and root path where not the TeamSite server.
TeamSite reports are
located.
Crystal Enterprise step 25 on No Refers to the system on
database information: page 42 which Crystal Enterprise
datasource name and (not TeamSite) is installed.
database name.
Crystal Enterprise step 26 on Yes Choices are LDAP or
authentication method. page 42 Enterprise.
ContentServices license step 27 on No You can optionally proceed
key. page 43 without a license key and
install one after completing
the TeamSite installation.
VisualAnnotate step 28 on No Only applies to English
administrator email page 43 locales.
address.
Interwoven, Inc. 30
Search Information
Table 8 Information required for Interwoven Search installation
Default
Information Step Provided Notes
?
Location of Interwoven step 4 on page 47 Yes
Search program files.
Name of the TeamSite step 5 on page 47 Yes
server.
Whether to enable Search, step 6 on page 48 Yes You must enable at least
indexing, or both. one.
Search server port and file step 7 on page 48 Some Required only if Search
system information: search 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 9 on page 49 Some Required only if indexing
stem information: index 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 9 on page 49 Yes Required only if indexing
incremental updates. was enabled in an earlier
step.
Event subsystem JNDI port. step 11 on page 51 Yes Required only if
incremental updates were
enabled in the previous
step. This is the same
value that was entered in
step 17 on page 38.
Indexing server host name step 12 on page 51 Some Required only if you
and port. 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
graphical mode (interactive GUI-based prompts). If you are installing a service pack,
see “Installing the TeamSite Service Pack” on page 22.

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 53.
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 22 and “TeamSite and
Search Compatibility” on page 22 for more information.
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.”
To install TeamSite on your server:

1. Log in as Administrator on the system where you want to install the TeamSite
server.
2. If you are installing from CD, insert the TeamSite CD and browse to the top-level
directory. Go to step 4 and continue from there.
If you are installing from the Interwoven download site, copy the
IWOVts-win-6.7.1.0-Build#####.exe file (where ##### represents the TeamSite
build number) to a temporary directory on a local drive.
NOTE
Do not copy the .exe file into a directory whose name contains spaces, such as
C:\Documents and Settings.
3. From the temporary directory, double-click IWOVts-win-6.7.1.0-Build#####.exe.

A TeamSite subdirectory is created, into which the contents of the .exe file are
expanded.
4. Navigate to the TeamSite directory and double-click install.bat.The Introduction
screen displays.
Interwoven, Inc. 32
Figure 1 Introduction screen
5. Click Next. The License Agreement screen is displayed.

Figure 2 License Agreement screen
6. Click the I accept... button and then click Next if you agree with the terms. Click
Previous or Cancel if you do not agree with the terms.
7. 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 13 on page 55
for more information.
If the installation program does not detect an older version of TeamSite on your
system, the Product Files screen is displayed prompting you for the location where
the TeamSite program files will be installed.

Figure 3 Product Files screen
8. Click Next to accept the default installation location for the TeamSite program files
(C:\Program Files\Interwoven\TeamSite) or click Choose to select another
location.
NOTE
If you specify an alternate location for the program files or the Content Store (in the
next step), you must use ASCII characters.
The location selected in this step is typically referred to as iw-home in the

documentation.
After configuring the installer for your installation directory, click Next. The
License Information screen displays instructions for obtaining a TeamSite license.
Figure 4 License Information screen
9. 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.
Interwoven, Inc. 34
Figure 5 License File screen
10. 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, an Information screen prompts you to proceed. Click
Install.
Figure 6 Information screen
12. If IIS is installed, you are prompted to specify whether to stop IIS. Accept the
default (Yes), which stops IIS and allows the installer to proceed.
13. The installation program prompts you for the location of the TeamSite Content
Store.

Figure 7 Content Store location screen
14. Click Next to accept the default location for the Content Store (C:\iw-store) or
click Choose to select another location.
NOTE
Do not use the iw-home location for the ContentStore location; specify a different
location.
If a Microsoft IIS Web server is installed on your system, you are prompted whether
you want to configure IIS for use with TeamSite.
Figure 8 IIS default configuration screen
15. Click Next to accept the default setting (Yes) and have the installation program
automatically configure IIS, or select No and manually configure your web server
after completing the TeamSite installation (see “Running the IIS Configuration
Script Manually” on page 69). It is recommended that you select auto-configuration.
16. The Web Ports screen is displayed prompting you for the port numbers used by the
Interwoven Web Daemon.
Interwoven, Inc. 36
Figure 9 Web Ports screen
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 because that Web server rendered both the
TeamSite UIs and content files. This is no longer the case with TeamSite.
Click Install to accept the default values, or edit the values and click Install. 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 to use
the selected port numbers by clicking Next.

Figure 10 Ports in use screen
17. After selecting the Web server ports, the Event Subsystem And Utility Daemon
Ports screen is displayed.
Figure 11 Event Subsystem And Utility Daemon Ports screen
18. 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.
Interwoven, Inc. 38
Figure 12 Event subsystem Database Type screen
19. 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 22 and continue
the installation procedure from there.
If you select a database rather than default, the Database Configuration screen is
displayed.
Figure 13 Event subsystem Database Configuration screen
20. 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).
If you selected default, oracle, or MySQL in step 19, the TeamSite Report Server
License Key screen is displayed. Go to step 22 and continue the installation
procedure from there.

If you selected mssql or db2 in step 19, the Database Drivers Directory screen is
displayed.
Figure 14 Event subsystem Database Drivers Directory screen
21. Enter or browse to the location of the drivers used by the event subsystem database.
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.
Click Install. The TeamSite ReportCenter License Key screen is displayed.

Figure 15 ReportCenter License Key screen
22. If you plan to use ReportCenter, enter the ReportCenter license key you received
from Interwoven and click Next. Go to step 23 and continue the installation
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, click Next without entering a license key. Go
to step 25 and continue the installation procedure from there.
23. The Database Type screen is displayed for ReportCenter.
Figure 16 ReportCenter Database Type screen
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.
Figure 17 ReportCenter Database Configuration screen
24. 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).
Click Install. The Crystal Enterprise Report Information screen is displayed.

Figure 18 Crystal Enterprise Report Information screen
25. 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). The host should be different from the system
that hosts the TeamSite server.
Click Next. The Crystal Enterprise Report Database Information screen is
displayed.
Figure 19 Crystal Enterprise Report Database Information screen
26. 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).
Click Next. The Authentication Method screen is displayed.
Interwoven, Inc. 42
Figure 20 Authentication Method screen
27. Select the authentication method and click Install. The ContentServices License
Key screen is displayed.
Figure 21 ContentServices License Key screen
28. 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 CS 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 is displayed.

Figure 22 VisualAnnotate Administrator Email screen
29. Enter the email address of the person or group who will be administering your
TeamSite installation and click Install.
This 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.
The installation program configures and installs the program files on your system. If
ReportCenter is not installed and configured, a notice is displayed containing
instructions for the installation and configuration.
Figure 23 ReportCenter Installation Information screen
30. If you need to install ReportCenter, follow the displayed instructions after
completing the TeamSite installation procedure. The instructions are also located in
“Installing ReportCenter as a Standalone Module” on page 28.
Interwoven, Inc. 44
Click Next. The Install Complete screen is displayed when the TeamSite installation
procedure is finished. If there were any compilation errors, they are described
onscreen.
Figure 24 Installation Complete screen
31. Click Done, then reboot the system.

32. After logging back in to your system, click Continue to complete the TeamSite
configuration.
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 22
“TeamSite and Search Compatibility” on page 22
“If Search is Installed” on page 53
The sections that follow describe how to install the Interwoven Search base product
using graphical mode (interactive GUI-based prompts). If you are installing a Search
service pack, see “Installing the Search Service Pack” on page 23.
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
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 10 on page 50). 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 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. Log in as Administrator on the system where you want to install the search server.
2. Either:
Go to the Interwoven download site and download the installation file
(IWOVtssrh-win-2.1.0.0-Build#####.exe 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 5 and continue the installation from there.
Insert the Search installation CD-ROM. Locate the install.bat installation
program at the top level of the CD-ROM contents. Go to step 5 and continue the
installation from there.
From the temporary directory, double-click
IWOVtssrh-win-2.1.0.0-Build#####.exe. A Search subdirectory is created, into
which the contents of the search installation package are expanded.
Navigate to the Search directory and double-click install.bat.The Introduction
screen displays.
Interwoven, Inc. 46
3. Click Install to continue. The License Agreement screen is displayed.

4. 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.
Figure 26 Product Files location screen
5. Click Install to accept the default installation location for the search program files
(C:\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 27 TeamSite Server Host screen
6. 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 28 Functionality to Enable screen
7. 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 8 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 9 and continue the installation from there.
Interwoven, Inc. 48
Figure 29 Search Server Ports and Shared Filesystem Location screen
8. 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).
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 7, the Index Server Ports and Shared Filesystem
Location screen is displayed. Go to step 9 and continue the installation from there.
If you did not enable indexing in step 7, the Index Server Host and Port screen is
displayed. Go to step 12 and continue the installation from there.
9. The Index Server Ports and Shared Filesystem Location screen appears:

Figure 30 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 8.
Click Install. The Enable Incremental Updates screen is displayed.
Figure 31 Enable Incremental Updates screen
10. 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 Next.
If you enabled incremental updates, the Event Subsystem JNDI Server Port screen is
displayed. Go to step 11 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 12 or step 13
and continue the installation from there.
Interwoven, Inc. 50
11. The Event Subsystem JNDI Server Port screen appears:

Figure 32 Event Subsystem JNDI Server Port screen
Enter the Event Subsystem port number. This is the same JNDI port number that
you specified in step 17 on page 38.
Click Install.
If you enabled search but not indexing in step 7 on page 48, the Index Server Host
and Port screen is displayed. Go to step 12 and continue the installation from there.
Otherwise, go to step 13 and continue from there.
12. The Index Server Host and Port screen appears:
Figure 33 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.
13. The installation program configures and installs the search program files on your
system. When the installation is finished, the Install Complete screen is displayed.

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
Interwoven, Inc. 52
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.
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 22.
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 63 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 Administrator.
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:
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
4. Ensure that rmiregistry.exe is not invoked when the system is rebooted:

Open the Services control panel (Start > Settings > Control Panel >
Administrative Tools > Services).
Change the Startup Type of all Interwoven services to manual (right-click the
service name, select Properties, then Manual from the drop-down menu).
Reboot the system.
5. Stop the Web server that supports TeamSite.
Interwoven, Inc. 54
6. If you are installing from CD, insert the CD and browse to the top-level directory.
Go to step 8 and continue from there.
If you are installing from the Interwoven download site, copy the
IWOVts-win-6.7.1.0-Build#####.exe file (where ##### represents the TeamSite
build number) to a temporary directory on a local drive.
NOTE
Do not copy the .exe file into a directory whose name contains spaces, such as
C:\Documents and Settings.
7. From the temporary directory, double-click IWOVts-win-6.7.1.0-Build####.exe.

A TeamSite subdirectory is created, into which the contents of the .exe file are
expanded.
8. Navigate to the TeamSite directory and double-click install.bat.The Introduction
screen displays.
9. 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.
10. 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.
11. The TeamSite license file must be named TS.Lic, and it must reside in a readable
location on the TeamSite server. To install TS.lic in the default location
(iw-home\etc), click Next.
12. If the license if is valid, an Information screen prompts you to proceed by clicking
Install.
13. 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, the installation continues as described in 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 to abort the installation.
You must update the currently installed modules to correct the displayed
incompatibilities before attempting another TeamSite 6.7.1 installation.
14. If the installation program detects an IIS server, it displays the IIS window:
Figure 36 IIS confirmation screen
15. Click Next to accept the default setting (Yes) and have the installation program
automatically configure IIS, or click No and manually configure your web server
after completing the TeamSite installation (see “Running the IIS Configuration
Script Manually” on page 69). It is recommended that you select auto-configuration.
16. The Web Ports screen displays, prompting you for the port numbers used by the
Interwoven Web Daemon.
Figure 37 Web Ports screen
Interwoven, Inc. 56
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.
17. 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 you select the ports, the Event Subsystem And Utility Daemon Ports screen is
displayed.
Figure 38 Event Subsystem and Utility Daemon Ports screen
18. 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 39 Event Subsystem Database Type screen
19. 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 22 and continue
the installation procedure from there.
If you select a database rather than default, the Database Configuration screen is
displayed.
Figure 40 Event Subsystem Database Configuration screen
20. 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
Password).
If you selected default, oracle, or MySQL in step 19, the ReportCenter License Key
screen is displayed. Go to step 22 and continue the installation procedure from there.
Interwoven, Inc. 58
If you selected mssql or db2 in step 19, the Database Drivers Directory screen is
displayed.
Figure 41 Event Subsystem Database Drivers Directory screen
21. Enter or browse to the location of the drivers used by the event subsystem database.
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.
Click Install. The TeamSite ReportCenter License Key screen is displayed.

Figure 42 ReportCenter License Key screen
22. If you plan to use ReportCenter, enter the ReportCenter license key you received
from Interwoven and click Next. Go to step 23 and continue the installation
If you do not plan to use ReportCenter, click Next without entering a license key. Go
to step 28 and continue the installation procedure from there.
23. The Database Type screen is displayed for ReportCenter.

Figure 43 ReportCenter Database Type screen
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.
Figure 44 ReportCenter Database Configuration screen
24. 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).
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.
Interwoven, Inc. 60
Figure 45 Crystal Enterprise Report Information screen
25. 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).
Click Next. The Crystal Enterprise Report Database Information screen is
displayed.
NOTE
already configured.
Figure 46 Crystal Enterprise Report Database Information screen
26. 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).
Click Next. The Authentication Method screen is displayed.

NOTE
already configured.
Figure 47 Crystal Enterprise Authentication Method screen
27. Select the authentication method and click Install. The ContentServices License
Key screen is displayed.
Figure 48 ContentServices License Key screen
28. 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.
Interwoven, Inc. 62
29. 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.
30. Click Done, then reboot the system.
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.
Interwoven, Inc. 64
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.
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. Select Interwoven TeamSite Index in the Services control panel and click
Restart.
2. Select Interwoven TeamSite Search in the Services control panel and click
Restart.
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
Interwoven, Inc. 66
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
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

1. Select Start > Settings > Control Panel > Add/Remove Programs.
The Add/Remove Programs window is displayed. Note that this process may differ
depending on the version of Windows you are using.
2. TeamSite:
a. Select Interwoven TeamSite Service Pack 1.
b. Click Change/Remove.
The Service Pack Uninstall window displays.
c. Click Next.
The service pack is removed from the system.
Search:
a. Select Interwoven Search Service Pack 1.
b. Click Change/Remove.
The Service Pack Uninstall window displays.
c. Click Next.
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
Complete the following procedures to uninstall TeamSite and Interwoven Search.

1. Log in as Administrator to the system where TeamSite and Search are installed.
2. Click Start > Settings > Control Panel.
3. Double-click the Add/Remove Programs icon. The Add/Remove Programs
window is displayed.
4. Select Interwoven Search from the list of applications.
5. Click the Change/Remove button. The Uninstall Introduction window is displayed.
6. Click Next.
7. Click Done.
8. Select Interwoven TeamSite from the list of applications.
9. Click the Change/Remove button. The Uninstall Introduction window is displayed.
10. Click Next.
11. Click Done, then reboot the system. TeamSite, search, and their related files are
removed from your system.
NOTE
The uninstallation program does not remove the C:\Program Files\Common
Files\Interwoven\lib entry from your system PATH variable. After completing the
uninstallation, remove this entry manually.
NOTE
The TeamSite and Search uninstallers rely on information in the
\Interwoven\iwinstall directory. Therefore, do not modify or remove files in that
directory.
Interwoven, Inc. 68
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:
Microsoft Internet Information Server (IIS) 5.0
The chapter contains information about the following topics:

Running the IIS Configuration Script Manually
Interwoven Web Server Port Number
Configuring the iw-mount Alias
Enabling Server-Side Include Requests
Stopping and Restarting the Web Server
Troubleshooting
Redirecting NSAPI HTTPS Requests
Running the IIS Configuration Script Manually

The TeamSite installation program offers an option to automatically configure IIS. If
you chose not to configure IIS during installation, you can use the configuration script,
tspostreboot.pl, to configure IIS after you reboot the system following installation.
Before running tspostreboot.pl, make sure the system’s Y: drive is up. The following
command will configure IIS to run with TeamSite:
>iw-home\iw-perl\bin\perl iw-home\install\tspostreboot.pl iw-home IIS

Chapter 3: Configuring Web Servers
Interwoven Web Server Port Number

You must provide the Interwoven Web server (iwwebd) port number value during
TeamSite installation. The default values are 80 for HTTP and 443 for HTTPS. These
port numbers are recorded in iw-home\etc\iw.cfg as follows (assuming the default
values):
[iwwebd]
http_port=80
https_port=443
When the TeamSite 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.)
The TeamSite 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 iw-home\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 default location of the
TeamSite Intelligent File System volume. If you are upgrading TeamSite 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 IIS

If you are using Microsoft IIS, the configuration script automatically creates and
configures the properties for the iw-mount alias. It also creates a new web directory
under the default Web site. If these tasks are completed, no further configuration of the
iw-mount alias is necessary.
Interwoven, Inc. 70
The virtual directory iw-mount (which points to the Y:\ drive) is created under a site
called Default Web Site with a port number of 81. One of the following Web sites is
chosen (in order of preference):
IW-Mount Web Site—Selected if you reinstall TeamSite 6.7.
TeamSite—Selected if a pre-5.0 version of TeamSite is already installed.
Default Web Site—IIS default.
Any Web site on the customer-selected port.
If none of these are found, the installation script creates and uses IW-Mount Web Site on
your selected port.
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 TeamSite 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 IIS

To install the redirector module for IIS:
1. Click Start > Run and type C:\WINNT\system32\inetsrv\iis.msc to open the
Microsoft Management Console.

Figure 50 Microsoft Management Console
2. Open the Internet Information Server folder.

3. Click the icon associated with the name of your server.
4. Right-click the Default Website icon to display the drop-down menu.
Figure 51 Management Console Web site menu
5. Select Properties from the drop-down menu. The Default Web Site Properties
dialog box is displayed.
Interwoven, Inc. 72
Figure 52 Management Console Web site properties
6. In the Default Web Site Properties dialog box, click the ISAPI Filters tab, then click
Add. The Filter Properties dialog box is displayed.
7. In the Filter Properties dialog box, enter iwrewrite in the Filter Name field.
Figure 53 Filter Properties dialog
8. Click Browse and highlight the iwproxy_isapi.dll file in the iw-home\lib

directory.
9. Click Open.
10. Click OK in the Filter Properties dialog box to complete the configuration of the
TeamSite redirector module for SSIs.
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 TeamSite 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,TeamSite (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 IIS that sets the x-iw-ts-vpath response header is distributed with
TeamSite.
Detailed information about using these plug-ins is contained in the following section.
ISAPI Plug-ins
The existing ISAPI (IIS) Web server plug-in implements the x-iw-ts-vpath response
header. To install it, refer to “Installing the Redirector Module for IIS” on page 71.
IBM HTTP Plug-ins
The plug-in for IBM HTTP Server 2.0 requires the installation procedure described in
this section. An optional technique for handling SSIs is also recommended. This
procedure is documented in the following Knowledge Base article (the instructions refer
to Apache, but are equally valid for IBM HTTP):
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=51890
The installation procedure for the IBM HTTP plug-in is as follows:

1. Copy mod_a2_iw_ts_vpath.dll from iw-home/lib to IBM HTTP Server
Home/modules/
2. Edit IBM HTTP Server Home/conf/httpd.conf so that the following line is the first
line in the LoadModule section:
LoadModule a2_iw_ts_vpath_module modules/mod_a2_iw_ts_vpath.dll
3. Establish an /iw-mount/ alias:

Alias /iw-mount/ Y:/
4. Restart the IBM HTTP server.
Interwoven, Inc. 74
Apache Plug-ins
TeamSite 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.
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:
[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.
Troubleshooting
If you are using an IIS Web server and SSI requests are not executing properly, try the
following procedure:
1. Click Start > Run and type mmc to open the Microsoft Management Console.
2. Right-click on the name of your Web server.
3. Select Properties.
4. Select the Home Directory tab.
5. Select Configuration.
6. Select the App Mappings tab.
7. Confirm that files with an .htm extension are mapped to the following file:
WINNT\system32\inetsrv\ssinc.dll
If the application mapping does not exist, create it.

8. Apply changes and confirm by selecting OK.
Redirecting NSAPI HTTPS Requests

You can configure TeamSite to redirect HTTPS requests from TeamSite 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 TeamSite 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-secureTeamSite server just as it would
Interwoven, Inc. 76
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 TeamSite 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 54 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, continue the initial configuration by
creating at least one TeamSite client as described in the next chapter.

Interwoven, Inc. 78
Chapter 4
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 Administrator 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
Administrator 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.
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

Chapter 4: Configuring TeamSite Clients
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).
Interwoven, Inc. 80
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 a shared
network volume. 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 the command line (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
access the TeamSite server as a shared volume. The following procedure describes how
to access TeamSite using Network Neighborhood.
To access TeamSite from Windows, use Network Neighborhood to locate the TeamSite
server. You can navigate to any directory in TeamSite (for example, the top level of a
branch or workarea, or a directory within a workarea), and create a shortcut to that
directory.
You can also mount the TeamSite server as a networked drive. To do this:
1. In Windows Explorer, select Map Network Drive from the Tools menu.
2. Select the drive letter you want to map the TeamSite server to from the Drive menu.
3. Locate and double-click on the TeamSite server in the Shared Directories list.
4. Double-click on IWServer to mount the TeamSite server as a networked drive.
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.
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.
Interwoven, Inc. 82
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.
Interwoven, Inc. 84
Chapter 5
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 113, and an introduction to ContentCenter is on page 95.
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 C:\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 5: 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 87.
Supported File Objects
TeamSite Content Stores support the following file objects:

Files
Directories
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 89.
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.
Interwoven, Inc. 86
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 C:\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 C:\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 the user you are logged in as 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
iw-home\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:
shift-jis (Japanese)
cp1252 (French or German)
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=C:\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=C:\salesAsiastore_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.
Interwoven, Inc. 88
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.
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 the user you are logged in as 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 C:\iw-store\ 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 C:\iw-store\default 0x64
store1 C:\iw-store\store1 0x65

Viewing Content Stores

To view a Content Store in ContentCenter Professional, highlight the Content Store:
Figure 55 Content Store screen
Click Properties to view the properties of the store:
Figure 56 Content Store Properties screen
All Content Stores (including the system-generated default) contain a Main branch that
contains a staging area, edition, and workarea:
Interwoven, Inc. 90
Figure 57 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.exe 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 (including domain) of the workarea’s owner in the Owner
box (for example, WEBSTER/andre).
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.
Interwoven, Inc. 92
e. Type or browse to the edition to use as the basis for the workarea.
f. Click OK.
You can also use the iwmkwa.exe command-line tool (see the TeamSite Command-Line
Tools manual for details).
Populating the Initial Workarea

To populate an initial workarea:
1. From the Windows file system, log in as Administrator.
2. Copy your content files into the new workarea (default location):
Y:\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.
3. Navigate to the workarea and ensure the file permissions are correct before
submitting the files to the staging area; if not, set standard Windows ACLs on the
content files.
Because TeamSite considers a change in ACLs 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.
To set permissions on content files and directories:
a. Select either a file or directory, and right-click on it.
b. Select Properties from the drop-down menu.
c. Click on the Security tab.
The Security window is displayed.
d. Add the appropriate users and groups, and, in the case of a directory, determine
whether to apply permission changes recursively down the entire directory tree.
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.exe 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.exe command-line tool to publish an edition (see the
TeamSite Command-Line Tools manual for details).
Interwoven, Inc. 94
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 58 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, IIS) 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 73.
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:
Interwoven, Inc. 96
Figure 59 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 73). 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 60 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 9 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
Interwoven, Inc. 98
Table 9 File status and display in ContentCenter Standard (Continued)

Displayed in Work In Progress
File State
Module?
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 61 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 62 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 79.
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.
Interwoven, Inc. 100

Displaying Task Variables

By default, the ContentCenter interfaces display the Priority and Due Date task
variables:
Figure 63 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.

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:
From the Services panel, stop the servletd process.
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:

From the Services panel, stop the servletd process.
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.
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 10 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 10 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.exe
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.exe
Alternatively, to generate the accessresults.xml manifest file without

completing the migration, use the -m option:
> iwaccessmigrate.exe -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.exe -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. Reboot the system to restart all TeamSite services. When the TeamSite server starts
for the first time, it could take longer than usual as the new permission and role
information is processed. Subsequent starts will take the normal amount of time.

Workflow Migration
Prior to TeamSite 6.7, external tasks in workflows ran as Administrator or the user who
started TeamSite. Starting with TeamSite 6.7, external tasks on Windows hosts run as
the task owner. The external task is restricted to the permissions associated with the task
owner. This potentially can cause problems with workflows that previously were able to
do privileged operations based on the user rather than the task owner.
To address this issue, if any external tasks need to be run as a special user, such as
Administrator or root, the workflows should be modified so that this user is the owner of
the task. Also, that account must be added as a TeamSite user if it is not already.
You can also configure TeamSite 6.7 so that external tasks revert back to pre-6.7
behavior by assigning the impersonate_without_password attribute with the value
false in the iw.cfg file:
[iwserver]
impersonate_without_password=false
This setting is subject to some limitations; see “Configuring the TeamSite Server” in the
TeamSite Administration Guide for details.

Index
Symbols copying files 93
.shtml files 71 CPU requirements 16
creating
branches 91
A workareas 92
accessing TeamSite 81
activating backing stores 89 D
database
B event subsystem 39, 58
backing store default file locations 25
activating 89 disk configuration 19
comments 88 disk space
disk space 19 partitions 19
encoding of names 87 documentation
location 25, 35 iw-home variable 34
moving 89
multibyte characters 87 E
Backup Domain Controller (BDC) 19 editions
branches initial 92
creating 91 new 94
restrictions on names 91 publishing 94
setting locking model 92 encoding
of backing store names 87
C of contents of iw.cfg 87
CGI tasks 100 text editors 87
configuring in ContentCenter GUIs 100 errata 13
clients event subsystem
TeamSite 81 database 39, 58
CLTs
iwreset 88 F
iwstoreadm 89 file system interface
comments network connection 19
publish 94 using 19
submit files
individual file 94 install log 32
keywords 94
submit operation 94 install.exe 32, 46, 55
configuring iwinstal_log.log 32
disk space 19 parsing .shtml 71
iw-mount alias 70 submitting to the staging area 93
web servers 69
conventions
path name 12
conventions, notation 11

Index
H multibyte characters
High Availability in backing store names 87
about 103, 113
HTTPS requests, redirecting 76 N
NetBEUI 82
I network drive 81
IIS notation conventions 11
configuring 69
incremental updates 46 P
initial edition 92 parsing .shtml files 71
install log location 32 path name conventions 12
install.exe 32, 46, 55 port 80 36, 56
installing port number
FormsPublisher 21 http server 36, 56
required access for 28, 32, 46, 54 web server 37, 57
required information 29 port numbers
search 46 Interwoven Web Daemon 37, 56
TeamSite 31, 32 ports
internationalization web server 70
text editor encoding 87 Primary Domain Controller (PDC) 19
iPlanet web server program files
aliases 76 location 33, 47
iw.cfg program files, default location 25
activating change to 88 publishing editions
encoding of 87 about 94
iw-home adding comments 94
about 25 first edition 94
iw-home variable 34 through the command line 94
iw-mount alias 70 through the TeamSite GUI 94
iwreset 88
iw-store directory, backing up 54, 68
iwstoreadm 89 R
RAID configurations 19
J redirecting HTTPS requests 76
redirector module
JavaScript 79 introduced 71
Reporting
L standalone installation 28
requirements
license keys
backing store 19
troubleshooting 53
CPU 16
loading content 85
local domains 19
Local File Manager S
about 81 SCSI controllers and drives 19
installing 81 search
locations installing 46
default program files 25 server-side includes 71
locking model 92 Service Packs, uninstalling 68
shared volume 19, 81
M SSIs, enabling 71
moving staging area 92
backing stores 89 submit filtering 93
submit task, ownership 102

Index
submitting, files to staging 93 shared 92

Sun ONE web server submitting to the staging area 93
aliases 76
supported web servers 69
T
tasks
CGI 100
ownership 102
TeamSite
accessing
through the file system 81
through the GUI 79
troubleshooting 82
clients 79, 81
FormsPublisher 21
High Availability 103, 113
see also High Availability
installing 32
mounting 81
populating 93
Service Pack 1 68
uninstalling 68
text editor encodings 87
troubleshooting, license keys 53
U
uninstalling
TeamSite 68
uninstalling TeamSite 68
V
VisualPreview
for SSIs 71
required plug-ins 73
W
web daemon 37, 56
web servers
aliases 25
configuring 69
iPlanet 76
port number 37, 57, 70
stopping and starting 75
Sun ONE 76
supported 69
window.opener Javascript object 100
workareas
creating 92
naming conventions 92
populating 93
private 92

Index

Ts 671sp1 Install Win v01 en

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ts 671sp1 Install Win v01 en

Uploaded by

Copyright:

Available Formats

TeamSite ®

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

TeamSite Installation Guide

TeamSite Installation Guide 3

Licensing TeamSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Chapter 5: Loading Content Files 85

TeamSite Installation Guide 5

TeamSite Installation Guide 7

TeamSite Installation Guide 9

Figure 44 ReportCenter Database Configuration screen . . . . . . . . . . . . . . . . . . . . . .60

Table 1 Notation conventions

TeamSite Installation Guide 11

Table 1 Notation conventions (Continued)

Path Name Conventions

you can try:

Online Documentation Errata

TeamSite Installation Guide 13

Server Hardware Requirements

Table 2 Disk space required for TeamSite installation

TeamSite Installation Guide 15

CPUs and Memory

All CPUs should be at least 3.0 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 17

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 19

Installing a Service Pack Release

TeamSite Installation Guide 21

TeamSite and Search Compatibility

Installing the TeamSite Service Pack

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

3. Double-click the package.

Installing the Search Service Pack

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

3. Double-click the package.

TeamSite Installation Guide 23

Installing a Base Release

What Gets Installed?

 ContentServices SOAP Server

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

TeamSite Log Files

These files are:

TeamSite Installation Guide 27

Installing ReportCenter as a Standalone Module

5. Execute the following command:

6. The first ReportCenter installation screen is displayed as shown in step 21 on

ContentServices SOAP Server

productname_timestampglobal_result.xml—Summary of each module’s

In the java.naming.provider.url=tcp://host:port/ property, set host to the