WS Authoring 7.3 Install Rev4 en

Web Solutions Authoring Components Installation Guide
Version 7.3
Document Revision 4 5 November 2012
Copyright Notice
Notice
This documentation is a proprietary product of Autonomy and is protected by copyright laws and international treaty. Information in this documentation is subject to change without notice and does not represent a commitment on the part of Autonomy. While reasonable efforts have been made to ensure the accuracy of the information contained herein, Autonomy assumes no liability for errors or omissions. No liability is assumed for direct, incidental, or consequential damages resulting from the use of the information contained in this documentation. The copyrighted software that accompanies this documentation is licensed to the End User for use only in strict accordance with the End User License Agreement, which the Licensee should read carefully before commencing use of the software. No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of the copyright owner. This documentation may use fictitious names for purposes of demonstration; references to actual persons, companies, or organizations are strictly coincidental.
Trademarks and Copyrights

Copyright 2012 Autonomy Corporation plc and all its affiliates. All rights reserved. Advise, AudioLogger, Autonomy etalk, ContentServices, ControlHub, DataDeploy, etalk PRO, etalk, e-talk, Expert, Explore, Interwoven, LiveSite, MediaBin, Media Aggregation Service, Observe, OpenDeploy, Optimost, Qfiniti Enterprise 3, Qfiniti, Recorder, SmartEncode, SoftSound, SoftSound Analysis Plug-in, Survey, TeamSite, VideoLogger, Virage ControlCenter, Virage Encoder, Virage SmartEncode, Virage VideoLogger, Virage, VisualAnnotate, VS Archive, VS Broadcast Monitoring, and all related titles and logos are trademarks of Autonomy Corporation plc and its affiliates, which may be registered in certain jurisdictions. Microsoft is a registered trademark, and MS-DOS, Windows, Windows 95, Windows NT, SharePoint, and other Microsoft products referenced herein are trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. AvantGo is a trademark of AvantGo, Inc. Epicentric Foundation Server is a trademark of Epicentric, Inc. Documentum and eRoom are trademarks of Documentum, a division of EMC Corp. FileNet is a trademark of FileNet Corporation. Lotus Notes is a trademark of Lotus Development Corporation. mySAP Enterprise Portal is a trademark of SAP AG. Oracle is a trademark of Oracle Corporation. Adobe is a trademark of Adobe Systems Incorporated. Novell is a trademark of Novell, Inc. Stellent is a trademark of Stellent, Inc. All other trademarks are the property of their respective owners.
Acknowledgments
MediaBin 8 uses Sea Dragon Ajax Code provided by Microsoft Corporation for Deep Zoom feature. (License: http:// gallery.expression.microsoft.com/site/SeadragonAjax/eula?licenseType=None)
Notice to Government End Users

If this product is acquired under the terms of a DoD contract: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of 252.227-7013. Civilian agency contract: Use, reproduction or disclosure is subject to 52.227-19 (a) through (d) and restrictions set forth in the accompanying end user agreement. Unpublished-rights reserved under the copyright laws of the United States. Autonomy, Inc., One Market Plaza, Spear Tower, Suite 1900, San Francisco, CA. 94105, US.
06 November 2012
Contents
Figures ............................................................................................................................................11 Tables ..............................................................................................................................................15 About This Document ...............................................................................................................17

Documentation Updates...............................................................................................................17 Related Documentation................................................................................................................19 Conventions .................................................................................................................................20 Notational Conventions .........................................................................................................20 Command-line Syntax Conventions ......................................................................................21 Notices ..................................................................................................................................22 Autonomy Customer Support .......................................................................................................22 Contact Autonomy........................................................................................................................23
Chapter 1 Introduction ................................................................................................................................. 25

The Autonomy Installer ................................................................................................................25 Components used by the Installer ................................................................................................26 Infrastructure Components ...................................................................................................26 Web Content Authoring .........................................................................................................27 Web Content Management ...................................................................................................27 Web Content Runtime ...........................................................................................................28 License the Products....................................................................................................................28 Web Solutions Configuration Overview ........................................................................................28 Development Server .............................................................................................................30 Runtime Server .....................................................................................................................30
Contents
Chapter 2 Installation Prerequisites ....................................................................................................... 31

TeamSite Prerequisites .............................................................................................................. 31 Server Hardware Requirements ........................................................................................... 31 Software Requirements ........................................................................................................ 31 Other Requirements ............................................................................................................. 32 Checksum File Requirement .......................................................................................... 32 Windows 2008 Requirements ........................................................................................ 33 Red Hat Enterprise Linux 6.x (64-bit Only) Requirements .............................................. 33 Patch Requirements ...................................................................................................... 34 Connect through the File System Interface .................................................................... 34 Database Information ........................................................................................................... 35 MySQL Requirement ..................................................................................................... 35 Supported Databases and Drivers ....................................................................................... 36 Pre-installation Tasks ................................................................................................................. 37 Configure OpenDeploy before Installing TeamSite ............................................................... 38 ReportCenter Prerequisites ........................................................................................................ 39 Search Prerequisites .................................................................................................................. 40 LSCS Authoring Prerequisites .................................................................................................... 40 Installation Prerequisites ...................................................................................................... 41 Abbreviations Used in the Installation Instructions ............................................................... 41 Format for Path Names and Character Encodings ............................................................... 42 Pre-Installation Tasks ........................................................................................................... 42
Chapter 3 Install TeamSite ......................................................................................................................... 43

What Is Installed? ....................................................................................................................... 43 TeamSite Components ......................................................................................................... 43 Essential Installation Information .......................................................................................... 45 Application Server ................................................................................................................ 45 Log Files .............................................................................................................................. 45 Installation Log Files ...................................................................................................... 46 TeamSite Log Files ........................................................................................................ 46 Password Syntax ................................................................................................................. 47 Required Input for TeamSite Installation ..................................................................................... 47 Install TeamSite .......................................................................................................................... 48 Run the Autonomy Installer on Linux or Solaris .................................................................... 49 Run the Autonomy Installer on Windows .............................................................................. 49 Continue the Installation for All Platforms ............................................................................. 50 Post-Installation Tasks ................................................................................................................ 76
Contents
Configure OpenDeploy after TeamSite Installation ...............................................................78 Configure LiveSite Server after TeamSite Installation ...........................................................82 Configure Targeting after TeamSite Installation ....................................................................82 TeamSite License .................................................................................................................83 To use Content Stores from a Previous TeamSite Version ...................................................83 Verify the Installation ............................................................................................................83 Verify Targeting Installation ..................................................................................................84 Recreate and Reconfigure Databases after Installation ..............................................................85 SitePublisher and LSDS .......................................................................................................85 Administration Console and CommonServices .....................................................................86 LSCS Runtime ......................................................................................................................91 Report Center and Advanced Reports ..................................................................................94 Uninstall TeamSite ......................................................................................................................95
Chapter 4 Silent Installation Options ...................................................................................................... 99

About Silent Installation ...............................................................................................................99 Selectively Run Silent Operations on Package Components ....................................................100 Run the Encryption Utility ..........................................................................................................100 Merge Multiple Silent Installation Input Files .............................................................................101 Run a Silent Installation .............................................................................................................102 Switch from Silent to UI Installation ...........................................................................................105 Run a Silent Upgrade ................................................................................................................105 Run a Silent Uninstallation ........................................................................................................106
Chapter 5 Upgrade and Migrate TeamSite .......................................................................................... 107

Upgrade Paths ..........................................................................................................................107 Files to Back Up Before Upgrading or Migrating .......................................................................108 Upgrade TeamSite on Linux, Solaris, or Windows ....................................................................108 Migrate TeamSite ......................................................................................................................119 Migration Paths ...................................................................................................................120 Additional Migration Steps ..................................................................................................121 iwutild.cfg and rewrite.conf.template .............................................................................121 SitePublisher ................................................................................................................121 Eventsubsystem ...........................................................................................................122 Non-root Support ..........................................................................................................122 Migrate Content to Support TeamSite Associations .....................................................123 Restructure Role Information ........................................................................................125 Resolve User/Group ID Information ..............................................................................126
Contents
Associate Roles with Branches .................................................................................... 126 Update Customization Items ........................................................................................ 127 Update Configuration files ............................................................................................ 128 Manage Users through the Administration User Interface ............................................ 128
Chapter 6 Configure TeamSite ............................................................................................................... 129

Configure Web Servers ............................................................................................................ 129 Run the IIS Configuration Script Manually .......................................................................... 130 Autonomy Web Server Port Number .................................................................................. 130 Configure the iw-mount Alias ............................................................................................. 131 Configure iw-mount for IIS ........................................................................................... 131 Configure iw-mount for Apache .................................................................................... 131 Configure CGI Programs .................................................................................................... 132 Enable Server-Side Include Requests ................................................................................ 132 Install the Redirector Module for IIS ............................................................................. 133 Install the Redirector Module for Apache 1.3.x ............................................................ 133 Enable Server-Side Include Requests on Apache 2.0.x or 2.2.x .................................. 135 Server-Side Includes for IHS (AIX only) ....................................................................... 136 Web Server Plug-ins and VisualPreview ...................................................................... 137 Stop and Restart the Web Server ....................................................................................... 139 Redirect NSAPI HTTPS Requests ..................................................................................... 139 Redirect to an Index Page .................................................................................................. 140 Where to Go From Here ..................................................................................................... 141 Configure TeamSite Clients ...................................................................................................... 141 Access TeamSite Using ContentCenter ............................................................................. 141 Install Local File Manager ............................................................................................ 142 Access TeamSite through the File System Interface .......................................................... 143 Mount Windows Clients ............................................................................................... 143 Create Desktop Shortcuts ............................................................................................ 144 Troubleshoot Windows Networking .............................................................................. 144 NFS Clients ................................................................................................................. 145 FTP Clients .................................................................................................................. 145 Macintosh Clients ........................................................................................................ 145 UNIX Clients ................................................................................................................ 146 Configure MediaBin Connector for Legacy MediaBin Servers .................................................. 147 Configure MediaBin Workflows .......................................................................................... 148 Load Content Files ................................................................................................................... 149 Create a Content Store ...................................................................................................... 149 Content Store Overview ............................................................................................... 150
6
Contents
Create Multiple Content Stores .....................................................................................150 View Content Stores .....................................................................................................155 Create a Subbranch ............................................................................................................157 Create a Workarea .............................................................................................................158 Populate the Initial Workarea ..............................................................................................159 Submit Files to the Staging Area .........................................................................................160 Publish an Edition ...............................................................................................................161 The ContentCenter Interfaces .............................................................................................161 Display Workareas .......................................................................................................161 Display Workarea Names .............................................................................................162 Click Workarea Names .................................................................................................163 Display Forms in the New Forms Module .....................................................................164 Display Files in the Work in Progress Module ..............................................................165 Display My Tasks .........................................................................................................166 Configure Local File Manager ......................................................................................167 Workflow CGI Tasks and ContentCenter ......................................................................167 Display Task Variables .................................................................................................168 The Get Latest Operation in ContentCenter Standard ..................................................169 Resolve Task Conflicts .................................................................................................169 Configure Submit Workflow ..........................................................................................169 Eliminate Tagging Steps in Wizards .............................................................................170 The iwui User ............................................................................................................................170
Chapter 7 Configure ReportCenter ........................................................................................................ 171

TeamSite Report Server Configuration File ...............................................................................171 Database ............................................................................................................................172 CSSDK ...............................................................................................................................172 Receiver .............................................................................................................................173 Hibernate Properties ...........................................................................................................174 DAO ....................................................................................................................................175 Reportable Extended Attributes ..........................................................................................175 Job Variables ......................................................................................................................176 Configure TeamSite ..................................................................................................................176 Configure OpenDeploy ..............................................................................................................177
Chapter 8 Install Search ............................................................................................................................ 179

Install Search ............................................................................................................................179
Contents
Uninstall Search ....................................................................................................................... 192
Chapter 9 Configure Search .................................................................................................................... 193

Configure the Index and Search Managers .............................................................................. 193 Generic Configuration ........................................................................................................ 194 Index Server Configuration ................................................................................................. 194 Search Server Configuration .............................................................................................. 199 Logging Configuration ........................................................................................................ 201 IDOL Server Configuration ................................................................................................. 201 Relocate the TeamSite Search Collection Folder ............................................................... 202 Field Mapping Configuration ..................................................................................................... 203 Configure Date Fields ........................................................................................................ 206 Example FieldMapping.xml File .......................................................................................... 207
Chapter 10 Install LiveSite Content Services Authoring ................................................................ 211

Before You Begin ..................................................................................................................... 211 Install the Authoring Server ...................................................................................................... 212 Post-Installation Tasks .............................................................................................................. 222 Upgrade LSCS ......................................................................................................................... 223
Chapter 11 Configure LiveSite Content Services Authoring......................................................... 225

Configure LSCS Sample Applications ...................................................................................... 225 Configure TeamSite ........................................................................................................... 226 Configure the LSCS Sample Application ............................................................................ 229 Remove the Files Installed by the LSCS Sample SPAR .................................................... 231 Content and Metadata Deployment .......................................................................................... 232 Deployment Process Overview .......................................................................................... 232 Phase 1Deployment Launcher ................................................................................. 233 Phase 2OpenDeploy Base Server, Receiver and Import Delivery Adapter ............... 233 Phase 3LSCS Web Service Import Resource .......................................................... 233 Phase 4OpenDeploy Base Server, Receiver and Commit Delivery Adapter ............ 233 Customize Deployments .................................................................................................... 234 Override Default Values ............................................................................................... 234 Control Comparison and Faceted Search .................................................................... 234 Fan-out Deployment .................................................................................................... 235 Administrative Tasks ................................................................................................................ 238 Reinitialize a Project Repository ......................................................................................... 238
8
Contents
Restrict Access ...................................................................................................................239 Enable Secure Communications on the Authoring Server .........................................................240 Enable Secure Communication on the OpenDeploy Base Server ......................................240 Enable HTTPS Transport on OpenDeploy Web Services .............................................240 Set up the LSCS Authoring Server Client Certificate ....................................................243 Configure the LSCS Authoring Server ..........................................................................244 Configure the Authoring Server to Access Runtime through SSL .......................................244
Chapter 12 Troubleshooting....................................................................................................................... 247

TeamSite ...................................................................................................................................247 Troubleshoot the TeamSite 7.x Installation .........................................................................248 Use TeamSite Logs to Evaluate your Installation Results .............................................248 Address Interwoven Registry Service Problems ...........................................................249 Complete an Unsuccessful Installation .........................................................................249 Installed Diagnostics ...........................................................................................................251 Solaris ..........................................................................................................................252 Windows .......................................................................................................................253 Clean or Remove the Installation Manually .........................................................................253 Clean or Remove the Installation on Linux ...................................................................253 Clean or Remove the Installation on Solaris .................................................................254 Clean or Remove the Installation on Windows .............................................................256 Make iwserver.exe 3GB Switch Aware (Windows Only) .....................................................257 Configure the Database Manually .......................................................................................258 Compile the UVFS Module .................................................................................................258 Troubleshoot the IIS Web Server ........................................................................................259 Perform Post-Installation Steps Manually ...........................................................................259 Preserve Custom Configurations for PLC ...........................................................................260 Adjust the Java Virtual Machine (JVM) Stack Size ..............................................................260 ReportCenter .............................................................................................................................261 Access the ReportCenter User Interface .............................................................................261 Generate Reports ...............................................................................................................261 Sample js-jboss-ds.xml File ................................................................................................262
Index ..............................................................................................................................................265
Contents
10
Figures
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 11
TeamSite complete installation and LiveSite Display ServicesConfiguration ........ 29 Add or Locate Common Services .............................................................................. 51 Use Common Services on another computer............................................................ 53 Select Components to Install ..................................................................................... 54 Select Base Directory for Installation......................................................................... 55 Configuration Details ................................................................................................. 56 Select the Database Type ......................................................................................... 57 Common Services Database Driver and Details ....................................................... 58 Directory for TeamSite Content Store........................................................................ 59 Stop Microsoft IIS Web Server for Installation Process ............................................. 61
Figure 10 Location of the Compiled UVFS kernel module......................................................... 60 Figure 12 Configure Microsoft IIS Web Server for use with TeamSite ...................................... 62 Figure 13 .Net Web Application for Preview .............................................................................. 63 Figure 14 Configure TeamSite Ports ......................................................................................... 64 Figure 15 TeamSite Log Directory ............................................................................................. 65 Figure 16 TeamSite mountpoint for Content Store .................................................................... 66 Figure 17 Apache httpd.conf file location................................................................................... 67 Figure 18 Apache bin directory location..................................................................................... 68 Figure 19 OpenDeploy Configuration ........................................................................................ 69 Figure 20 Database type for SitePublisher ................................................................................ 70 Figure 21 SitePublisher Database Driver Files and Details ....................................................... 71 Figure 22 LiveSite Display Services Database Driver Files and Details.................................... 72 Figure 23 Configure Application Servers screen ....................................................................... 73 Figure 24 TeamSite Reporting Database Configuration ............................................................ 74 Figure 25 Basic ReportCenter Database Configuration............................................................. 75 Figure 26 Installation Type......................................................................................................... 96 Figure 27 Select Components to Uninstall................................................................................. 97 Figure 28 Add or Locate Common Services ............................................................................ 109 Figure 29 Use Common Services on Another Computer......................................................... 111 Figure 30 Upgrade Component Selection................................................................................ 112
11
Figures
Figure 31 Database Type for Common Services .....................................................................113 Figure 32 Common Services Database Configuration .............................................................114 Figure 33 OpenDeploy Admin Username and Web Services connection information .............116 Figure 34 Database type for SitePublisher...............................................................................117 Figure 35 TeamSite Reporting Database Configuration ..........................................................118 Figure 36 ContentCenter Standard Content module................................................................141 Figure 37 Content Store ..........................................................................................................155 Figure 38 Content Store Properties .........................................................................................156 Figure 39 Content Store Main branch .....................................................................................157 Figure 40 ContentCenter Standard New Forms module ..........................................................163 Figure 41 Non-TeamSite browser directory list .......................................................................164 Figure 42 ContentCenter Standard New Forms module ..........................................................165 Figure 43 Files in ContentCenter Standard Work In Progress module ....................................166 Figure 44 ContentCenter Standard Tasks module...................................................................167 Figure 45 ContentCenter Standard Task Details .....................................................................168 Figure 46 Component Selection...............................................................................................180 Figure 47 Select Base Directory for Installation .......................................................................181 Figure 48 TeamSite Server Host..............................................................................................182 Figure 49 Search Server Port...................................................................................................183 Figure 50 Index Server Port .....................................................................................................184 Figure 51 Event Subsystem JMS Server Port..........................................................................185 Figure 52 Get IDOL Server Ports .............................................................................................186 Figure 53 Get IDOL Category Server Ports .............................................................................187 Figure 54 Get IDOL Community Server Ports..........................................................................188 Figure 55 Get Agent Store Server Ports ..................................................................................189 Figure 56 Get TeamSite Connector Server Ports ....................................................................190 Figure 57 Get Connector Framework Server Ports..................................................................191 Figure 58 Component selection ...............................................................................................213 Figure 59 Base directory for installation ...................................................................................214 Figure 60 OpenDeploy configuration........................................................................................215 Figure 61 Configuration details ................................................................................................216 Figure 62 JDK configuration.....................................................................................................217 Figure 63 TeamSite Home configuration..................................................................................218 Figure 64 Configure TeamSite User.........................................................................................218 Figure 65 Destination Node and Area ......................................................................................219 Figure 66 Preview configuration...............................................................................................220 Figure 67 Preview configuration (IDOL details)........................................................................221 Figure 68 Preview (targeting) configuration .............................................................................222 Figure 69 Metadata for sample data ........................................................................................227
12
Figures
Figure 70 Sample application .................................................................................................. 229 Figure 71 Deploying sample content ....................................................................................... 230 Figure 72 Explore a sample application................................................................................... 231 Figure 73 LiveSite Content Services deployment process ...................................................... 234
13
Figures
14
Tables
Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12
Supported databases and required drivers................................................................. 36 Authoring environment system requirements ............................................................. 41 Abbreviations used in the installation instructions ...................................................... 41 TeamSite installation locations ................................................................................... 44 Information required for TeamSite installation ............................................................ 47 Using the Common Services option............................................................................ 52 Configuration parameters ........................................................................................... 92 Use the Common Services options........................................................................... 110 Upgrade and migration paths.................................................................................... 120 File status and display in ContentCenter Standard................................................... 165 fieldName and fieldStorage entries........................................................................... 205 Interpretation of time and date patterns .................................................................... 207
15
Tables
16
About This Document
This guide describes the procedures for installing, uninstalling, upgrading, and licensing the Web Solutions authoring components. In addition, it describes the initial, one-time configuration of all related system resources. This guide is primarily for Web server administrators and system administrators.
When installing on UNIX platforms, users of this guide should be familiar with basic UNIX commands and be able to use a text editor such as emacs or vi. Many of the operations described in this guide require root access to the system on which you are installing the TeamSite Content Server. If you do not have root access, contact your UNIX system administrator. When installing on Windows platforms, you should be familiar with Internet information Server (IIS) Web servers and with basic Windows operations such as adding users and modifying Access Control Lists (ACL).
The topics in this section include:

Documentation Updates Related Documentation Conventions Autonomy Customer Support Contact Autonomy
Documentation Updates
The information in this document is current as of Web Solutions Authoring Components version 7.3. The content was last modified 5 November 2012. You can retrieve the most current product documentation from Autonomys Knowledge Base on the Customer Support Site.
17
About This Document
A document in the Knowledge Base displays a version number in its name, such as IDOL Server 7.5 Administration Guide. The version number applies to the product that the document describes. The document may also have a revision number in its name, such as IDOL Server 7.5 Administration Guide Revision 6. The revision number applies to the document and indicates that there were revisions to the document since its original release. It is recommended that you periodically check the Knowledge Base for revisions to documents for the products your enterprise is using. To access Autonomy documentation 1. Go to the Autonomy Customer Support site at https://customers.autonomy.com 2. Click Login. 3. Enter the login credentials that were given to you, and then click Submit. The Knowledge Base Search page opens. 4. In the Search box, type a search term or phrase. To browse the Knowledge Base using a navigation tree only, leave the Search box empty. 5. Ensure the Documentation check box is selected. 6. Click Search. Documents that match the query display in a results list. 7. To refine the results list, select one or more of the categories in the Filter By pane. You can restrict results by
Product Group. Filters the list by product suite or division. For example,
you could retrieve documents related to the iManage, IDOL, Virage or KeyView product suites.
Product. Filters the list by product. For example, you could retrieve
documents related to IDOL Server, Virage Videologger, or KeyView Filter.

Component. Filters the list by a products components. For example, you
could retrieve documents related to the Content or Category component in IDOL.

Version. Filters the list by product or component version number. Type. Filters the list by document format. For example, you could retrieve
documents in PDF or HTML format. Guides are typically provided in both PDF and HTML format. 8. To open a document, click its title in the results list. To download a PDF version of a guide, open the PDF version, click the Save icon in the PDF reader, and save the PDF to another location.
18
Related Documentation
Related Documentation
The following documents provide more details on Web Solutions:

ContentCenter Professional User Guide LiveSite Content Services Technical Reference Guide OpenDeploy Installation Guide OpenDeploy Administration Guide TeamSite Administration Guide TeamSite Release Notes TeamSite Site Developer Guide TeamSite User Guide TeamSite User Interface Customization Guide Workflow Modeler User Guide Web Solutions Runtime Components Installation Guide Web Solutions Installation Planning Guide
19
About This Document
Conventions
The following conventions are used in this document.
Notational Conventions
This document uses the following conventions. Convention
Bold
Usage
User-interface elements such as a menu item or button. For example: Click Cancel to halt the operation.
Italics
Document titles and new terms. For example: For more information, see the IDOL Server Administration Guide. An action command is a request, such as a query or indexing instruction, sent to IDOL Server.
monospace font
File names, paths, and code. For example: The FileSystemConnector.cfg file is installed in C:\Program Files\FileSystemConnector\.
monospace bold
Data typed by the user. For example: Type run at the command prompt. In the User Name field, type Admin.
monospace italics
Replaceable strings in file paths and code. For example: user UserName
20
Conventions
Command-line Syntax Conventions

This document uses the following command-line syntax conventions. Convention
[ optional ]
Usage
Brackets describe optional syntax. For example: [ -create ]
Bars indicate either | or choices. For example: [ option1 ] | [ option2 ] In this example, you must choose between option1 and option2.
{ required }
Braces describe required syntax in which you have a choice and that at least one choice is required. For example: { [ option1 ] [ option2 ] } In this example, you must choose option1, option2, or both options.
required
Absence of braces or brackets indicates required syntax in which there is no choice; you must type the required syntax element. Italics specify items to be replaced by actual values. For example: -merge filename1 (In some documents, angle brackets are used to denote these items.)
variable <variable>
...
Ellipses indicate repetition of the same pattern. For example: -merge filename1, filename2 [, filename3 ... ] where the ellipses specify, filename4, and so on.
The use of punctuationsuch as single and double quotes, commas, periods indicates actual syntax; it is not part of the syntax definition.
21
About This Document
Notices
This document uses the following notices:
CAUTION A caution indicates an action can result in the loss of data.
IMPORTANT An important note provides information that is essential to completing a task.
NOTE A note provides information that emphasizes or supplements important points of the main text. A note supplies information that may apply only in special casesfor example, memory limitations, equipment configurations, or details that apply to specific versions of the software.
TIP A tip provides additional information that makes a task easier or more productive.
Autonomy Customer Support

Autonomy Customer Support provides prompt and accurate support to help you quickly and effectively resolve any issue you may encounter while using Autonomy products. Support services include access to the Customer Support Site (CSS) for online answers, expertise-based service by Autonomy support engineers, and software maintenance to ensure you have the most up-to-date technology. To access the Customer Support Site, go to https://customers.autonomy.com The Customer Support Site includes:
Knowledge Base: The CSS contains an extensive library of end user documentation, FAQs, and technical articles that is easy to navigate and search.
22
Contact Autonomy
Case Center: The Case Center is a central location to create, monitor, and manage all your cases that are open with technical support. Download Center: Products and product updates can be downloaded and requested from the Download Center. Resource Center: Other helpful resources appropriate for your product.
To contact Autonomy Customer Support by e-mail or phone, go to http://www.autonomy.com/content/Services/Support/index.en.html
Contact Autonomy
For general information about Autonomy, contact one of the following locations: Europe and Worldwide
E-mail: autonomy@autonomy.com Telephone: +44 (0) 1223 448 000 Fax: +44 (0) 1223 448 001 Autonomy Corporation plc Cambridge Business Park Cowley Rd. Cambridge CB4 0WZ United Kingdom
North and South America

E-mail: autonomy@autonomy.com Telephone: 1 415 243 9955 Fax: 1 415 243 9984 Autonomy, Inc. One Market Plaza Spear Tower, Suite 1900 San Francisco, CA 94105 USA
23
About This Document
24
CHAPTER 1
Introduction
This section introduces the Autonomy Installation program and Web Solutions Components configuration.

The Autonomy Installer Components used by the Installer License the Products Web Solutions Configuration Overview
The Autonomy Installer

The Autonomy Installer facilitates installing, reinstalling, upgrading, and uninstalling various products within the Autonomy Web Content Management solution. This Installer simplifies the overall installation process and provides a robust, optimal, and user-friendly installation experience.
25
Chapter 1 Introduction
NOTE There are several options for installing Web Solutions Authoring Components, so you may not need to use this entire document. TeamSite only TeamSite and SitePublisher only TeamSite with SitePublisher and LiveSite, and optionally with Targeting ReportCenter with one of the other options
The Autonomy Installer differs from the traditional product installers in that you can point the installer to a software package (typically an iwpkg file). This Installer can detect the components in a package.

Any Autonomy product, module, service, or other entity that is installed as a self-contained unit by the installation program is called a component. A product can be made up of one or more components.
The installation program is an interactive, GUI-based method. It does not support console mode installation.
Components used by the Installer

The following components leverage the new installation framework:

Infrastructure Components Web Content Authoring Web Content Management Web Content Runtime
Infrastructure Components
The infrastructure components are used by all components, except the runtime components.The infrastructure components are:

Foundation Libraries. The infrastructure component that contains JDK and Ant. There is no dependent component for Foundation Libraries. Application Container. The infrastructure component that installs JBoss and depends upon Foundation Libraries component.
26
Components used by the Installer
Common Services. The infrastructure component used by ReportCenter, TeamSite, and Administration Console for authentication and configuration information. Many or all of the functionality of various components fail without this component. Hence, after you install this component, verify that it installed successfully and works correctly. Common Services depends upon Application Container component. Common Services Client. The infrastructure client component used by all the components to communicate with Common Services. Common Services Client is installed automatically when you install Common Services.
Web Content Authoring

LiveSite Content Services Authoring is the Web content authoring component that installs LiveSite Content Services Authoring and depends on the TeamSite component.
Web Content Management

The following components belong to Web Content Management:
Autonomy Administration Console. The Web content management component that installs the Administration Console for unified administration. Administration Console depends on Common Services Client component and TeamSite. Autonomy TeamSite UI Framework. Autonomy TeamSite User Interface. (Requires TeamSite UI Framework.) Autonomy TeamSite WorkFlow Modeler. Define workflow models, which are then automated by TeamSite. Workflows encompass the procedures, tasks, people, and rules that define business practices and processes within an organization. CSSDK Soap Services. CSSDK SOAP server is an optional component. CSSDK SOAP services depends on JBoss, IR Client, and TeamSite, however, TeamSite can reside on a remote machine. Report Center. The Web content management component that installs Advanced Reporting Functionality. ReportCenter depends on Common Services Client and Administration Console components. TeamSite. The Web content management component that installs TeamSite, SitePublisher and Targeting. TeamSite depends on Common Services Client component and Targeting depends on LiveSite Content Services and LiveSite Display Services. TeamSite Search
27
Web Content Runtime
LiveSite Display Services is the runtime component that installs LiveSite Runtime and LiveSite Display Services (LSDS). LSDS depends on LSCS Runtime when Targeting is used. LiveSite Content Services is the runtime component that installs LiveSite Content Services. Targeting depends on LiveSite Content Services for rules.
NOTE To install the Web Solutions runtime components, refer to the Web Solutions Runtime Components Installation Guide.
License the Products

The Autonomy installer does not prompt for a license key during the installation process and lets the user install the components in the available product packages. While the users can install TeamSite without a valid license key during the installation process, Autonomy recommends to provision your valid TeamSite license key immediately after the installation is complete. Upon installation, TeamSite Server can run for 48 hours after which it requires a valid license. Depending on your product entitlements, if you wish to use the SitePublisher, Targeting, LiveSite Content Services (both authoring and runtime), and ReportCenter functionality, ensure that while generating your TeamSite license the respective feature options are enabled in your license key.
Web Solutions Configuration Overview

Figure 1 shows a typical configuration set up of the complete suite of TeamSite and LiveSite Display Services (runtime environment).
28
Web Solutions Configuration Overview
Figure 1 TeamSite complete installation and LiveSite Display Services Configuration
TeamSite provides a development environment where Web sites are created. It is designed to work with LiveSite Display Services to render those sites in a runtime environment. This design employs the following parts:

TeamSite development server LiveSite Display Services LiveSite Content Services (Runtime) Database management system (DBMS)
The development server is the platform where SitePublisher components, templates, and pages are created and where Web sites are designed. The runtime server for a Web site is the platform where the LiveSite Display Services is located. Autonomy recommends running separate systems for SitePublisher (development) and LiveSite Display Services (runtime environment) (and a requirement in most business environments), but it is possible to install both on the same system. The DBMS can reside on any system as long as both SitePublisher and LiveSite Display Services have access to the databases.
29
Development Server
The development server includes the followings components:

TeamSite/SitePublisher. SitePublisher is part of TeamSite. SitePublisher provides a development environment where Web sites are created. OpenDeploy (Base Server). OpenDeploy Base Server is used to copy files from the development server to the runtime environment server. Refer to the OpenDeploy Installation Guide for installation instructions. Install the following Base Server component: Base package (including DataDeploy) After installing OpenDeploy Base Server, but before installing TeamSite, configure OpenDeploy for TeamSite (see Required Input for TeamSite Installation on page 47).
LiveSite Content Services (Authoring). The Targeting rules reside in LiveSite Content Services for Authoring.
Runtime Server
The runtime server includes the followings components:

OpenDeploy (Receiver). OpenDeploy Receiver is used to manage files copied from the development server. LiveSite Display Services. LiveSite Display Services provides a runtime environment to implement sites created on the development server. LiveSite Content Services (Runtime). LiveSite Content Services (Runtime) connects the Website presentation layer (ASP, JSP, AJAX, portal, and so on) to a runtime view of the content and metadata managed in TeamSite. Java 2 Standard Edition Java Development Kit (J2SE JDK). LiveSite requires the J2SE JDK to support SitePublisher components at run time. Web Application Server. LiveSite requires a Web application server at run time.
30
CHAPTER 2
Installation Prerequisites
This section describes the installation prerequisites that must be met before you install the Web Solutions Authoring components.

TeamSite Prerequisites Pre-installation Tasks ReportCenter Prerequisites Search Prerequisites LSCS Authoring Prerequisites
TeamSite Prerequisites
Before you install TeamSite, ensure that you meet these requirements.
Server Hardware Requirements

Refer to the Web Solutions Installation Planning Guide and the TeamSite Release Notes for details about hardware requirements.
Software Requirements
Refer to the TeamSite Release Notes for details about software requirements and TeamSite compatibility with other Autonomy products.
31
Chapter 2 Installation Prerequisites
Other Requirements
You must also meet the following additional requirements (other than hardware and software requirements).

See Web Solutions Configuration Overview on page 28 for information on configuring the required software products for TeamSite. See Required Input for TeamSite Installation on page 47 for information on installing the software required for TeamSite. Ensure that your system has reg.exe program which is used to add or modify Registry keys. TeamSite requires reg.exe in the system path. If unavailable, you can download it from the Microsoft site and copy it to the system32 folder. If you plan to use DataDeploy during PLC operations, the DataDeploy user must have the Create Table permission. The installed components must have the following database permissions.
read and write access create table create and update index
A separate database is required for ReportCenter.
Checksum File Requirement

Installation files can become corrupt, especially when downloaded over FTP, which can lead to installation failures. For Windows installations, the TeamSite installer validates the installation package to ensure that the files are not corrupt. For Linux installations, you can manually check that the files are not corrupt (see Recommendation for UNIXManual Checksum Comparison on page 32). For the validation to work on Windows, you must download the .md5 files provided with the installer .iwpkg files and place them in the same directory. If you do not download the .md5 files, the installer terminates and generates an error message. To validate the files on Linux, you must also download the .md5 files. It does not matter where you save them. Recommendation for UNIXManual Checksum Comparison To check that the installation files are not corrupt on UNIX systems, you must generate an md5 file and compare it to the downloaded .md5 file. If there are any differences, the installation files are probably corrupted.
32
To validate installation files on UNIX 1. After downloading the product installation packages, run one of the following commands to generate an md5 file.
Linux: run md5sum <package filename> Solaris: run digest -a md5 <package filename>
2. Compare the generated checksum to the <package filename>.md5sum file that you downloaded. 3. If the checksums do not match, retry the download.
Windows 2008 Requirements

Due to an issue on Windows 2008 systems that run IIS 7, a TeamSite installation may be unsuccessful. Before you install TeamSite, you must add an IIS Server Role and set the following options during setup. To add an IIS Server Role and set the setup options 1. On the Role Services page, under Common HTTP Features, select the following options:
Static Content Default Document Directory Browsing HTTP Errors HTTP Redirection
2. Under Application Development, select ASP.NET. 3. Under Security, select Windows Authentication. 4. Restart Windows for the changes to take effect.
Red Hat Enterprise Linux 6.x (64-bit Only) Requirements

Teamsite requires 32-bit versions of the following packages.

compat-libstdc++-33 keyutils-libs krb5-libs libXi libXtst libcom_err
33
libicu libselinux libstdc++ libuuid ncurses-libs nspr nss nss-util openssl098e pam zlib
Patch Requirements
On Solaris 10, ensure that patch 118833 with a revision number 18 or later is installed. The installer detects this patch level and proceeds with installation if the minimum kernel patch is available. If this patch is not installed, the installer displays a warning and quits the installation. the x86 version of Solaris requires Solaris 10 Update 7 or later, instead of the patch.
Connect through the File System Interface

To connect to TeamSite using the file system interface, Windows users must have a network connection and the ability to connect to the TeamSite-shared IFS volume through their local domains. Linux or Solaris users must have a network connection and the ability to interact with a networked file system (for example, FTP, NFS, PCNFS, FTP client, Windows networking). Before installing and configuring any of these protocols, you should be familiar with them to perform basic configuration and start-up procedures. For more information, see Access TeamSite through the File System Interface on page 143.
34
Database Information
TeamSite requires the use of a Database Management System (DBMS). Common Services, TeamSite, SitePublisher, TeamSite Reporting, and LiveSite support the following DBMS products.
Oracle and Oracle Real Application Clusters (RAC). Refer to the Oracle documentation for installation instructions and general information. (http:// www.oracle.com/technology/documentation/index.html and http:// www.oracle.com/technetwork/database/clustering/overview/index.html). Microsoft SQL Server. Refer to the Microsoft SQL Server documentation for installation instructions. (http://www.microsoft.com/sql/techinfo/books.mspx). MySQL. Refer to the MySQL documentation for installation instructions (http://dev.mysql.com/doc/) IBM DB2. Refer to the IBM DB2 documentation for installation instructions. (http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp).
In addition to having a DBMS available, you must download the appropriate drivers for the database. See Supported Databases and Drivers on page 36 for a list of the required driver files.
NOTE Ensure that the database drivers are copied locally. Do not access database drivers from mounted disk drives. The mounted disk drives may be disconnected after restart and the Installer cannot access the file from the disconnected drive during the post-start configuration.
MySQL Requirement
When executing on Linux against MySQL, you must modify the configuration file before you create the TeamSite database. To modify the MySQL configuration file 1. Open the my.cnf configuration file. 2. Set the following parameter: lower_case_table_names = 1 3. Restart the MySQL services.
35
Supported Databases and Drivers

This section provides details about the supported databases and required database drivers for:

CommonServices TeamSite SitePublisher LiveSite TeamSite Reporting ReportCenter
Refer to the following links for information about drivers:

Oracle. http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/ index.html Microsoft SQL Server. http://msdn.microsoft.com/hi-in/data/ aa937724(en-us).aspx MySQL. http://dev.mysql.com/downloads/connector/ IBM DB2. http://www.ibm.com/support/us/en/ Table 1 Supported databases and required drivers
Database Management System One of the following DBMS: Oracle SQL Server DB2 MySQL Database Driver Files Oracle 10g and 10g RAC, 11g and 11g RAC SQL Server 2008 and 2008 R2 SQL Server 2005 DB2 8.2, 9.0, 9.5 MySQL 5.x ojdbc14.jar sqljdbc4.jar sqljdbc.jar db2jcc_license_cu.jar and db2jcc.jar mysql-connector-java-5.1.6-bin.jar 10g and 10g RAC, 11g and 11g RAC 2005, 2008, 2008 R2 8.2, 9.0, 9.5 5.x
36
Pre-installation Tasks
Pre-installation Tasks
If you plan to perform a complete installation (TeamSite, LiveSite, and ReportCenter), perform the following tasks before you install TeamSite. To perform the pre-installation tasks for a complete installation 1. In the DBMS, create databases for:
Common Services EventSubSystem TeamSite Reporting SitePublisher (development environment)
You can have a single database for all the subsystems mentioned above except ReportCenter. See Supported Databases and Drivers on page 36 for information on supported databases and the required drivers. 2. Create databases for the following components:
TeamSite LiveSite Display Services Runtime. Refer to the Web Solutions Runtime
Components Installation Guide for more information.

LiveSite Content Services Authoring LiveSite Content Services Runtime. Refer to the Web Solutions Runtime
Components Installation Guide for more information.

NOTE Do not create any tables in the databases, as the installer automatically creates the schema and populates the tables. The databases are independent and can be on separate systems, and the database names can be of your choice.
3. If you use DB2 v8.x or later to work with SitePublisher:

Navigate to the folders od-home/drivers and od-home/userlib on
the development server.

Rename the files db2java_72_sol.zip and db2java_72_nt.zip to
any other name.
37
4. Install OpenDeploy Base server (including DataDeploy) on the development server. It is no longer necessary to install OpenDeploy Admin for OpenDeploy Base Server co-located with TeamSite. In this case, CSF is not used for authentication, instead the authentication is done using the CSSDK.
NOTE The Autonomy Installation program does not include the installation of OpenDeploy. Install OpenDeploy using its specific installation program.
5. Configure OpenDeploy. See Configure OpenDeploy before Installing TeamSite on page 38.
NOTE While Autonomy recommends you install OpenDeploy prior to installing TeamSite, OpenDeploy can be installed after installing TeamSite. (See Configure OpenDeploy after TeamSite Installation on page 78).
Configure OpenDeploy before Installing TeamSite

Before installing TeamSite, perform the next procedure on the development server to configure OpenDeploy. To configure OpenDeploy on the development server before installing TeamSite 1. Add an OpenDeploy user called livesite-od and assign the master role to that user. (Refer to the sections about roles and authorization in the OpenDeploy Administration Guide.) Windows requires the form domain-name\\livesite-od, and UNIX requires the form livesite-od. 2. Configure the OpenDeploy Web services, as described in the following file: od-home/websvc/README_OD_WEB_SERVICE
Ignore step 1 (passphrase copy) in the README_OD_WEB_SERVICE file
because this step is done by the SitePublisher installer.

In od-home/etc/odbase.xml, uncomment the following
<databaseDeployment> and <webServices> sections and type the appropriate host name:
<databaseDeployment> <standalone enabled="yes"/> <das enabled="no"/> </databaseDeployment>
38
ReportCenter Prerequisites
<webServices enabled="yes"> <httpTransport port="port_number" host="hostname"> </httpTransport> </webServices>
For example, the entry for the OD Server running on the hostname odserver on port 9273 is as follows: <httpTransport port="9273" host="ODSERVER">
NOTE SitePublisher does not need DAS. Autonomy recommends that you set the value of das enabled to no, unless you use it for other purposes.
3. Restart the OpenDeploy services. (Refer to the section about starting OpenDeploy in the OpenDeploy Administration Guide.) 4. Access the following URL to verify that the configuration is working:
http://hostname:port_number/iw/services/cd/1.1/
opendeployservice where port_number is the value specified for the parameter httpTransport port in the WebServices element in od-home/ etc/odbase.xml.
ReportCenter Prerequisites
ReportCenter must be installed separately and not while installing TeamSite/ Administration Console. Run the installer separately to install ReportCenter. Before installing ReportCenter, ensure that the following prerequisites are met:
License key When you purchase ReportCenter, you need to contact Autonomy Customer Support (https://customers.autonomy.com) for license key. You will receive an e-mail message with the ReportCenter license key. Locate this e-mail or contact Autonomy Customer Support prior to attempting to install ReportCenter if you have questions regarding the license key. Copy the license file, TS.lic, to the ts-home/etc folder where TeamSite is installed. Restart the TeamSite server.
TeamSite/Administration Console and ReportCenter:

are installed on different systems
39
ReportCenter is dependent on TeamSite and Administration Console, but it must be installed on a different server than that of TeamSite and Administration Console.
have different database schemas
Availability of a database server. The ReportCenter installer configures ReportCenter against the following databases:
Oracle Microsoft SQL IBM DB2 MySQL
See Supported Databases and Drivers on page 36 for information on supported databases and the required database drivers.
Search Prerequisites
TeamSite Search is installed as a separate module from TeamSite. If you are installing Search on a different system from TeamSite, TeamSite must be installed and available prior to installing Search. If you choose to install Search on the same system as TeamSite, 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 detects any problems if you attempt to configure Search to use a port already used by TeamSite.
LSCS Authoring Prerequisites

The next sections provide information you need before installing LSCS. This includes details on planning your configuration, installation prerequisites (including system requirements), and a table of the abbreviations used in the installation instructions, and the required format for path names and character encodings.
NOTE If a preview instance of LSCS is to be installed in the authoring environment, it requires a similar configuration to the runtime environment.
40
LSCS Authoring Prerequisites
Installation Prerequisites
Table 2 lists the hardware and software that must be available prior to installation and operation of LSCS. Table 2 Authoring environment system requirements Authoring Environment
Processor Multicore Intel processor running at 2 Ghz (minimum) or Sun UltraSPARC processor running 1 Ghz (minimum) Operating System Microsoft Windows Server 2003, Windows 2008 or Sun Solaris 10, Solaris 10 SPARC 64 bit, Solaris 10 x86 64 bit or RedHat Enterprise Linux 5 Available Memory Disk Space Java Virtual Machine Java Servlet Container TeamSite OpenDeploy 3 GB (minimum) 100 MB n/a n/a
TeamSite VersionNumber
OpenDeploy VersionNumber Base Server
Abbreviations Used in the Installation Instructions

This book uses the abbreviations outlined in Table 3. Table 3 Abbreviations used in the installation instructions Abbreviation
iw-home ts-home od-home lscsauth-home ls-home auth-host
Meaning
Interwoven directory (for example, C:\Interwoven\) TeamSite home directory (for example, C:\Program Files\Interwoven\TeamSite) OpenDeploy home directory (for example, C:\ Interwoven\OpenDeployNG) LiveSite Content Services home directory (for example, C:\ Interwoven\LiveSiteCSAuth) LiveSite Display Services home directory (for example, C:\ Interwoven\LiveSiteDisplayServices) The DNS hostname of authoring server.
41
Table 3 Abbreviations used in the installation instructions (continued) Abbreviation

auth-port auth-context tomcat-home
Meaning
The TCP port on which the Preview Java Servlet Container is running. The Servlet Context on which the LSCS Preview Web Service is installed. Apache Tomcat Home Directory (e.g. C:\Program Files\Apache\apache-tomcat-6.0.18)
Format for Path Names and Character Encodings

With the exception of command scripts, all configuration files described in this chapter require file system paths to be entered using the forward slash ('/') as the directory separator on all operating systems, including Microsoft Windows-based operating systems.
NOTE Do not use the Microsoft Windows path separator ('\') in property files.
In addition, note that these files are encoded using the ISO-8859-1 (ASCII) encoding. Unicode characters must be entered numerically using Java properties files conventions (\u followed by the four digit hexadecimal Unicode value). For example, the directory C:\donnes\2011 must be entered as C:/donn\u00e9es/2011.
Pre-Installation Tasks
Before you start the installation, ensure that all software listed in the Authoring Environment column of Table 2 on page 41 is installed and available.
42
CHAPTER 3
Install TeamSite
This section describes the process to install and uninstall TeamSite.

What Is Installed? Required Input for TeamSite Installation Install TeamSite Post-Installation Tasks Recreate and Reconfigure Databases after Installation Uninstall TeamSite
What Is Installed?
The next sections briefly introduce some of the major components and files that are installed with TeamSite. The inclusion or location of many of these components differs from previous versions of TeamSite.
TeamSite Components
The following components and their supporting files install during the TeamSite installation.

Foundation Libraries Common Services Client
43
Chapter 3 Install TeamSite
Common Services Application Container TeamSite
By default, TeamSite is installed in the locations shown in Table 4 (you can select alternative locations for some of these files during installation). Table 4 TeamSite installation locations Default Directory
/usr/Interwoven/ TeamSite (Linux, Solaris) C:\Interwoven\TeamSite (Windows)
Contents
Default location of TeamSite program files. The location of this directory can be changed during the installation. This directory is referred to throughout this guide as iw-home. 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 guide as iw-home. NOTE The TeamSite installation defaults to the system root drive. In this example, C:\ is used. NOTE In Windows, the location of the TeamSite directory must not contain any spaces.
/iw-store (Linux, Solaris) C:\iw-store (Windows)
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 (refer to the TeamSite Command-Line Tool Reference Guide). NOTE The contents of this directory should never be edited by hand in any way. Tampering with this directory can irreparably corrupt the data stored in TeamSite.
/iwserver (Linux)
Local file system mount projection directory. Clients mount to this directory to access content files. No actual data is stored in this directory, and its location cannot be changed. NFS server mount point. 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 aliases virtual directories must be updated to reflect this. NFS server mount point. This is a noncaching alias used by the Web server. The location of this directory can be changed; however, the Web server alias must be updated to reflect this change.
/iwmnt (Linux) Y:\ (Windows)
/.iwmnt (Linux)
44
What Is Installed?
Table 4 TeamSite installation locations (continued) Default Directory

/etc/apache (Linux)
Contents
Default location of the httpd.conf file. If you use Apache as your content Web Server, you must modify your Apache httpd.conf file and the installer targets the default location. You can also choose the right location if different from the above. Default location of the Apache bin directory. If you use Apache as your content Web Server, the TeamSite installation program must know the location of your Apache bin directory. You can also choose the right location if different from the above. Directory for managing all Autonomy Interwoven software on the system. Do not alter, move, or remove this directory. It is required for future upgrades and full installations.
/etc/apache/bin (Linux)
/usr/Interwoven/ iwinstall (Linux, Solaris) C:\Interwoven\ iwinstall (Windows)
Essential Installation Information

The usr/Interwoven/iwinstall directory in Linux and the Interwoven\iwinstall directory in Windows contains essential metadata about the currently installed components. If you alter any of this information, future upgrades or full installations could fail. Moreover, the software currently installed on the system could also fail. For this reason, Autonomy highly recommends that you not alter or delete any files in the aforementioned directories.
Application Server
The JBoss application server is included with TeamSite and is installed when you perform an installation as described in Install TeamSite on page 48.
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 Autonomy products that are installed Monitor the TeamSite Content Server and UIs
These files are described in the sections that follow.
45
Installation Log Files

The installation log files contains the logs for all the components and are created one level up from the TeamSite directory as follows:

Linux/Solaris: /iwinstall/logs Windows: \iwinstall\logs
For example, if you accepted the default installation directory (C:\Interwoven\ ) in Windows, the installer.log file is placed in the C:\Interwoven\ iwinstall\logs directory:
NOTE The installation log file are temporarily located in the /tmp (or c:\tmp) folder until all the components are copied to the disk.
TeamSite Log Files

These text-format files log activities performed by the TeamSite Content Server and UIs. The default location of the files is:

Linux/Solaris: /Interwoven/TeamSite/local/logs Windows: \Interwoven\TeamSite\local\logs
The log files are:

cssdk_soap.log eventsubd_err.log eventsubd_out.log iwevents.log iwserver.log iwtrace.log iwutild.log iwutild_cmdout.log tsreport.log tsreport_err.log tsreport_out.log
The iwui directory can include several additional log files. Refer to the TeamSite Administration Guide for more information about these log files.
46
Required Input for TeamSite Installation
Password Syntax
The TeamSite installer cannot parse specified password strings containing more than one dollar sign ($). For example, if you specify the database password in Step 12 on page 58 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.
Required Input for TeamSite Installation

Table 5 describes the information for which you are prompted during TeamSite installation. Table 5 Information required for TeamSite installation Information
Location of TeamSite program files Location of Content Store TeamSite ports
Step
Step 8 on page 55 Step 13 on page 60 Step 19 on page 63
Default Provided?
Yes Yes Yes
Notes
Referred to as ts-home throughout documentation.
Includes ports used by Autonomy Interwoven Web Daemon, JMS server, and the Utility Daemon HTTP and HTTPS.
Location of TeamSite log files TeamSite mount point Web server selection Location of Apache configuration file Location of Apache bin directory
Step 20 on page 65 Step 21 on page 66 Step 22 on page 66 Step 23 on page 67 Step 24 on page 68
Yes Yes Yes Yes Yes Choices are Apache or Other. Required only if you selected Apache in the previous step. Required only if you selected Apache earlier.
47
Table 5 Information required for TeamSite installation (continued) Information

SitePublisher database information: database driver location, server name, listen port, database name, administrator name, and administrator password LiveSite Display Services database information: database driver location, server name, listen port, database name, administrator name, and administrator password TeamSite Reporting database information: database driver location, server name, listen port, database name, administrator name, and administrator password
Step
Step 27 on page 70
Default Provided?
Yes
Notes
Pre-populated based on the values entered during the Common Services database configuration.
Step 28 on page 71
Yes
Step 32 on page 73
Yes
Install TeamSite
You can use the platform-specific Autonomy Installer to install TeamSite on Linux, Solaris, or Windows platforms. The installation program can be run with or without a GUI. Before installing, ensure that your system satisfies the hardware and software requirements described in the TeamSite Release Notes, and that you meet the prerequisites described in TeamSite Prerequisites on page 31. For installation procedures:

see Run the Autonomy Installer on Linux or Solaris on page 49 for Linux see Run the Autonomy Installer on Windows on page 49 for Windows see Silent Installation Options on page 99 for instructions on how to install without a GUI
IMPORTANT Disable all virus scanners before launching the TeamSite installer.
48
Install TeamSite
Run the Autonomy Installer on Linux or Solaris

This section describes how to install TeamSite on Linux or Solaris. In Linux and Solaris, run the TeamSite build in the terminal and continue the installation in the graphical mode. To install without a GUI, see Silent Installation Options on page 99. To install TeamSite on your Linux or Solaris server 1. Log in as root on the system where you want to install the TeamSite server. You can also use sudo su - to gain root access when installing TeamSite. Sudo users require full root permissions to install TeamSite. 2. If you are installing from a CD or from the Autonomy download site, copy IWOVInstaller-Platform-VersionNumber.bin and IWOVTeamSite-Platform-VersionNumber.iwpkg files to a temporary directory on a local drive. Ensure that you only include the .iwpkg and .bin files from the current release in the folder. 3. cd to the directory that has the installer and run it as follows:
./IWOVInstaller-Platform-VersionNumber.bin
4. The installer opens. See Continue the Installation for All Platforms on page 50 and continue the installation procedure from there.
Run the Autonomy Installer on Windows

This section describes how to install TeamSite on Windows. To install TeamSite on your Windows server 1. Log in as Administrator on the system where you want to install the TeamSite server. 2. If you install from a CD, insert the TeamSite CD and browse to the top-level directory. If you install from the Autonomy download site, copy IWOVInstaller-Windows-VersionNumber.exe and IWOVTeamSite-Windows-VersionNumber.iwpkg files to a temporary directory on a local drive. Ensure that you only include the .iwpkg and .exe files from the current release in the folder.
49
3. Double-click IWOVInstaller-Windows-VersionNumber.exe. The installer opens. See Continue the Installation for All Platforms on page 50 and continue the installation procedure from there.
Continue the Installation for All Platforms

During the installation, you must specify several databases. Remember the following guidelines.

All Authoring databases can be the same, except for Advanced Reporting. The Authoring databases must be different than the Runtime databases. For example, the SitePublisher database must be different from the LiveSite Display Services database.
To install TeamSite on Windows, Linux, or Solaris 1. Run the TeamSite Installer on your system. See Run the Autonomy Installer on Linux or Solaris on page 49 or Run the Autonomy Installer on Windows on page 49. 2. After you launch the installer, the Introduction dialog box opens. Click Next. If the installation program detects Common Services on your system, the installer skips Common Services step and the Select Installation Type dialog box opens. Go to Step 6. If the installation program does not detect Common Services on your system, the Add or Locate Common Services dialog box opens (see Figure 2).
NOTE In the installation wizard, you can move between text fields by either clicking a field or by pressing Tab.
50
Install TeamSite
Figure 2 Add or Locate Common Services
You can add or Locate Common Services in this dialog box. Common Services include Registry, User, and Config services. 3. Select the appropriate Common Services option from Table 6.
51
Table 6 Using the Common Services option Common Services options

Use Common Services on another computer
If you use this option...

Go to Step 4. If you select Use Common Services on another computer option, the installer uses common services installed on a different system. If you have an instance of Common Services already on a different machine, use the Use Common Services on another computer option. Common Services should be installed and running on the target system prior to using this option. The installer uses this remote Common Services to store and query the configuration information required for the installer to proceed. Go to Step 6. If you select Install Common Services on this computer option, the installer installs the Common Services application on this machine. To upgrade, reinstall, or uninstall Common Services. Use this option if you have not installed Common Services on a different machine. Installing Common Services and Common Services Client is mandatory for the installation to proceed. Go to Step 6. If you select Skip, only runtime applications will be installed, upgraded/reinstalled, or uninstalled option, the installer skips Common Services and other dependent components. Use this option if you want only runtime components such as LiveSite Display Services. Runtime components do not depend on Common Services.
Install Common Services on this computer
Skip, only runtime applications will be installed, upgraded/reinstalled, or uninstalled
4. After you select Use Common Services on another computer, click Next.
52
Install TeamSite
The Use Common Services on another computer dialog box opens (see Figure 3). Figure 3 Use Common Services on another computer
5. Type the Hostname and Port Number of the target computer and click Next. The Select Installation Type dialog box opens. The Uninstall option is only enabled if the installer detects a previous installation on the system. 6. Select Install and click Next.
53
The Select Components to Install dialog box opens (see Figure 4). Figure 4 Select Components to Install
Hover over a component to view component name, description, the
relevant installation package location and name, and the amount of disk space it requires.
Click Find to find an installation package (.iwpkg) file and add its
components to the list. If you selected Install Common Services on this computer option in the Common Services dialog box, all the Infrastructure Components including Common Services are selected by default. If you selected Skip, only runtime applications will be installed, upgraded/ reinstalled, or uninstalled option in the Common Services dialog box, all components except the runtime components are disabled. Components are enabled based on what is already installed and are selected automatically based on dependent item selections. See Components used by the Installer on page 26 for more information on components and their dependency. 7. Select Autonomy Administration Console, Autonomy TeamSite UI Framework, TeamSite User Interface, and TeamSite. Click Next.
54
Install TeamSite
The Select Base Directory for Installation dialog box opens (see Figure 5). Figure 5 Select Base Directory for Installation
The default installation directory for the selected components are as follows: Linux/Solaris: /usr/Interwoven Windows: C:\Interwoven Click Browse to select a different location or click Restore Default to select the default location. Installation location can also be entered directly.
IMPORTANT In Windows, the location of the installation directory must not contain any spaces. For example, you can use C:\Program Files\Interwoven\ but not C:\ Program Files (x86)\Interwoven\
8. Type or choose the installation location for TeamSite and other selected components. Click Next. The Autonomy License Agreement dialog box opens. 9. Accept the terms of the License Agreement, and click Next.
55
The first of the Configuration Details screens opens (see Figure 6). Figure 6 Configuration Details
10. Click Next to use the default port number.
56
Install TeamSite
The Select the Database Type dialog box opens (see Figure 7). Figure 7 Select the Database Type
CAUTION Ensure that you use an empty database for Common Services.
11. Select the database type for Common Services and click Next.
57
The Common Services Database Driver and Details dialog box opens (see Figure 8). Figure 8 Common Services Database Driver and Details
12. Type the following database configuration details for Common Services:
Database driver files. Browse and select the database drivers for the
selected database type.

Database Server Name. Name of the server that hosts the database. Database Listen Port. Port used by the database. Database Name. Database name as assigned by the database
administrator.
User Name. Database user created during the pre-installation tasks. User Password. Database user password.
NOTE Separate multiple file paths with commas.
58
Install TeamSite
If the selected database type is Oracle RAC or Custom, type the database configuration details as follows:
JDBC database driver file (directory where JDBC database drivers are
located)
JDBCDriver Class JDBC URL
If you select Oracle RAC, type the JDBC URL in the following format:
jdbc:oracle:thin:@(DESCRIPTION= (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST=dbhost1)(PORT=1521)) (ADDRESS = (PROTOCOL = TCP)(HOST=dbhost2)(PORT=1521)) (FAILOVER=on) (LOAD_BALANCE=off)) (CONNECT_DATA = (SERVER=DEDICATED) (SERVICE_NAME =dbservice))) Username (ID of the database administrator) Password (database administrator password)
When finished, click Next. The Directory for TeamSite Content Store dialog box opens (see Figure 9). Figure 9 Directory for TeamSite Content Store
59
The default installation directory for TeamSite Content Store are as follows: Linux/Solaris: /iw-store Windows: C:\iw-store Click Browse to select a different location.
CAUTION On Linux/Solaris, you must not select iw-store as the parent directory of iw-home.
13. Type or select the directory location for TeamSite Content Store and click Next.
If you install on Windows, the Stop Microsoft IIS Web Server for
Installation Process dialog box opens (see Figure 11 on page 61). Go to Step 15 to continue the installation procedure from there.
If you install on Solaris, the TeamSite Web Ports dialog box opens (see
Figure 14 on page 64). Go to Step 19.

If you are installing on Linux, the Location of the Compiled UVFS kernel
module dialog box opens (see Figure 10). Figure 10 Location of the Compiled UVFS kernel module
See Compile the UVFS Module on page 258 for information on how to compile the UVFS module.
60
Install TeamSite
14. Click Browse to select the location of the compiled UVFS kernel files. Go to Step 19. 15. Click Next. If IIS is installed, the Stop Microsoft IIS Web Server for Installation Process dialog box opens (see Figure 11). Figure 11 Stop Microsoft IIS Web Server for Installation Process
16. Select Stop IIS (recommended) and click Next.
61
The Configure Microsoft IIS Web Server for use with TeamSite dialog box opens (see Figure 12). Figure 12 Configure Microsoft IIS Web Server for use with TeamSite
17. Select the appropriate option:

Automatically configure IIS for TeamSite. The default and
recommended option. Click Next.

If you are using IIS 7, go to Step 18. If you are using IIS 6, go to Step 19.
Manually configure IIS later (after installation). You can manually
configure IIS if required. Click Next and go to Step 19. 18. If you selected automatic configuration in Step 17 and are using IIS 7, the Configure IIS Instance dialog box opens. Type your IIS User ID and IIS User Password in the text boxes and click Next.
62
Install TeamSite
19. The .Net Web Application for Preview dialog box opens if you selected automatic configuration in Step 17 and are using IIS 7 (see Figure 13). Figure 13 .Net Web Application for Preview
Select the appropriate option:

Automatically configure .Net Preview for TeamSite. The default and
recommended option.
Manually configure .Net Preview for TeamSite. You can manually
configure .Net Preview if required. Click Next.
63
The Configure TeamSite Ports dialog box opens (see Figure 14). Figure 14 Configure TeamSite Ports
The dialog box lists the TeamSite port numbers used by the Autonomy Interwoven Web Daemon, JMS server, and the Utility Daemon HTTP and HTTPS. Accept or edit the values and click Next.
64
Install TeamSite
The TeamSite Log Directory dialog box opens (see Figure 15). Figure 15 TeamSite Log Directory
20. Type or select the directory where you want to store the TeamSite log files. The default directory for TeamSite Content Server log files are as follows: Linux/Solaris: /usr/Interwoven/TeamSite/local/logs Windows: C:\Interwoven\TeamSite\local\logs When finished, click Next.
If you install on Windows, the SitePublisher Database Type dialog box
opens (see Figure 21 on page 71). Go to Step 26 and continue the installation procedure.
If you install on Linux or Solaris, the Location of the TeamSite mountpoint
for Content Store dialog box opens (see Figure 16).
65
Figure 16 TeamSite mountpoint for Content Store
Click Browse to select a different location or click Restore Default to select the default location. 21. Type or select the mount point that you want to use to access the content stored in your ContentStore and click Next. The Apache Content Server selection dialog box opens. 22. Perform one of the following actions:
If you are not using Apache as your Content Web Server, select No and
click Next. The TeamSite Event Subsystem and Utility Daemon Ports dialog box opens. Go to Step 24.
NOTE If you use a Web server other than Apache, you must configure it after the installation. See Configure TeamSite on page 129. If you use Apache as your Content Web Server, select Yes, and click
Next. The Apache httpd.conf file location dialog box opens (see Figure 17).
66
Install TeamSite
Figure 17 Apache httpd.conf file location
Click Browse to select a different location or click Restore Default to select the default location. 23. Type or select the location of your httpd.conf file, and click Next.
67
The Apache bin directory location dialog box opens (see Figure 18). Figure 18 Apache bin directory location
24. Type or select the location of your Apache bin directory, or click Restore Default to select the default location. Click Next.
68
Install TeamSite
The OpenDeploy Admin Username and Web Services connection information dialog box opens (see Figure 19). Figure 19 OpenDeploy Configuration
25. Type the following details:

OpenDeploy Admin username. Enter the OpenDeploy Admin user
name.
OpenDeploy Webservices Hostname. Enter the OpenDeploy
Webservices host name.

OpenDeploy Webservices Port. Enter the port number for the
OpenDeploy Web services.

LSDS Server Name. The location where you installed (or intend to install)
LiveSite Display Services

Web Site Root Directory. The path for the LiveSite Web site on that
system. for example, C:\Interwoven\LiveSiteDisplayServices.

Check here if LSDS will be configured with IIS. Select the check box if
the option applies to you. If you have multiple LSDS instances, you can type server details of any one instance. Refer to the OpenDeploy documentation to configure the deployment to all the other instances. 26. Click Next.
69
The SitePublisher Database type dialog box opens (see Figure 20). Figure 20 Database type for SitePublisher
The database type selected for CommonServices is selected by default. 27. Perform one of the following actions: Select No database if you do not wish to select a database for SitePublisher, and click Next. The TeamSite Reporting Database Configuration dialog box opens (see Figure 24 on page 74). Go to Step 33.
NOTE LiveSite Display Services shares the database requirements of SitePublisher. If you select No database for SitePublisher, the installer skips the LiveSite Display Services database configuration. You can manually configure the database later.
To use the default database, click Next.
70
Install TeamSite
The SitePublisher Database Driver Files and Details configuration dialog box opens. Figure 21 SitePublisher Database Driver Files and Details
The database text boxes are populated by default based on the details entered during the CommonServices database configuration (Step 11). 28. Click Next to complete the database connection configuration for SitePublisher.
71
The LiveSite Display Services Database Driver Files and Details configuration dialog box opens (see Figure 22). Figure 22 LiveSite Display Services Database Driver Files and Details
29. Type the Database Name. Note that LiveSite Display Services must use a separate database schema from that of SitePublisher. 30. The remaining database text boxes are populated by default based on the details entered during the CommonServices database configuration (see Step 11). Click Next at each one until you are presented with the Process Confirmation screen. Click Next again to install and configure the selected components. The processing time will vary based on the selected components. The installation Summary dialog box opens when the TeamSite installation process is complete.
72
Install TeamSite
The Configure Application Servers dialog box opens (see Figure 23). Figure 23 Configure Application Servers screen
31. Select the appropriate application server:

Apache Tomcat (Java). This is the default selection. Microsoft Internet Information Server (.NET). Select this if you are
installing LSDS on a .NET runtime environment. Click Next.

If you chose Apache Tomcat, the JDK Installation directory dialog box
opens. Go to Step 33.

If you chose Microsoft IIS, the Configure IIS Instance dialog box opens. Go
to Step 32. 32. Type the appropriate Web Site Port, IIS User, and IIS User Password and click Next.
73
The TeamSite Reporting Database Configuration dialog box opens (see Figure 24). Figure 24 TeamSite Reporting Database Configuration
33. Click Next to accept the default values and complete the database connection configuration for TeamSite Reporting.
74
Install TeamSite
The Basic ReportCenter Database Configuration dialog box opens (see Figure 25). Figure 25 Basic ReportCenter Database Configuration
The Basic ReportCenter Database Configuration dialog box opens if you chose to install Autonomy Administration Console in the Component Selection dialog box. The database text boxes are populated by default based on the details entered during the CommonServices database configuration. 34. Click Next to accept the default values and complete the database connection configuration for Basic ReportCenter. The Process Confirmation dialog box opens. 35. Click Next to install and configure the selected components. The processing time can vary based on the selected components. The installation Summary dialog box opens when the TeamSite installation process is complete. 36. Do one of the following, depending on your operating system:
Linux: Click Done. The installation is complete and the installer quits. Windows: Click Next. The Restart Confirmation dialog box opens. Click
Yes to restart your system now, or click No to restart later. Click Done.
75
Solaris: Click Next. The Restart Confirmation dialog box opens. Click
Done. The installer quits. To complete the installation on Solaris, from the shell prompt, run init 6 to reboot the system. After the restart, the installer runs automatically in silent mode. The Restart Confirmation dialog box opens. 37. Choose one of the following options:
Click Yes, restart my system to manually complete the post-restart
configuration later.
Click No, I will restart my system myself to start the post-restart
configuration. The Final Install and Configuration Summary dialog box opens. 38. Click Done. 39. After your system restarts, run the TeamSite installer again to automatically complete the post-restart configuration.
Post-Installation Tasks
This section describes the tasks you must perform after the installation is complete. After installing TeamSite, perform the following tasks 1. If OpenDeploy was not installed prior to installing TeamSite, install the OpenDeploy base server on the development system and configure it for SitePublisher (see Configure OpenDeploy after TeamSite Installation on page 78). 2. Deploying sites from the SitePublisher development server to the runtime environment server is accomplished through a TeamSite workflow. Because such workflows are situation-specific, a default workflow is not implemented. Therefore, you must configure a workflow prior to any deployment. SitePublisher uses the default Publish LiveSite Content workflow. This workflow can be customized as needed. To accomplish these tasks, take the following actions on the development server after installing SitePublisher: To configure a workflow: (For more information, refer to the Workflow Modeler User Guide.) a. Log in to TeamSite ContentCenter Professional and click Administration.
76
b. In the Administration Console, select Configurations tab, and then select Application Configurations. From the left pane, select Workflow:available_model.xml. c. The contents of the available_models.xml file appear in the right pane. Click Edit. d. In the Edit window that opens, add the following code snippet in bold:
<available_models xmlns="http://www.interwoven.com/modeler/ schema/subscription10"> <model debug=false active=true filename=Publish LiveSite Content name=Publish LiveSite Content> <allowed> <and> <vpath-regex regex=^(//[^/]+)?/default/ main.*/> <command name=submit/> </and> </allowed> </model> <model debug=false active=true filename=Globalization name=Translation Workflow> <allowed> <and> <vpath-regex regex=^(//[^/]+)?/default/ main.*/> <command name=translate/> </and> </allowed> </model> </available_models>
e. Click Save. You can log out of TeamSite after this step.
NOTE The following steps set up the metadata capture rules for SitePublisher and create the SitePublisher and LiveSite database tables. The databases must be created prior to executing these steps.
f.
You must map assets to the supplied rules in the metadata-rules.cfg file if you use metadata with your content. Edit the metadata-rules.cfg.livesite.template file in the ts-home/ local/config directory and merge it with the metadata-rules.cfg file in the same directory as appropriate. This includes the following rules:
LiveSite Content Rule. This rule applies metadata associated with a LiveSite content item. Any asset tagged with this rule can be deployed
77
using the ExtendedAttributeContentMetadata deployment. For more information, refer to LiveSite Content Rule in the TeamSite Site Developer Guide.
LiveSite Rule. This modifiable rule is used when deploying content items (such as the Content, News, Event, and BlogEntry items, which are included in the installation) to the database. For more information, refer to the TeamSite Site Developer Guide. LiveSite Image Rule. This modifiable rule is used while deploying images (regex .jpg, gif, .png) to the runtime. For more information, refer to the TeamSite Site Developer Guide.
g. Go to Administration Console and click Servers. The available servers appear in the left pane. h. Select OpenDeploy. Click Edit. The Edit OpenDeploy Server Settings dialog box opens. i. j. Change the default Address to the correct hostname. Click Save. OpenDeploy is registered successfully.
3. Procure a TeamSite license. Contact your Autonomy representative for more information. 4. Enable SitePublisher and Targeting in the license file. 5. (Solaris only) Ensure the fully qualified host.domain is the first entry in hosts file after the IP address to validate the license. 6. Copy the license file in ts-home/etc. 7. Reset the services. 8. Migrate any DCRs and SitePublisher sites from earlier versions using the Dependency Migration tool to ensure that the Globalized Content Management and Find Related Files functions work properly. For more information, see Migrate Content to Support TeamSite Associations on page 123.
Configure OpenDeploy after TeamSite Installation

The procedure in this section is only necessary if you have not already installed OpenDeploy. To configure OpenDeploy after installing OpenDeploy Base Server, on the development server 1. Overwrite od-home/etc/passphrase with ts-home/private/etc/ passphrase. 2. Copy the JDBC drivers to od-home/drivers and od-home/userlib.
78
3. If you have used the MSSQL database, remove sqljdbc4.jar from od-home/drivers and od-home/userlib (as it is not compatible with OD7 Java5 VM). 4. In od-home/etc/odnodes.xml, add the following element to the <nodeSet> element: <node name="LiveSiteRuntime" host=RuntimeServerName port="20014"/> where,
RuntimeServerName is the name of the server on which LiveSite
Display Services is installed. The name of the runtime server should be localhost if LiveSite Display Services and SitePublisher are installed on the same machine. 5. In od-home/etc/odbase.xml, add the following element to the <allowedHosts> element: <node host="RuntimeServerName">
<allowedDirectories> <path name="ls_home\runtime\web"/> </allowedDirectories> </node>
where,
RuntimeServerName is the name of the server on which LiveSite
Display Services is installed.

ls-home\runtime\web is the path to the LiveSite Display Services
installation directory. 6. Navigate to ts-home/local/config/lib/content_center/ livesite_customer_src/etc/conf/livesite_customer/ opendeploy.properties. Edit the following entries:
opendeploy.home=$IW_ODHOME_UNIXSTYLE$
Replace $IW_ODHOME_UNIXSTYLE$ with the path to the OpenDeploy installation directory.

opendeploy.webServicePort=$IW_OD_WS_HTTP_PORT$
Replace $IW_OD_WS_HTTP_PORT$ with the OpenDeployWebService listening port number.

opendeploy.proxyUserName=$IW_OD_BOOTSTRAP_USER_NAME$
Replace $IW_OD_BOOTSTRAP_USER_NAME$ with the proxy user account information that LiveSite uses to authenticate with OpenDeploy.
79
The username format for Windows is <domain-name>\\<user-name>.

opendeploy.runtimeHome=$IW_LIVESITE_ENDUSER_WEB_UNIXSTY
LE$ Replace $IW_LIVESITE_ENDUSER_WEB_UNIXSTYLE$ with the path to the LiveSite Display Services installation directory on the production host. Example: ls-home/runtime/web. 7. Navigate to ts-home/local/config/lib/content_center/ livesite_customer_src/ and run the command build.bat[sh] to update the opendeploy.properties file. 8. Copy the contents of ts-home/install/opendeploy/ to od-home. 9. Navigate to od-home/etc. Make a copy of livesite-database.xml.template and rename it to livesite-database.xml. In the livesite-database.xml file, edit the following entries so that they contain the appropriate database values for the databases that you used on the production and development servers:
<database name="livesite-production" db="$IW_PROD_DB_CONNECT_STRING$" user="$IW_PROD_DATABASE_USER_NAME$" password="$IW_PROD_DATABASE_USER_PWD$" vendor="$IW_DB_VENDOR$" jdbc-driver="$IW_PROD_JDBC_DRIVER$" protocol-url="$IW_PROD_PROTOCOL_URL$" db="$IW_DEV_DB_CONNECT_STRING$" user="$IW_DEV_DATABASE_USER_NAME$" password="$IW_DEV_DATABASE_USER_PWD$" vendor="$IW_DB_VENDOR$" jdbc-driver="$IW_DEV_JDBC_DRIVER$" protocol-url="$IW_DEV_PROTOCOL_URL$" NOTE You can specify an encoded password if you add the field password-encoded="yes". Use the encryption utility in the LiveSite Customer Toolkit to encrypt passwords. Refer to the TeamSite Site Developer Guide.
Example: Microsoft SQL 2005

<database name="livesite-production" db="<dbservername>:1433?database=pelican" user="livesite" password="livesite" vendor="microsoft-inetuna" jdbc-driver=""
80
protocol-url="" <database name="livesite-development" db="<dbservername>:1433?database=mauser" user="livesite" password="livesite" vendor="microsoft-inetuna" jdbc-driver="" protocol-url=""
10. If the database type is not Microsoft SQL 2005 or Microsoft SQL 2008, navigate to od-home/conf/LiveSite. Within all the .xml files in the Livesite folder, replace all instances of the entry, __IW_DATE_DATATYPE__ with date. 11. If the database type is Microsoft SQL 2005 or Microsoft SQL 2008, navigate to od-home/conf/LiveSite. Within all the .xml files in the Livesite folder, replace all instances of the entry __IW_DATE_DATATYPE__ with datetime. 12. Copy the appropriate database driver files for the databases you use to the following locations:
od-home/userlib od-home/drivers
13. In the machine containing OpenDeploy Receiver is installed, navigate to od-home/etc/odrcvr.xml. Add the following element to the <allowedHosts> element:
<node host="ODServerName"> <allowedDirectories> <path name="ls_home\runtime\web"/> </allowedDirectories> </node>
where,
ODServerName is the name of the server on which OpenDeploy Base is
installed.
ls-home\runtime\web is the path to the LiveSite Display Services
installation directory. 14. Navigate to od-home/conf/LiveSite/OpenDeployWebRoot.xml. Replace the entry __IW_ODBASE_SERVER__ with the name of the server on which OpenDeploy Base is installed. The name of the OpenDeployBase server should be localhost if LiveSite Display Services and SitePublisher are installed on the same machine. 15. Restart the OpenDeploy services and daemons. 16. Open a command prompt and run the command iwreset -ui.
81
Configure LiveSite Server after TeamSite Installation

NOTE The procedure in this section is only necessary if you have not already installed LiveSite Server.
The server name entry is added to the host element in the od-home/etc/ odnodes.xml. The Web Site root directory path is added to opendeploy.runtimeHome in the ts-home/local/config/lib/ content_center/live_customer_src/etc/conf/ livesite_customer/opendeploy.properties. Go to the ts-home/local/config/lib/content_center/ livesite_customer_src directory, create the database schema, and populate the tables as follows:
Windows: Open the Run dialog box (Start-> Run) and type the following command:
build.bat update
Linux/Solaris: Type the following command:

./build.sh update
Configure Targeting after TeamSite Installation

Targeting is installed with the TeamSite component. Perform the next procedure to configure Targeting. To complete the Targeting installation 1. Create a Targeting test branch. a. Log in to TeamSite. b. Create a branch: /default/main/targeting-heartbeat c. Create a workarea named as shared 2. Install targeting-heartbeat.spar by running the following commands. a. cd ts-home/install b. <ts-home>/iw-perl/bin/iwperl <ts-home>/install/ install_archive.ipl -i <ts-home>/install/ targeting-heartbeat.spar /default/main/ targeting-heartbeat/WORKAREA/shared 3. Submit to development.
82
a. Navigate to the workarea. b. Select all the top area folders. c. Submit the content to development using the Publish LiveSite Content workflow. 4. Create Users. a. Log in to TeamSite. b. Create teen@test.com and adult@test.com users for development. 5. Test targeting. See Verify Targeting Installation on page 84.
TeamSite License
TeamSite does not require a license for the installation. After the complimentary period of 48 hours or after the first restart, the TeamSite server requires a valid license. 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 as follows: Linux/Solaris: ts-home/etc Windows: iw-home\etc
To use Content Stores from a Previous TeamSite Version

If you use a content store from an earlier TeamSite version with a new installation, you must run the Dependency Migration Tool to ensure the Find Related Files, Publish LiveSite Content workflow, and Globalized Content Management features work properly. See Migrate Content to Support TeamSite Associations on page 123.
Verify the Installation

Use the following procedure to verify whether the installation was successful. To verify whether TeamSite installed successfully 1. Access TeamSite from a client computer, through your Web browser, and type either of the following URLs for the ContentCenter interfaces:
http://server_hostname http://server_hostname/iw-cc
83
where server_hostname is the name of your TeamSite server (for example, teamsite1.example.com). You can bookmark this URL for future use. The TeamSite login dialog box opens. 2. Type your user name and password. By default, TeamSite accepts the host systems Administrator or root user name and password for all user roles. 3. Click Login. The TeamSite ContentCenter home page opens. 4. Verify that the Site Map tab and the SitePublisher menu appear on the home page. 5. Browse to the Component Guide folder.
//alpha/default/main/component-guide/STAGING/sites/Component Guide/default.site
6. Create a simple site. 7. Run a development deployment to test the deployment and database configuration.
Verify Targeting Installation

Targeting is installed with the TeamSite component. To verify the Targeting installation 1. Navigate to targeting-heartbeat/WORKAREA/shared/sites/ Targeting Heartbeat. 2. Click Anonymous Targeting.page. a. Verify that the rule execution result is: Success. URL contains '.'. b. Verify for Targeting Success Image. c. Verify for Content Retrieval Success Image. d. Verify for Anonymous Segmentation Success link. 3. Click User Profile Targeting.page. Log in as one of the users created for development. Verify that the Anonymous Segmentation Success link changes to User Profile Segmentation Success based on the current user. This also affects the link displayed on the Anonymous Targeting.page until you log out using the button on the User Profile Targeting.page.
84
Recreate and Reconfigure Databases after Installation

It may be necessary to recreate databases and change database configuration details (server, name, or password) for various components after the installation if the databases were not configured correctly initially.
SitePublisher and LSDS

You can recreate and reconfigure the SitePublisher and LiveSite Display Services runtime databases at the same time or separately. To recreate the SitePublisher and LSDS databases simultaneously 1. Navigate to ts-home/local/config/lib/content_center/ livesite_customer_src. 2. Run the following command:
build sql.create
The schema (Data Definition Language) and initial data (Data Manipulation Language) are created in the development and production databases. To recreate the SitePublisher and LSDS databases separately 1. Navigate to ts-home/local/config/lib/content_center/ livesite_customer_src. 2. Run one or both of the following commands.
For SitePublisher: build sql.create.development For LSDS: build sql.create.production
To change database configuration settings 1. Under ts-home/local/config/lib/content_center/ livesite_customer_src, open all database.properties files (by default there is only one, but check the preview, runtime, and portlet folders for overrides) in a text editor. 2. Edit the fields according to the instructions contained in the file. You can update your development and production database connections at the same time.
85
3. In the livesite_customer_src directory, run the appropriate command.

To update the preview environment: build install To create an update package that you can manually install in your LSDS
instances:
build runtime.zip
Administration Console and CommonServices

The Administration Console uses the CommonServices database and tables within it. You must run several scripts to recreate the database and tables, then register several components. To recreate the CommonServices database and the required tables 1. Run the following script to create the database.
--------------------------------------------------------------/****** Object: Database [CommonServices] ******/ CREATE DATABASE CommonServices_DB_NAME GO
2. Run the following scripts to create the required tables.

/****** Object: Table [dbo].[IR_DBINFO] Script Date: 12/10/2010 12:08:52 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO CREATE TABLE [dbo].[IR_DBINFO]( [DBENTRY_ID] [numeric](19, 0) IDENTITY(1,1) NOT NULL, [connectionDriverClass] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [connectionUrl] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [userName] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [userPwd] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [dbType] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [dbServerName] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [dbName] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
86
[dbPort] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [componentName] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, PRIMARY KEY CLUSTERED ( [DBENTRY_ID] ASC )WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY] GO SET ANSI_PADDING OFF ----------------------------------------------------------------------------------------------------------------------------/****** Object: Table [dbo].[IR_GENERICINFO] Script Date: 12/ 10/2010 12:10:07 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO CREATE TABLE [dbo].[IR_GENERICINFO]( [COLUMN_KEY] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [value] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, PRIMARY KEY CLUSTERED ( [COLUMN_KEY] ASC )WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY] GO SET ANSI_PADDING OFF ----------------------------------------------------------------------------------------------------------------------------/****** Object: Table [dbo].[IR_GENERICINFOWITHNAMESPACE] Script Date: 12/10/2010 12:10:39 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO CREATE TABLE [dbo].[IR_GENERICINFOWITHNAMESPACE](
87
[NAMESPACE] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [GENERIC_KEY] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [GENERIC_VALUE] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, PRIMARY KEY CLUSTERED ( [NAMESPACE] ASC, [GENERIC_KEY] ASC )WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY] GO SET ANSI_PADDING OFF ----------------------------------------------------------------------------------------------------------------------------/****** Object: Table [dbo].[IR_SERVICEINFO] Script Date: 12/ 10/2010 12:10:56 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO CREATE TABLE [dbo].[IR_SERVICEINFO]( [serviceId] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [serviceName] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [componentName] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [description] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [installLoc] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [status] [int] NULL, [hostName] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [port] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [sslPort] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [version] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [buildNumber] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
88
[osType] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [startTime] [datetime] NULL, [stopTime] [datetime] NULL, PRIMARY KEY CLUSTERED ( [serviceId] ASC )WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY] GO SET ANSI_PADDING OFF ---------------------------------------------------------------
To register components 1. Run the following insert statement.

--------------------------------------------------------------INSERT INTO [dbo].[IR_SERVICEINFO] ([serviceId] ,[serviceName] ,[componentName] ,[description] ,[installLoc] ,[status] ,[hostName] ,[port] ,[sslPort] ,[version] ,[buildNumber] ,[osType] ,[startTime] ,[stopTime]) VALUES ('CsJKi1j6E45usCG2D2WTBDT14E0LIM2ZvZvi8T76O/ qmXeP8HOq+dHtleOL1F9mL' ,'UnifiedInstaller' ,NULL ,'Interwoven Unified Installer' ,NULL ,0 ,NULL ,NULL ,NULL ,NULL ,NULL ,NULL ,NULL ,NULL)
89
---------------------------------------------------------------
The statement creates a unified installer entry, which allows you to register components with CommonServices. 2. Run iwirregister.bat to register the following components in order. a. CommonServices b. TeamSite c. InterwovenAdministrationConsole For example:
iwirregister.bat -C TeamSite "Autonomy TeamSite" <TeamSiteHostName> "D:\utils\iw-home\TeamSite" "" "" win NOTE Run iwirregister.bat without any parameters to list the parameters it requires for registration.
3. Restart JBoss. To change the CommonServices database and machine names 1. Open the database properties with its respective database management tool (for example, Microsoft SQL Server Management for SQL databases) and record the database name and server name. 2. Open the CommonServices database.properties file in a text editor. The default file location is:
iw-home\CommonServices\config\private\database.properties
3. Change the database and machine names in the connection.url entry. For example:
connection.url=jdbc:sqlserver:// NewMacName:1433;databaseName=NewDBName
where NewMacName is the machine name from IR_DBINFO and NewDBName is the database name from IR_DBINFO. 4. Change the value of the database.name property to the new database name. 5. Change the value of the database.server property to the new machine name. 6. Save and close the file.
90
To change the CommonServices database password 1. Open a Windows command prompt and go to iw-home\ CommonServicesClient\bin. 2. Run the following command:
iwirencryption.bat -e
You are prompted to type some text for encryption. 3. Type the new database password and press ENTER. The encrypted password is returned. 4. Copy the encrypted text without the leading or trailing spaces. 5. Open the CommonServices database.properties file in a text editor. The path to the file is:
iw-home\CommonServices\config\private\database.properties
6. Replace the value of the connection.password property with the new encrypted password. 7. Save and close the database.properties file. 8. Restart JBoss.
LSCS Runtime
This section describes how to recreate and reconfigure the LSCS Runtime database. For instructions on LSCS Runtime, refer to the Web Solutions Runtime Components Installation Guide. To recreate the LSCS runtime database 1. Create the schema and database on the database server. The procedure depends on the type of database server you are using. Refer to the database server documentation for more information. 2. In the <lscsauth-home>\install\sql folder, run the SQL script for the appropriate database server, such as lscs_ddl_sqlserver.sql for SQL servers or lscs_ddl_oracle.sql for Oracle servers. The script creates the table structure in the database. To reconfigure the LSCS runtime database 1. Open the lscs-conf.properties file in a text editor. The path to the file is: <lscsauth-home>\runtime\webapps\lscs\WEB-INF\classes\ lscs-conf.properties 2. Change the appropriate configuration parameters (see Table 7).
91
Table 7 Configuration parameters Configuration Parameter

dataSource.username dataSource.password
Description
Database user name. Encrypted database password. To generate an encrypted password, run the appropriate encryption utility in <LSCSAUTH-HOME>\ install\scripts\: encryptpassword.bat (Windows) encryptpassword.sh (Linux)
dataSource.jarList dataSource.driverClassNa me
Database driver file (see Supported Databases and Drivers on page 36) Driver class name for the database server. For MSSQL: com.microsoft.sqlserver.jdbc. SQLServerDriver For Oracle: oracle.jdbc.driver.OracleDriver For MYSQL: com.mysql.jdbc.Driver For DB2: com.ibm.db2.jcc.DB2Driver
92
Table 7 Configuration parameters (continued) Configuration Parameter

dataSource.url
Description
Database server, port number, and name. In the following examples, Server is the name of the server, Port is the port number, and DBName is the database name. For MSSQL:
jdbc:sqlserver:// Server:Port;databaseName=DBName
For example: jdbc:sqlserver:// sitepubdev:1433;databaseName= atlscsrt For Oracle: jdbc:oracle:thin:@Server:Port: DBName For example: jdbc:oracle:thin:@sitepubdev:1521: atlscsrt For MYSQL: jdbc:mysql://Server:Port/DBName For example: jdbc:mysql://sitepubdev:3306/ atlscsrt For DB2: jdbc:db2://Server:Port:DBName For example: jdbc:db2://sitepubdev:3978/ atlscsrt hibernateDialect Database server dialect. All possible values are listed in code comments in the lscs-conf.properties file.
3. Restart the application server.
93
Report Center and Advanced Reports

Before you can change the Report Center and Advanced Reports database details, the database administrators must copy the full set of databases including the schemas, data, and permissions. To reconfigure the Report Center and Advanced Reports databases 1. Open the database properties with its respective database management tool (for example, Microsoft SQL Server Management for SQL databases) and record the database name and server name. 2. Navigate to:
<iw-home>/ApplicationContainer/server/default/deploy
3. In a text or XML editor, open js-jboss-ds.xml. This file contains the JNDI data source bindings with the following JNDI names: ? jdbc/jasperserver (Report Center) ? jdbc/jasperserver-pro (Advanced Reports) 4. Update the databaseName, serverName and userName in the appropriate section.
For Report Center, it should resemble the following example: <local-tx-datasource> <jndi-name>jdbc/jasperserver</jndi-name> <connection-url>jdbc:sqlserver:// sitepubdev:1433;databaseName=iwreportcenter;SelectMethod=cur sor</connection-url> <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</ driver-class> <user-name>sa</user-name> <password>iwov</password> <min-pool-size>5</min-pool-size> <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> </local-tx-datasource> For Advanced Reports, it should resemble the following example: <local-tx-datasource> <jndi-name>jdbc/jasperserver-pro</jndi-name> <connection-url>jdbc:sqlserver:// sitepubdev:1433;databaseName=iwadvreportcenter;SelectMethod= cursor</connection-url> <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</ driver-class> <user-name>sa</user-name> <password>iwov</password>
94
Uninstall TeamSite
<min-pool-size>5</min-pool-size> <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> </local-tx-datasource>
5. From a command prompt, go to the following directory:

iw-home\CommonServicesClient\bin
6. Run the following command:

iwirencryption.bat -e
You are prompted to input text for encryption. 7. Type the password from Step 4 press ENTER. The encrypted password returns. 8. Copy the encrypted text without the leading or trailing spaces. 9. Open the database properties with its respective database management tool (for example, Microsoft SQL Server Management for SQL databases) and paste the encrypted password in the appropriate user password field. 10. From a command prompt, run the following command:
iwreset -a
Uninstall TeamSite
This section describes how to remove TeamSite from your system using the TeamSite installer. You cannot use the 7.x installer to uninstall pre-7.x versions of TeamSite. To uninstall versions prior to 7.x, see Clean or Remove the Installation Manually on page 253. You can use the Autonomy Installer to uninstall TeamSite on the Linux, Solaris, or Windows platform. To uninstall TeamSite from your server 1. Run the TeamSite Installer on your system. See Run the Autonomy Installer on Linux or Solaris on page 49 or Run the Autonomy Installer on Windows on page 49. 2. The TeamSite installer starts and the Introduction dialog box opens. 3. Click Next.
95
The installation program detects Autonomy Registry on your system and the Installation Type dialog box opens (see Figure 26). Figure 26 Installation Type
You can find the previous installation details in the Installation Type dialog box. If the installation program does not detect any previously installed Autonomy Interwoven components, the Registry dialog box opens and it enables you to install new components only. 4. Select Uninstall in the Installation Type dialog box, and click Next.
96
Uninstall TeamSite
The Select Components to Uninstall dialog box opens (see Figure 27). Figure 27 Select Components to Uninstall
The installer displays the components available for uninstall. 5. Select TeamSite and dependent components to uninstall. Click Next. The Process Confirmation dialog box opens. 6. Click Next. The installer uninstalls the selected components and the Summary dialog box opens. 7. Click Next. If you are working on a Windows system, the Restart Confirmation dialog box opens. UNIX machines must be restarted manually. 8. Select Yes to restart your system now or No to restart later. Click Done.
97
98
CHAPTER 4
Silent Installation Options

This section describes how to run the silent installation options (that is, without a GUI).

About Silent Installation Selectively Run Silent Operations on Package Components Run the Encryption Utility Merge Multiple Silent Installation Input Files Run a Silent Installation Switch from Silent to UI Installation Run a Silent Upgrade Run a Silent Uninstallation
About Silent Installation

Silent installation provides a way for you to perform a console-based installation, especially on a UNIX system where the X Window System may not be available. Silent installation input files provide the text input that you would otherwise enter through the user interface during a normal (that is, non-silent) installation. The silent installation input files are properties files that consist of key-value pairs and a list of affected components in the package.
99
Chapter 4 Silent Installation Options
Each package you install has a corresponding silent installation input file that you need to copy and customize for your environment and desired configuration. The provided silent installation input files show all the possible inputs and values. You fill in the desired values and save it with a different name before running the silent operation. The silent installation input files offer the following operational options on complete packages or their selected components:

installation upgrade an installation uninstallation (removal)
Selectively Run Silent Operations on Package Components

By default, all components in the package are selected for the installation, upgrade, or uninstallation operation. If you need to specify which components to affect, change the COMPONENT_UNIQUE_IDLIST value in the silent installation input file to contain only the desired components. The COMPONENT_UNIQUE_IDLIST value lists components; their information is delimited by an ampersand (&). To exclude a component, remove all of the component information from the value. The component properties can remain in the silent installation input file because they are not used.
NOTE Some components may have dependencies on other components so using operations with selective components may cause the operation to fail. Contact Autonomy Customer Support for assistance before using any operation involving selective components.
Run the Encryption Utility

Having encrypted passwords is a prerequisite to changing the silent installation input file. A command-line encryption utility program (an executable jar file) can convert plain-text passwords (or other sensitive values) to encrypted passwords.
100
Merge Multiple Silent Installation Input Files
NOTE Autonomy recommends storing the encryption utility in a secure location. While Autonomy strongly encourages you to encrypt passwords, if you intend to use unencrypted passwords, contact Autonomy Customer Support.
You run the password encryption utility (with the clear-text password as the argument) to generate an encrypted password before you modify your silent installation input file.
NOTE The database you use may impose restrictions on allowable characters in passwords or password length. Refer to the database documentation for any such restrictions.
To generate an encrypted password 1. Review the silent installation input file to identify the passwords you need to provide (refer to the files mentioned in Run a Silent Installation on page 102). 2. Run the encryption script with the clear-text password as the argument. It outputs an encrypted password to the screen. java -jar iwov-install-enc.jar <clear-text_password> 3. Copy the encrypted password to use in your custom install.properties file. 4. Repeat the process as needed to generate additional encrypted passwords.
NOTE Encrypted passwords that are generated multiple times from the same clear-text password differ. If you need to use two passwords and they are the same, you can use the same encrypted password for both databases or you can generate a new encrypted password so the encrypted text differs. Both encrypted passwords decrypt to the same clear text.
Merge Multiple Silent Installation Input Files

While you can merge data from multiple, silent-installation input files, it is easier Autonomy recommendsthat you install independently from different silent installation input files.
101
NOTE If the merge is not done correctly, installation may not succeed. Contact Autonomy Customer Support before merging silent installation input file files.
To merge multiple silent installation input files 1. Copy the desired name-value pairs from one installation.properties file and paste them into the installation.properties file to be installed. 2. Update the COMPONENT_UNIQUE_ID_LIST key with newly merged component list. 3. Save the installation.properties file and perform the silent installation with the next procedure.
Run a Silent Installation

The provided silent installation input files are:
Silent installation for TeamSite:

Windows:
IWOVTeamSite-Windows-<VersionNumber>.silent_install.pr operties
UNIX:
IWOVTeamSite-UNIX-<VersionNumber>.silent_install.prope rties
Silent installation for LiveSite (UNIX) runtime package (LSCS and LSDS): IWOVLiveSite-UNIX-<VersionNumber>.silent_install. properties
Silent Installation for Report Center IWOVReportCenter-<VersionNumber>.silent_install. properties

NOTE The following procedure shows UNIX paths (with forward slash (/) in paths). To use the instructions with Windows, change the forward slash to back slash (\).
102
Run a Silent Installation
To perform a silent installation 1. From the command line, make a directory with the MD <install_directory>/iwinstall/private/config command. 2. Unzip the silent installation zip file to the new <install_directory>. The <install_directory> is the directory where TeamSite is to be installed. This must be the location to specify in installer.properties as the default installation location. 3. Copy the silent installation input file to the <install_directory>/ iwinstall/private/config directory.
copy IWOVTeamSite-<Operating_System>-<VersionNumber>.silent_install. properties <install_directory>/iwinstall/private/config
4. Change to the <install_directory>/iwinstall/private/config directory with the CD command.

CD <install_directory>/iwinstall/private/config
5. Rename the copied silent installation input file to installer.properties. (The installer may reboot; it needs to find this file to continue.)
ren IWOVTeamSite-<Operating_System>-<VersionNumber>.silent_install. properties installer.properties
6. In the <install_directory>, make sure all scripts have execute permissions. (Refer to man chmod on the command line for detailed instructions on changing file permissions.)
chmod +x SilentInstall.sh
(Optional) in Windows, run silent installation by typing:

IWOV-Installer.exe -f <path_to_silent_install_input_file> -i silent
7. Modify the values in your silent installation input file marked with <customer-data>. Ensure that all these parameters have your values before you start the installation. 8. (Optional) By default, all components in the package are selected for the operation. To specify which components to install, upgrade, or uninstall, modify the COMPONENT_UNIQUE_IDLIST value to contain only the desired components. The value list components and their information are delimited by an ampersand (&).
103
IMPORTANT Components may have dependencies on other components, so removing components can cause the operation to fail. Contact Autonomy Customer Support for assistance before removing any components.
To exclude a component, remove all the component information from the value. The component's properties can remain in the template as they are not used. 9. Ensure that all scripts have execute permissions. a. To view the octal numerical values (where * lists all files in current directory), run:
stat -c '%A %a %n' *
b. To change the change a file to have execute permissions, run:

chmod 555 myfile
10. (Optional) For sensitive values, use the encryption script to generate the encrypted value. Run the script with the clear-text password as the argument. It outputs an encrypted password that you can copy and paste into your custom silent installation template. You can use the same encrypted password if the value is the same or you can generate a new one (newly generated encrypted passwords from the same clear-text password differ). a. To run the encryption utility, make sure that you have Java 1.5 or later installed and in the path. Run the utility as:
java -jar iwov-install-enc.jar <clear-text_password>
b. Copy the encrypted passwords and paste them into your custom silent installation input file, installer.properties (see Run the Encryption Utility on page 100). c. Save the silent installation input file. 11. Read the accompanying readme.txt file, and then run the silent installation command:
./SilentInstall.sh <path-to-installer.bin> <path-to-installer.properties>
12. Review the output log, /tmp/stderr.log, for any errors.

the UNIX silent installation script starts the tail operation on the output
104
Switch from Silent to UI Installation
use the UNIX command, tail /tmp/stderr.log to view status
information and any errors that may have occurred during operation
Windows users can open the log file with a text editor such as Notepad
Switch from Silent to UI Installation

You can switch between a silent and UI installation by modifying the installer.properties file. To switch from a silent installation to a manual UI installation 1. In the installer.properties file, delete the INSTALLER_UI=silent entry. 2. Restart the installer.
Run a Silent Upgrade

By default, the silent installation input files perform an installation, however, you can modify them to do upgrades and uninstallations by changing the value of the INSTALLTYPE property. To perform a silent upgrade 1. Edit the silent installation input file as shown in Run a Silent Installation on page 102. 2. Leave the INSTALLTYPE value of INSTALL. 3. Be sure to change all other relevant properties for the operation. 4. Run the script to perform the silent operation.
./SilentInstall.sh -f <path_to_silent_install_input_file>

Use the UNIX command, tail /tmp/stderr.log to view status
information and any errors that may have occurred during the operation.
Windows users can open the log file with a text editor such as Notepad.
105
Run a Silent Uninstallation

To perform a silent uninstallation 1. Edit the silent installation input file as shown in Run a Silent Installation on page 102. 2. Change the INSTALLTYPE value to UNINSTALL. 3. Adjust the component list so that it matches what is being done and the components to which it is referring.
Use pkg to refer to components in the package. It is used for installation
and upgrade.
Use loc (instead of pkg which is used for installations and upgrades), to
specify the components to uninstall. To specify a loc component in the component unique id list, provide:
n v i d [<name>] [<version>] [<true|false>] (this is "installed") [<directory of the installed component>]
The values you provide must match the values specified in inventory.xml. The following code is a TeamSite example:
COMPONENT_UNIQUE_IDLIST=loc\: n[TeamSite], v[7.2.1.0.0], i[true], d[C\:\\Interwoven\\TeamSite]
NOTE Be sure to escape all special characters such as : and \.
4. Run the script to perform the silent operation.

./SilentInstall.sh -f <path_to_silent_install_input_file>

Use the UNIX command, tail /tmp/stderr.log to view status
information and any errors that may have occurred during the operation.
Windows users can open the log file with a text editor such as Notepad.
106
CHAPTER 5
Upgrade and Migrate TeamSite

You can use the Autonomy Installer to upgrade TeamSite on the Linux, Solaris, or Windows platform.

Upgrade Paths Files to Back Up Before Upgrading or Migrating Upgrade TeamSite on Linux, Solaris, or Windows Migrate TeamSite
Upgrade Paths
TeamSite 7.3 supports the following upgrade paths. If you are upgrading from or to a version not listed here, contact Autonomy Customer Support.
TeamSite 7.x to TeamSite 7.3.2
107
Chapter 5 Upgrade and Migrate TeamSite
Files to Back Up Before Upgrading or Migrating

If you intend to connect TeamSite 7.3.2 to MediaBin 7.x or earlier, you must back up the following files and directories before upgrading. You will need to restore them later in the installation (see Configure MediaBin Connector for Legacy MediaBin Servers on page 147).
<ts-home>/etc/TS.lic
NOTE To operate with MediaBin 7.x or earlier, the TeamSite license file must have Rich Media Management (RMM) disabled. You can backup the license file before upgrading or contact Autonomy Customer Support for a license file with RMM disabled.
<ts-home>/private/lib/content_center/ecmconnector.tk.war <ts-home>/iw-perl/vendor/lib/TeamSite/PT/ iwov_import_mediabin.pm <ts-home>/iw-perl/vendor/lib/TeamSite/PT/ iwov_mediabin_param.pm <ts-home>/examples/Templating/templatedata/ecm
To access MediaBin 7.x, you must also back up the Update MediaBin Assets workflow model file and configuration directory:

<iwmount>\iwadmin\main\workflowModels\WORKAREA\iw-wa\ Models\Update_MediaBin_Assets.ipm <iwmount>\iwadmin\main\workflowModels\WORKAREA\iw-wa\ Config\Update_MediaBin_Assets_config
Upgrade TeamSite on Linux, Solaris, or Windows

Use this procedure to upgrade TeamSite.
108
To upgradeTeamSite on your server 1. Run the TeamSite Installer on your system. See Run the Autonomy Installer on Linux or Solaris on page 49 or Run the Autonomy Installer on Windows on page 49. The Autonomy installer starts with the Introduction dialog box.
TIP In the installation wizard, you can move between text fields by either clicking a field or by pressing Tab.
2. Click Next.
If the installation program detects Common Services on your system, the
installer skips the Common Services step and the Installation Type dialog box opens. Go to Step 6 on page 111 to continue the installation procedure.
If the installation program does not detect Common Services on your
system, the Add or Locate Common Services dialog box opens (see Figure 28). Figure 28 Add or Locate Common Services
You can Add or Locate Common Services in this dialog box. Autonomy Registry, User, and Config Services are known as Common Services.
109
3. Select the appropriate Common Services option (see Table 8). Table 8 Use the Common Services options Common Services options
Use Common Services on another computer
If you use this option...

Go to Step 4. The installer uses common services installed on a different system. Common Services should be installed and running on the target system prior to selecting this option. The installer uses the remote Common Services to store and query the configuration information required for the installer. Go to Step 5. The installer installs the Common Services application on this machine. Installing Common Services and Common Services Client is mandatory for installation to proceed. Go to Step 5. The installer skips Common Services and other dependent components. Select this option if you want only runtime components such as LiveSite Display Services. Runtime components do not depend on Common Services.
Install Common Services on this computer
Skip, only runtime applications will be installed, upgraded/ reinstalled, or uninstalled
4. Click Next. The Use Common Services on Another Computer dialog box opens (see Figure 29).
110
Figure 29 Use Common Services on Another Computer

.
5. Type the Hostname and Port Number of the target computer and Click Next. The Select Installation Type dialog box opens. If the installation program does not detect any previously installed Autonomy Interwoven components, the Registry dialog box opens and it enables you to install new components only.
NOTE The Administration Console or ReportCenter cannot be installed together with the TeamSite upgrade. You have to install them separately after the TeamSite upgrade is complete.
6. Select Upgrade or re-install in the Installation Type dialog box and click Next. The Upgrade Recommendation dialog box opens. 7. Click Next.
111
The Upgrade Component Selection dialog box opens (see Figure 30). Figure 30 Upgrade Component Selection
The components available for upgrade appear. Components are enabled or disabled based on the availability of disk space and upgrade support. The installer automatically selects or clears the components and provides status messages as appropriate. 8. Select TeamSite and any other components you want to upgrade.
components to the list. 9. Click Next to upgrade the selected components. If you are upgrading from 7.x, go to Step 18 on page 118. The Administration Server Port dialog box opens. 10. Click Next.
112
The Database Type for Common Services dialog box opens (see Figure 31). Figure 31 Database Type for Common Services
11. Select the database type for Common Services, and click Next.
113
The Common Services Database Configuration dialog box opens (see Figure 32). Figure 32 Common Services Database Configuration
12. Type the following database configuration details:

Database driver files. Browse and select the database drivers for the
selected database type.

Database Server Name. Name of the server that hosts the database. Database Listen Port. Port used by the database. Database Name. Database name as assigned by the database
administrator.
User Name. Database user created during the pre-installation tasks. User Password. Database user password.
NOTE Separate multiple file paths with commas.
114
If the selected database type is Oracle RAC or Custom, type the database configuration details as follows:
JDBC database driver file (directory where JDBC database drivers are
located)
JDBCDriver Class JDBC URL
If you select Oracle RAC, type the JDBC URL in the following format:
jdbc:oracle:thin:@(DESCRIPTION= (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST=dbhost1)(PORT=1521)) (ADDRESS = (PROTOCOL = TCP)(HOST=dbhost2)(PORT=1521)) (FAILOVER=on) (LOAD_BALANCE=off)) (CONNECT_DATA = (SERVER=DEDICATED) (SERVICE_NAME =dbservice))) Username (ID of the database administrator) Password (database administrator password)
If the Database Connection is not successful, the Database Connection Failure dialog box opens. 13. Click Next.
115
The OpenDeploy Admin Username and Web Services connection information dialog box opens (see Figure 33). Figure 33 OpenDeploy Admin Username and Web Services connection information
Ensure that you add the Web Site Root Directory path in the allowedpath entry in odrcvr.xml file. 14. Click Next. You do not have to change any values in the dialog box because they do not affect the upgrade process. 15. Click Next.
116
The Database type for SitePublisher dialog box opens (see Figure 34). Figure 34 Database type for SitePublisher
The database type selected for CommonServices is selected by default. 16. Select No database and click Next.
117
The TeamSite Reporting Database Configuration dialog box opens (see Figure 35). Figure 35 TeamSite Reporting Database Configuration
The database text boxes are populated by default based on the details entered during the CommonServices database configuration. 17. Click Next to complete the database connection configuration for TeamSite Reporting. The Process Confirmation dialog box opens. 18. Click Install to upgrade and configure the selected components. If you are upgrading from 6.7.2, the Upgrade/Reinstall and Configuration Process Summary dialog box opens. If you are upgrading from 7.x, the Restart Confirmation dialog box opens. Go to Step 20. 19. Click Next to complete TeamSite upgrade. The Restart Confirmation dialog box opens. 20. Select Yes to restart your system now or No to restart later. Click Done. After the restart, the Final Configuration Confirmation dialog box opens.
118
Migrate TeamSite
To complete the post-restart configuration later, click Cancel. You must run the installer again to complete the configuration. 21. To start the post-restart configuration, click Next. The Final Configuration Summary dialog box opens. 22. Click Done. 23. Run the Dependency Migration tool. See Migrate Content to Support TeamSite Associations on page 123. 24. Run any other necessary migrations.
Migrate TeamSite
The different upgrade and migration paths are outlined in Table 9 and described in the following sections.
NOTE Starting with release 6.7.2, SitePublisher is included as part of TeamSite. SitePublisher was previously packaged as part of the LiveSite product, which included both a development environment component (SitePublisher) and a runtime environment component (LiveSite). Starting with LiveSite release 7.1, LiveSite and SitePublisher are no longer packaged together. LiveSite now includes only the runtime environment component, while SitePublisher is part of TeamSite.
Upgrade and migrate are defined as:
upgrade. You are running a TeamSite (and optionally LiveSite) version that is supported for upgrade. You can install directly over your earlier version. See Upgrade Paths on page 107 for a list of supported upgrade paths. migrate. You are running a TeamSite (and optionally LiveSite) version that is not supported for upgrade. You may be able to migrate your Content Store by performing a new installation of TeamSite and copying over your Content Store.
119
Table 9 Upgrade and migration paths Path

Upgrade from 6.7.2 SP2 or 7.x
Description
Perform a standard TeamSite upgrade. See Upgrade TeamSite on Linux, Solaris, or Windows on page 108. Run the Dependency Migration tool on the content store. See Migrate Content to Support TeamSite Associations on page 123
Upgrade from versions prior to TeamSite 6.7.2 SP2.
No direct upgrade is available from versions prior to TeamSite 6.7.2 SP2. Contact Autonomy Customer Support to upgrade from earlier versions prior to TeamSite.
Migration Paths
If you use a TeamSite version that is not supported for upgrade, you may be able to do a new installation of TeamSite and copy your existing Content Store and customized files into the new installation of TeamSite. This requires running a number of CLTs against your Content Store and otherwise updating information. A checklist of items is listed here.
NOTE Migration cannot be undone. If you may need to revert to your previous TeamSite release, back up your Content Stores, TeamSite roles files, and TeamSite configuration files and store them in a location that is not affected by the migration. If you do an in-place upgrade, you cannot revert to the previous version of TeamSite. In this case, you must reinstall TeamSite.
To use a new TeamSite installation with an old Content Store 1. Stop TeamSite Services. 2. Manually copy the Content Store (refer to https://support.interwoven.com/kb/ kb_show_article2.asp?ArticleID=55358). 3. Perform the TeamSite installation. 4. Installation procedure reboots server and restarts TeamSite. 5. UNIX only: Reset Content Store ownership to iwts as described in Non-root Support on page 122. 6. Stop TeamSite. 7. Remap local OS user/group ID info using iwidmap (see Resolve User/Group ID Information on page 126). 8. Map roles files to flexible roles format or configure LDAP using iwusermigrate (see Restructure Role Information on page 125).
120
Migrate TeamSite
9. Reboot server. 10. Verify role mapping is correct. Verify all user IDs are present. 11. Map user permissions roles on each branch using iwaccessmigrate (see Associate Roles with Branches on page 126). 12. Copy configuration files (see Update Configuration files on page 128). 13. Map permissions for custom menu items using migrate_customtk.ipl (see Update Customization Items on page 127).
Additional Migration Steps

This section provides procedures that you may require to complete the TeamSite upgrade or migration.
iwutild.cfg and rewrite.conf.template

1. Manually merge iwutild.cfg to add the latest entries. 2. When you upgrade TeamSite, the installer creates a rewrite.conf.template.example file, which you must reconcile with the existing .template file. Do one of the following actions:
If there are customizations in rewrite.conf.template, manually merge
the rewrite.conf.template.example file content into the existing rewrite.conf.template file. Ensure that you preserve your customizations.
If there are no customizations in rewrite.conf.template, rename the
rewrite.conf.template.example file to .template and overwrite the existing rewrite.conf.template file. 3. Run iwreset a and iwutildreset to apply the changes.
SitePublisher
If you have a previous version of SitePublisher when upgrading from TeamSite 6.7.x, to retain the customizations that you have made in the webtrends-resource-config.xml file, Autonomy recommends that you use the following procedure. To upgrade a 6.7.x version of SitePublisher 1. Back up the existing the webtrends-resource-config.xml file. 2. Upgrade to the current version of TeamSite. 3. Create the following directory structure, <livesite_customer_src>/ etc/conf/livesite/resources, if it does not exist.
121
Copy the <bean> element from the backup copy of webtrends-resource-config.xml into <livesite_customer_src>/ etc/conf/livesite/resources/ customer-teamsite-resource-config.xml. 4. Run build.bat or build.sh.
Eventsubsystem
Eventsubsystem migration involves making sure that any events that are already part of OpenJMS are consumed by the subscribers. The engine can be upgraded and any new events will be part of the new ActiveMQ engine. To ensure all the messages are consumed 1. Prior to upgrade, shutdown the publishing of events to the eventsubsystem. To do this, edit the iw_bridge_cfg.xml file and comment the <logFile/> sections. 2. Check the database to ensure that the eventsubsystem persists data to (the database configuration information can be found in jmsconfignew.xml). Check the message_handles table and ensure that there are no rows in that table. This means that all messages that have been sent so far have been consumed. 3. Upgrade to the current version of TeamSite. 4. After upgrading, check the iw_bridge_cfg.xml file and uncomment the <logFile/> sections. Additional configurations in the file may have been commented out earlier; they should not be uncommented. 5. Restart TeamSite services and ensure that all the events are propagated to the subscribers.
Non-root Support
In TeamSite 6.7.1, the iwserver process was changed to run as the iwts user instead of root on UNIX platforms. All the files and directories in the Content Store and some files under iw-home must be accessible by iwts. During the TeamSite installation, the migrate_non_root script runs to walk the Content Store and change ownership and permissions on the Content Store files to allow iwts user access. This only affects Content Store permissions on UNIX; TeamSite users cannot see files owned by iwts. The script also changes ownership and permissions on the appropriate files in iw-home. After installation, if you do not have a 6.7.1 Content Store, you must reset permissions and ownership of the store or you receive an error. Run the following UNIX commands to reset permissions and ownership:
su - root
122
Migrate TeamSite
iwtgethome/private/bin/walkArchive.pl -p /app/interwoven/ iw-old-store NOTE The above tool completes the changes in a single pass (twice as fast), and sets the file and directory permissions correctly.
CAUTION Do not run the migrate_non_root script, which is invoked by the installer, to reset permissions on the store. This script also modifies files in iw-home and elsewhere.
Running the migrate_non_root script during installation or running the UNIX chown and chmod commands on the Content Store may be a moderately long process. It can take a few hours to walk all the Content Stores. Starting in TeamSite 6.7.1 SP1, you can use a script named ts-home/private/bin/ walkArchive.pl, which does the equivalent of chown and chmod steps at a much faster pace. Refer to the following support article for additional information: https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=57393
Migrate Content to Support TeamSite Associations

The Dependency Migration tool enables the TeamSite Associations feature for Sites, Pages, DCRs, and other assets linked from those entities. TeamSite associations are used by the Find Related Files feature, the Publish LiveSite Content workflow when attaching dependencies, and by localized sites. To ensure that these features work properly after installing TeamSite, you must run the Dependency Migration tool to migrate all workareas. You must migrate all workareas that contain DCRs to ensure that Find Related Files and localized sites work. Autonomy recommends migrating a single workarea (per branch, if possible) and then having all other workareas perform a get latest. This recommendation requires that all users submit their in-progress changes. If this is not possible, all workareas can be migrated individually. The Dependency Migration tool is located at:
ts-home\install\livesite\install_scripts\ iw_migrate_dependencies.ipl
Log files generated by the script are stored in:

ts-home\install\livesite\install_scripts\ iw_migrate_dependencies.log
123
NOTE If your iw-store is older than TeamSite 7.0, you must run iw_migrate_dependencies.ipl.
The tool has the following syntax:

iw_migrate_dependencies.ipl -s|-w workarea-path
where,

-s migrates all sites across all stores (migrate sites) -w migrates DCRs in a specified workarea (migrate workarea DCRs)
NOTE The -w parameter can only be used on DCRs that include the extended attribute TeamSite/Templating/DCR/Type. If the DCR does not include this attribute, dependencies are not created from the asset.
workarea-path is the workarea vpath for migrating DCRs. This option is required for workarea migration. For example, /default/main/mybranch/ WORKAREA/myarea.
To upgrade associations using the Dependency Migration tool 1. Run the migration tool with the -s option to migrate all workareas that contain sites. 2. Run the migration tool with the -w option for each workarea that contains DCRs. 3. After the workarea is migrated, submit the files. Typically only one workarea per branch is migrated, and then the other workareas can be updated using Get Latest. The dependency migration can take significant time depending on the migrated content. You can monitor the progress by examining the iw_migrate_dependencies.log file.
NOTE TeamSite only supports a single Workarea per branch. The Dependency Migration tool does not by default migrate more than one Workarea because of this condition; however, you can migrate these workareas by using the Migration tool's -w option. If you need to use multiple Workareas, contact Autonomy Customer Support.
124
Migrate TeamSite
Restructure Role Information

Prior to TeamSite 6.7.0, user and role information was defined in either .uid files (author.uid, editor.uid, admin.uid, and master.uid) or as attributes in LDAP, when TeamSite is configured to use the ldap_roles key in iw.cfg. In TeamSite 6.7 and later, user information is read and recorded in the iw-home/ conf/roles/tsusers.xml file. If role information is in LDAP, the user list is recorded in iw-home/conf/roles/tsldapuserscache.xml; when TeamSite is running, the tsldapuserscache.xml file is updated regularly to keep it synchronized with LDAP. Role-specific information is associated with particular branches in TeamSite 6.7 and has been moved to the Content Store. Each branch now contains a list of users and groups and the roles they have on that branch. The only role information read from tsusers.xml or tsldapuserscache.xml is master access. The iwusermigrate CLT is used to process uid files and produce tsusers.xml or creates tsldapuserscache.xml from LDAP. During an upgrade installation of TeamSite, the installer automatically runs the iwusermigrate CLT to create the tsusers.xml or tsldapuserscache.xml file. In a fresh installation, iwusermigrate CLT needs to be run manually. Before running the CLT, make sure to copy over uid files from your current installation to iw-home/conf/roles directory. If your current TeamSite installation is configured to keep login role information in LDAP, before running the iwusermigrate CLT, copy the [authentication] section of iw.cfg from your current TeamSite installation to the new installation. To verify that iwusermigrate ran successfully, run the command: $ iwhome/iw-perl/bin/iwperl -ne "/name=/" iwhome/conf/roles/ tsusers.xml If you use LDAP, run the command: $ iwhome/iw-perl/bin/iwperl -ne "/name=/" iwhome/conf/roles/ tsldapuserscache.xml The output of the command is a list of all TeamSite users. Verify that the list is complete. Alternatively, when the server is started later, you can run the command iwuseradm list-users -t to get a list of all TeamSite users in the system.
125
NOTE Verify that the user list is complete before going to the next upgrade step. If the list is not complete, the subsequent iwaccessmigrate step will not have sufficient data to correctly associate users with particular roles on each branch.
Resolve User/Group ID Information

The iwidmap CLT resolves user/group ID problems. If you are doing a fresh installation and copying the Content Store over to the target system, you may need to remap some local OS user/group id information. Use the iwidmap CLT to perform the remapping. Refer to the following support article for additional information: https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=49980
Associate Roles with Branches

The iwaccessmigrate CLT associates users with particular roles on each branch. Since TeamSite 6.7.0, the TeamSite access model was enhanced to allow users to have different roles in different branches instead of logging in with one global role (as specified in the uid files). The iwaccessmigrate CLT migrates to the new access model. The iwaccessmigrate CLT needs the following information to successfully migrate to the new model. If the information is not available (or is not set up correctly), an incorrect migration can occur, which results in subsequent permission problems. 1. List of all TeamSite users and their highest role (from uid files or LDAP). TeamSite roles in the old model were hierarchical. Master is the highest role, followed by admin, editor, and author, in that order. 2. List of all groups a user is a member of. The iwaccessmigrate CLT retrieves this information by making calls to the iwserver process. The server builds this information when it starts. 3. Owner and group-for-sharing attribute of all the branches and workareas across all stores. The iwaccessmigrate CLT retrieves this information by making calls to the iwserver process. 4. The file-system permission of the branch and workarea root directories of all branches and workareas of all stores. The iwaccessmigrate CLT retrieves this information by making calls to the iwserver process. To ensure item 1 is in the correct state, verify that the iwusermigrate CLT was run properly. See Restructure Role Information on page 125 for more details.
126
Migrate TeamSite
When the server is started with item 1 in the correct state, it builds the membership information of all TeamSite users in memory. To verify item 2 is in the correct state, you can choose a sample group of users and run the command iwgroup list-groups-of-user -recurse user to check if the membership information is correct. To ensure items 3 and 4 are in the correct state, verify that

The Content Store has been copied over properly. The iwidmap CLT changes have been made, if needed (see Resolve User/ Group ID Information on page 126). All stores are activated. If a store is inactive, iwaccessmigrate exits by asking you to activate the store. If you are really sure that the inactive stores are no longer used, then specify the iwaccessmigrate -o option to override the active store check.
NOTE If your upgrade path requires the iwmigrate step to be run, perform the iwmigrate step after the iwaccessmigrate step (see Restructure Role Information on page 125).
After you verify that these items are in order, you can run the iwaccessmigrate CLT. When running the CLT, Autonomy strongly recommends that you first run it with the -m option. This option only creates a manifest file, iw-home/local/ logs/accessresults.xml and does not apply the changes. Review the manifest file to verify that users are assigned correct roles to branches they are currently using. After you verify that the contents of the accessresults.xml file are correct, you can feed the manifest file back to the iwaccessmigrate CLT and apply the changes this time. Use -f manifest-file option for this. If you need to rerun iwaccessmigrate, refer to the following knowledge base article for detailed instructions: https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=57148
Update Customization Items

In TeamSite 6.5 and earlier, it was possible to restrict custom user interface links (menu items and tabs) and operations that invoke non-Autonomy functionality based on the user's login role. This restriction was specified by entering the operation IDs corresponding to the custom links in the roles_custom.xml in the custom toolkit. In TeamSite 6.7 and later, since there is no longer the concept of a login role, role restrictions on custom menu items and tabs are now made by entering their operation IDs in userops_custom.xml.
127
The migrate_customtk.ipl CLT is used to populate the userops_custom.xml file, reading it from roles_custom.xml. Run the command iw-home/install/migrate_customtk.ipl. For backward compatibility, TeamSite supports the legacy method of specifying role restrictions for custom menu items and tabs for the predefined roles of Author, Editor, Administrator, and Master. This allows you to defer migrating already defined custom menu items and tabs to the new permission scheme if you are working with just the default roles. Refer to the TeamSite User Interface Customization Guide for more details.
Update Configuration files

You must manually migrate changes in configuration and customization files from the original installation. In some cases, such as for iw.cfg, you may need to merge changes made in the source file into the destination file, instead of overwriting it. Exactly which files need to be copied or merged differs from one installation to another, because of variations in the level of configuration and customization among customers. In most cases, this process should be done manually and with care, and you should compare the source file with the destination file, if it exists, so that you do not overwrite new configuration information at the destination site.
Manage Users through the Administration User Interface

In Administration Console, Master users can administer not only TeamSite, but also the co-located OpenDeploy Base Server. In order to administer the OpenDeploy server, master users should have od-admin role in OpenDeploy. When users are added through Administration Console, they are also added to TeamSite with OpenDeploy specific privileges. Refer to the TeamSite Administration User Guide for more information on adding users. However during an upgrade from versions prior to TeamSite 7.1, the users in TeamSite may not have OpenDeploy privileges and cannot access deployment-related functionality through Administration Console. However, there is a bootstrap user who is already a TeamSite master, and has od-admin role. This user can grant OpenDeploy privileges as necessary to other users through Administration UI. If there are no users who are TeamSite masters or have od-admin role, the administrators need to grant OpenDeploy admin privileges to specific users through iwodauthorize command line tool available in the OpenDeploy installation directory. Refer to the OpenDeploy Administration Guide for more information. You can also perform the same task through OpenDeploy Administration user interface.
128
CHAPTER 6
Configure TeamSite
This section describes how to configure TeamSite after you install or upgrade.

Configure Web Servers Configure TeamSite Clients Configure MediaBin Connector for Legacy MediaBin Servers Load Content Files The iwui User
Configure Web Servers

This section describes how to configure your systems Web server after you install or upgrade TeamSite. Configuration procedures for the following Web servers are included:

Microsoft Internet Information Server (IIS) 5.0 Apache Web Server IBM HTTP Server
This section contains information about the following topics:

Run the IIS Configuration Script Manually Autonomy Web Server Port Number Configure the iw-mount Alias
129
Chapter 6 Configure TeamSite
Configure CGI Programs Enable Server-Side Include Requests Stop and Restart the Web Server Redirect NSAPI HTTPS Requests Redirect to an Index Page Where to Go From Here
Run the IIS Configuration Script Manually

If you use Windows, 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 systems Y: drive is up. The following command configures IIS to run with TeamSite:
>ts-home/iw-perl/bin/perl ts-home/install/tspostreboot.pl ts-home IIS
Autonomy Web Server Port Number

You must provide the Autonomy 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 ts-home/etc/iw.cfg as follows (assuming the default values):
[iwwebd] http_port=80 https_port=443
NOTE If port 443 is already in use, specify another port number.
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.)
130
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 ts-home/etc/iw.cfg as follows (assuming the default value of 81):
[iwproxy] customer_webserver_port=81
Configure the iw-mount Alias

The Web server uses the iw-mount alias to access the NFS server mount point (UNIX) or default location of the TeamSite Intelligent File System volume (Windows). 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 use. Configuration details are in the following sections.
Configure iw-mount for IIS

If you use 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. 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. 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.
Configure iw-mount for Apache

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

If your UNIX-based system will execute CGI programs in TeamSite workareas, you must edit the httpd.conf file as described in this section. After making the required edits, you must restart the Web server for the changes to take effect. If you reinstall your Web server or lose your automatically modified configuration files, you can refer to the installation log to duplicate the changes previously made. Add the following section to the obj.conf file:
<Object ppath="/.iwmnt/*/cgi-bin/*"> ObjectType fn="force-type" type="magnus-internal/cgi" Service fn="send-cgi" </Object>
To configure CGI programs for Apache 1. Add the ExecCGI directive to the Directory section in the httpd.conf file as shown here:
<Directory "/.iwmnt"> Options Indexes FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all </Directory>
2. Add the following section:

<Location ~ "/iw-mount/.*/cgi-bin/.*"> SetHandler cgi-script </Location>
Enable 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 SSIs by specifying that it parse .shtml files.
132
Install the Redirector Module for IIS

If you choose to enable VisualPreview for SSIs, you must install the TeamSite redirector module as described in the following procedure. The installation steps vary depending on the type of Web server you use. To install the redirector module for IIS 1. Click Start > Run and type C:\WINNT\system32\inetsrv\iis.msc. The Microsoft Management Console opens. 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. 5. In the menu, select Properties. The Default Web Site Properties dialog box opens. 6. Click the ISAPI Filters tab, then click Add. The Filter Properties dialog box opens. 7. In the Filter Name text box, type iwrewrite. 8. Click Browse and select the iwproxy_isapi.dll file in the ts-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.
Install the Redirector Module for Apache 1.3.x

If you use an Apache 1.3.x Web server, there are two different types of redirector modules available. The type of module you use depends on your configuration and is determined by the procedure that follows. Complete the next procedure to install and configure the appropriate redirector module for Apache 1.3.x. To install and configure the appropriate redirector module for Apache 1.3.x 1. Determine if mod_so is enabled by running the following directive: # apache-home/bin/httpd -l 2. Look for mod_so.c in the output, then do one of the following actions:
If mod_so.c is in the output, go to Step 3. If mod_so.c is not in the output, run the following configuration directive to
configure and build Apache with mod_so:
133
# ./configure --enable-shared=max --prefix=// path_to_apache_home # make # make install
3. Determine if your Apache Web server has a mod_ssl patch by running the following command: httpd -V 4. Look for -D EAPI in the output.
If the output contains -D EAPI, use the mod_iw_ts_rewrite_eapi.so
module.
If the output does not contain -D EAPI, use the
mod_iw_ts_rewrite.so module. 5. Edit the LoadModule section of the httpd.conf file as follows:
If you use the mod_iw_ts_rewrite_eapi.so redirector module: LoadModule iw_ts_rewrite_module ts-home/lib/ mod_iw_ts_rewrite_eapi.so If you use the mod_iw_ts_rewrite.so redirector module: LoadModule iw_ts_rewrite_module ts-home/lib/ mod_iw_ts_rewrite.so NOTE On IHS servers, the system fails if the redirector module mod_iw_ts_rewrite is not loaded as the last module in the configuration. To avoid this, add the following lines as the last entry in the httpd.conf file: LoadModule iw_ts_rewrite_module ts-home/lib/ mod_iw_ts_rewrite.so AddModule mod_iw_ts_rewrite.c
6. Enable relative SSIs in .shtml files as follows: a. Add the Includes statement to the Directory section of the httpd.conf file as shown in the following example:
<Directory "/.iwmnt"> Options Indexes FollowSymLinks ExecCGI Includes AllowOverride None Order allow,deny Allow from all </Directory>
b. Add or uncomment the <If Module mod_mime.c> section in the httpd.conf file as follows:
134
<If Module mod_mime.c> AddType text/html .shtml AddHandler server-parsed .shtml </IfModule>
7. Edit the end of the AddModule section of the httpd.conf file as follows: AddModule mod_iw_ts_rewrite.c
Enable Server-Side Include Requests on Apache 2.0.x or 2.2.x

For Apache 2.0.x or 2.2.x, use a combination of mod_a2_iw_ts_vpath and a mod_rewrite configuration to virtualize SSI and read proxy configurations from the iw.cfg file. Perform the following procedure to enable Server-Side Include Requests on Apache 2.0.x or 2.2.x. To enable server-side Include requests on Apache 2.0.x or 2.2.x 1. Install Apache 2.0.x or 2.2.x 2. Change directory to <apache_install>/bin 3. Build mod_a2_iw_ts_vpath.so by running the following command:
-./apxs -i -a -c <ts-home>/src/apache/mod_a2_iw_ts_vpath.c
4. Run the following command:

<ts-home>/iw-perl/bin/iwperl /<ts-home>/src/apache/ mk_mod_rewrite_conf.ipl > <apache-install>/conf/ssi.conf
5. Open httpd.conf from <apache_install>/conf a. Make sure the following line is available in the LoadModule section
LoadModule a2_iw_ts_vpath_module <path-to-mod_a2_iw_ts_vpath.so>
b. Add the following two lines.

AddType text/html .shtml AddHandler server-parsed .shtml
c. To enable TS preview feature add the following lines at the end of the httpd.conf: For Solaris:
<Directory "/.iwmnt"> Options Indexes FollowSymLinks ExecCGI Includes AllowOverride None Order allow,deny Allow from all </Directory> Alias /iw-mount/ /.iwmnt/
135
For Linux:
<Directory "/iwmnt"> Options Indexes FollowSymLinks ExecCGI Includes AllowOverride None Order allow,deny Allow from all </Directory> Alias /iw-mount/ /.iwmnt/
d. Further append the following lines to include the path to the rewrite module (as compiled in Step 4):
RewriteEngine on #RewriteLog logs/rewrite.log #RewriteLogLevel 9 Include conf/ssi.conf You can optionally turn on/uncomment the following two settings: #RewriteLog logs/rewrite.log #RewriteLogLevel 9
6. Perform an iwreset ui 7. Restart apache -- apachectl start 8. Create test.shtml and add the following content:
<html> <head> <title>SSI Test Page</title> </head> <body>  after </body> </html>
9. Create inc.txt and add the following file:

inc.txt
The inc.txt file can be in the WORKAREA root or in a sub-directory. 10. Populate test.shtml WORKAREA/wa 11. Click test.shtml and make sure SSI works.
Server-Side Includes for IHS (AIX only)

The procedure for setting up SSIs for IHS on AIX is the same as setting them up for Apache except for one item.
136
IHS must have runtime linking enabled (-brtl). You can determine whether IHS has been linked with -brtl by using the command:
$ dump -H httpd | grep librtl
If you see a line in the output containing librtl.a, IHS has been linked with the -brtl option. If not, you must relink IHS. Use the following commands to relink the httpd in http_server.base.rte 1.3.19.0.
# # # # # /usr/HTTPServer/bin/apachectl stop cd /usr/HTTPServer/bin mv httpd httpd.orig ld -o httpd -bexpall -brtl httpd.orig -lpthread -lC -lc /usr/HTTPServer/bin/apachectl start
Web Server Plug-ins and VisualPreview

The VisualPreview functionality in ContentCenter interfaces 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 (Windows) or your content Web server (UNIX) that sets the x-iw-ts-vpath response header is distributed with TeamSite if you use Windows or is available as follows if you use a UNIX-based system:

If you use Apache, the required module source code is distributed with TeamSite. If you use another Web server, you need to create a custom plug-in that sets the x-iw-ts-vpath header. That response header must contain the URL-escaped, natively encoded vpath that corresponds to the current request.
137
Detailed information about using these plug-ins is in the following sections. ISAPI Plug-ins The existing ISAPI (IIS) Web server plug-in implements the x-iw-ts-vpath response header. To install it, see Install the Redirector Module for IIS on page 133. IBM HTTP Plug-ins The plug-in for IBM HTTP Server 2.0 requires the installation procedure described in this section. Autonomy also recommends using an optional technique for handling SSIs. This procedure is documented in the following Knowledge Base article (the instructions refer to Apache, but are valid for IBM HTTP):
https://support.interwoven.com/kb/ kb_show_article2.asp?ArticleID=51890
To install the IBM HTTP plug-in 1. Copy mod_a2_iw_ts_vpath.dll from ts-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. 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 ts-home/src/apache/. To compile them, use the apxs utility included with your installation of Apache. There may be precompiled binaries available from Autonomy Customer Support for common configurations (for example, Apache 1.3.28 with mod_ssl on Solaris 2.8).
138
Custom Plug-ins If you use a content Web server other than IIS, HTTP, Apache, 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.
Stop and Restart 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 /icons/=/icons/ /images/=/multimedia/img/
No trailing slash allowed Trailing slashes allowed
After ensuring that all _docroot trailing slashes in the [iwproxy_remap] section are deleted, stop and restart your Web server.
Redirect 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.
139
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 servers NSAPI plugin are redirected to the Web daemon. The Web daemon then sends the requests to the non-secure TeamSite server just as it would any request originating from the browser. For example, if the NSAPI plugin on the secure server receives an HTTPS request for a file in a 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 display a warning that the request is being sent to an insecure document. This is normal behavior. If you see such a message, click OK to continue.
Redirect 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 (see Figure 36).
140
Configure TeamSite Clients
Figure 36 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, refer to the TeamSite User Interface Customization Guide.
Where to Go From Here

After completing the Web server configuration, do one of the following things, depending on your operating system:

UNIX. Continue the initial configuration by creating at least one TeamSite client as described in Configure TeamSite on page 129. Windows. Continue the initial configuration by creating at least one TeamSite client as described in the Configure TeamSite on page 129.

After installing TeamSite and configuring your Web server, you need to configure at least one TeamSite client. You can use either the ContentCenter interfaces or the file system interface for client access.
Access TeamSite Using ContentCenter

You can access ContentCenter Standard and ContentCenter Professional 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 (refer to the TeamSite Administration Guide). If you do not add users or change your own user status, you can log in using the host systems root (UNIX) or Administrator (Windows) user name and password for all user roles.
141
To access TeamSite from a client computer 1. Open your Web browser and type 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 can bookmark this URL for future use. The TeamSite login dialog box opens. 2. Type your user name and password. By default, TeamSite accepts the host systems root (UNIX) or Administrator (Windows) user name and password for all user roles. 3. Click Login.
Install 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. The client system associates different applications with different file types, so that when you double-click a file, it knows what application to use to open it. You 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 need to set preferences for HTML files in Local File Manager. 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 opens. 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 opens. 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.
142
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 appears in the File Types window. 6. Click OK.
Access TeamSite through the File System Interface

Using the file system interface, you can manage your content in TeamSite as a shared network volume on Windows, or as a mounted drive on the network on UNIX. 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 you to use link checkers and scripts that need to access or create files. In addition, most TeamSite operations can be performed from the command line on Windows or a UNIX command-line interface.
CAUTION The file system interface should not be used for localized workareas. Doing so results in the loss of associations required for localization maintenance operations. For more information on localization, refer to the ContentCenter Professional User Guide.
Mount Windows Clients

The first time you access your TeamSite server from a Windows client, you may need to mount or access the TeamSite server as a shared volume/network drive depending on whether it is on Windows or a UNIX machine. The next procedure describes how to access TeamSite using Network Neighborhood on Windows or on UNIX with:

a networked computer using an NFS client a networked computer with FTP
To access TeamSite from Windows, through Samba on UNIX, use Windows Explorer or Network Neighborhood on Windows to locate the TeamSite server. On Windows, 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.
143
To mount the TeamSite server as a networked drive in Windows 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 IWServer to mount the TeamSite server as a networked drive. To mount the TeamSite server as a networked drive in UNIX 1. Click Start > Search > For Files or Folders. 2. Select the Search for other items: Computers option. 3. Type the name of the TeamSite server in the Computer Name text box. 4. Click Search Now. 5. Double-click the name of the TeamSite server when it appears in the list. The server window opens. 6. Double-click the TeamSite mount point directory (usually iwmain) and navigate through the TeamSite directory structure to find your workarea. Within your workarea, you can edit, move, or rename TeamSite files as you would any other files. You can also drag and drop files and directories from your local hard drive to directories in your workarea.
Create Desktop Shortcuts

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 for your Desktop. To create a Desktop shortcut Right-click the workarea or commonly used directory and select Send To > Desktop (create shortcut). The shortcut appears on the Desktop.
Troubleshoot Windows Networking

If your Windows clients cannot find the TeamSite server through Windows Networking, see if you have NetBEUI installed. If so, uninstall it if possible with the next procedure. To uninstall NetBEUI if Windows clients cannot find the TeamSite server through Windows Networking 1. Select Start > Settings > Control Panels.
144
2. Double-click the Network 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 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 uses TCP/IP to send and receive network transmissions. You can now 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, however, this solution is not as reliable because it might be upset as network cards are changed and protocols are added and removed.
NFS Clients
UNIX: If you use an NFS client, follow your programs setup instructions to mount / iwserver on the TeamSite server as a networked drive. If you can, you should modify the client configuration to NFS Version 2 and turn off NFS locking (sharing) on the client. If you do not turn off locking, operations might freeze for long periods of time.
FTP Clients
UNIX: If you use an FTP client, follow your programs setup instructions to install the software. Log in to the TeamSite server using your UNIX login and password and navigate to your workarea, located at:
/iwmnt/default/main/branchpath/WORKAREA/workareaname
Macintosh Clients
NOTE The following instructions are for Classic MacOS (before version 10.0).
145
To use the TeamSite file system interface for Apple Macintosh, you need to have an AppleShare server set up for the server that is running TeamSite. To use the TeamSite file system interface for Macintosh 1. In the Chooser, select AppleShare. 2. Select the name of the TeamSite server. Click OK. 3. If you are asked for your user name and password, type your TeamSite user name and password, and click OK. 4. Select the items you want to use, and click OK. The TeamSite server appears on your desktop. For additional AppleShare server recommendations, contact an Autonomy sales representative.
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 user name and password. If you have UNIX clients that will access 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.
146
Configure MediaBin Connector for Legacy MediaBin Servers
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 Load Content Files on page 149. If you intend to connect TeamSite to MediaBin 7.x or earlier, first follow the procedures in Configure MediaBin Connector for Legacy MediaBin Servers on page 147.
Configure MediaBin Connector for Legacy MediaBin Servers

By default, the TeamSite 7.3.2 MediaBin connector supports connections only to MediaBin 8.0.3 or newer. To connect to MediaBin 7.x or earlier, you must restore an earlier version of the connector. You need the files that you backed-up before upgrading or migrating (see Files to Back Up Before Upgrading or Migrating on page 108). To restore the legacy MediaBin connector
NOTE In this procedure, original refers to the file copy that you backed-up before upgrading or migrating TeamSite. New refers to the file copy that was installed with the upgrade or migration.
1. Ensure that the TS.lic file in <ts-home>/etc does not have Rich Media Management enabled. If it does, you must replace it with the backed-up original file or contact Autonomy Customer Support for a license file with RMM disabled. If you replace the new license file, for it to take effect you must run the command <ts-home>/bin/iwreset 2. Back up the new ecmconnector.tk.war file residing in <ts-home>/ private/lib/content_center/ecmconnector.tk.war. 3. Copy the original ecmconnector.tk.war file into the directory, overwriting the new file to preserve permissions.
147
NOTE Autonomy recommends that you also back up the restored ecmconnector.tk.war file, because future TeamSite updates might overwrite it. In the event of the file being overwritten, repeat the above procedure using the backup file.
4. Cd to <ts-home>/install and run the following command:

install_webapps -f content_center
5. Copy the original files to the following locations:

iwov_import_mediabin.pm. Save to <ts-home>/iw-perl/
vendor/lib/TeamSite/PT
iwov_mediabin_param.pm. Save to <ts-home>/iw-perl/vendor/
lib/TeamSite/PT
the ecm directory. Replace the directory at <ts-home>/examples/
Templating/templatedata/ecm To use the legacy MediaBin connector, you must enable and configure the legacy settings. Refer to the TeamSite Administration Guide for instructions.
Configure MediaBin Workflows

To use a legacy MediaBin server, you must also modify the workflow settings. MediaBin 4.x does not support the Get Latest MediaBin Assets feature and therefore the Update MediaBin Assets workflow. You must remove this workflow from the TeamSite 7.3.2 configuration to use MediaBin 4.x. Both MediaBin 4.x and 7.x do not support importing multiple files at one time, and therefore the Import MediaBin Assets workflow. You must remove this workflow from the TeamSite 7.3.2 configuration to use MediaBin 4.x or 7.x. To configure workflows for MediaBin 4.x 1. In the Admin Console, click the Configurations tab and select available_templates.cfg. 2. Download and edit the file to remove the Import MediaBin Assets and Update MediaBin Assets workflows. 3. Save and upload the file. To configure workflows for MediaBin 7.x 1. In the Admin Console, click the Configurations tab and select available_templates.cfg.
148
Load Content Files
2. Download and edit the file to remove the Import MediaBin Assets workflow and change the Update MediaBin Assets workflow to:
<model debug=false active=true filename=Update_MediaBin_Assets name=Update MediaBin Assets> <allowed> <and> <vpath-regex regex=^(//[^/]+)?/default/main.*/> </and> </allowed> </model>
3. Save and upload the file. 4. Replace the Update MediaBin Assets workflow model and configuration files with the original files that you backed up before installing TeamSite.
Load 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. Populate TeamSite with your content using the following procedures. Steps for each procedure are in the following sections.

Create a Content Store Create a Subbranch Create a Workarea Populate the Initial Workarea Submit Files to the Staging Area Publish an Edition
The procedures in this chapter use the ContentCenter Professional interface.
Create 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.
149
Content Store Overview

The Content Store, called the backing store in older versions of TeamSite, is a large directory structure created by the TeamSite installation program that contains TeamSite files and metadata. By default, the Content Store is located in /local/iw-store. Up to eight Content Stores are supported for each TeamSite server. These Content Stores can be located on different file systems, local to the TeamSite server machine. 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 Define Content Stores in the iw.cfg File on page 151. TeamSite Content Stores support the following file objects:

Files Directories Symbolic links (UNIX)
Create 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.
150
Load Content Files
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 Create Content Stores with a CLT on page 154. Editing the iw.cfg file defines Content Stores with entries in the [iwserver] section of the iw.cfg file. This procedure:

Accepts multibyte characters for the store name (though the path to the store must use ASCII characters). Creates the new Content Store in any location. Allows you to add a descriptive comment to the Content Store. This comment appears when the active Content Stores are listed from the command line or display in the TeamSite user interfaces. Must be activated by using the iwstoreadm CLT with the -a option.
Another alternative is to use the iwstoreadm CLT, which creates and activates new Content Stores when issued with the -a option. This procedure:

Accepts ASCII characters for store names. Creates the new Content Store in the default location (typically /local/ iw-store). Does not allow for a descriptive comment to be added to the Content Store.
Define Content Stores in the iw.cfg File The advantages of defining Content Stores in the iw.cfg file include the ability to use multibyte characters in store names and to locate the Content Store in a directory other than /local/iw-store. User-defined Content Stores that are named using multibyte characters must have a corresponding entry in the iw.cfg file. While the name of the Content Store can be defined in multibyte characters, the Content Store location must be defined using ASCII characters. All Content Store data is stored in UTF-8 encoding. To create Content Stores defined in the iw.cfg file 1. For your operating system, ensure that:
UNIX: You are logged in as the user root and that root has the Master role
enabled in iw-home/conf/roles/tsusers.xml
Windows: 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 the following location:
151
UNIX: /etc Windows: ts-home\etc
3. If you use 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 fileit must be the first line or it will be ignored.
[iwcfg] encoding=locale_name
where locale_name is one of the following locales:

iso-8859-1 (German on UNIX) euc-jp (Japanese on UNIX) shift-jis (Japanese) cp1252 (French or German on Windows)
For example:
[iwcfg] encoding=shift-jis NOTE The locale entry must match the encoding of your text editor. Refer to the TeamSite Administration Guide for details about text editor encodings.
4. Append the following entry to the [iwserver] section to define additional Content Stores:
store_directory_store_name=absolute_path_to_backing_store
For example:
store_directory_salesAsia=/local/salesAsia NOTE The absolute_path_to_backing_store must be in ASCII while the store_name and the optional descriptive_comment (described in Step 5) can be in high-ASCII or multibyte characters.
5. Optionally, add a comment to the [iwserver] section below the Content Store you just defined:
store_comment_store_name=descriptive_comment
For example:
store_comment_salesAsia=Store for Demo
The completed entry, should look like this:
152
Load Content Files
[iwserver] existing iwserver entries store_directory_salesAsia=/local/salesAsia store_comment_salesAsia=Store for Demo
6. Save and close the iw.cfg file. 7. Run the iwreset CLT to have the TeamSite server read the changes to the iw.cfg file. 8. Run the iwstoreadm CLT with the -a option to create the newly defined Content Store: % iwstoreadm -a salesAsia (UNIX) > iwstoreadm -a salesAsia (Windows) The iwstoreadm CLT checks the iw.cfg file to see if a store_directory or store_comment entry exists, when it finds these entries, their definitions are used to create the Content Store. The system then activates and mounts the new Content Store. 9. Run the iwstoreadm CLT with the -l option to list all active Content Stores: % iwstoreadm -l (UNIX) > iwstoreadm -l (Windows) The system displays the following information:
UNIX
:
Name
default salesAsia
Store Directory
local/iw-store/ default /local/salesAsia
ID
0x64 0x65
Comment
Store for Demo
Windows:
Name
--default salesAsia
Store Directory
--------------/local/iw-store/ default /local/salesAsia
ID
-0x64 0x65
Comment
-------
Store for Demo
153
NOTE You can repeat the procedure to create any number of Content Stores, but you can only have eight active at one time. When using multiple Content Stores, you cannot relocate Content Stores (iw-store) by editing the /etc/ defaultiwhome file. (UNIX) You can edit the store_directory_storename entries to move Content Stores defined in iw.cfg.
Create Content Stores with a CLT The next procedure describes the creation of Content Stores from the command line with iwstoreadm. It also describes viewing the newly created Content Stores in the command window. To create content stores from the command line 1. For your operating system, ensure that:
UNIX. You are logged in as the user root and that root has the Master role
enabled in iw-home/conf/roles/tsusers.xml
Windows. 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 (UNIX) > iwstoreadm -a store1 (Windows) store1 is created in /local/iw-store, mounted, and activated. 3. Type the following command to list the active Content Stores: % iwstoreadm -l (UNIX) > iwstoreadm -l (Windows) The following list appears for: UNIX: Name
---default store1
Store Directory
--------------/local/iw-store/default /local/iw-store/store1
ID
-0x64 0x65
Comment
-------
154
Load Content Files
Windows: Name
---default store1
Store Directory
--------------C:\iw-store\default C:\iw-store\store1
ID
-0x64 0x65
Comment
-------
View Content Stores

1. To view a Content Store in ContentCenter Professional, select Content Store (see Figure 37). Figure 37 Content Store
2. Click Properties to view the properties of the store (see Figure 38).
155
Figure 38 Content Store Properties
All Content Stores (including the system-generated default) contain a Main branch that contains a staging area, edition, and workarea (see Figure 39).
156
Load Content Files
Figure 39 Content Store Main branch
Create a Subbranch
Autonomy 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 use 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 branchesthe 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 with 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 appears in the right pane:
157
a. Type the name of the branch in the Name text box. avoid using spaces or the following invalid characters in the branch name: \ / : * ? " < > | Avoid naming 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 text box) to the owners name. d. If you want this branch to have multiple Administrators, select Add Group in the Sharing text box and type the name of the group to administer this branch in the Group box. The Administrators of this branch can create workareas and subbranches. For more information on administrator privileges, refer to the TeamSite Administration Guide. e. Select the type of locking to be used on this branch. f. In the Based On text box, type 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 contains 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 (refer to the TeamSite Command-Line Tools guide for details).
Create 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 appears in the right pane: a. Type the name you want to give the workarea in the Name text box. Avoid using spaces and punctuation characters in workarea names. Workarea names should consist only of alphanumeric characters, hyphens, and underscores.
158
Load Content Files
b. Add any comments in the Description box. c. Type the username (including domain for Windows) of the workareas 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 text box and type the name of the group in the Group box. If you want this workarea to be private, so that only the owner can modify files in it, leave the default group (None) selected. e. Type or browse to the edition to use as the basis for the workarea. f. Click OK.
You can also use the iwmkwa (iwmkwa.exe for Windows) command-line tool (refer to the TeamSite Command-Line Tools Guide for details).
Populate the Initial Workarea

To populate an initial workarea 1. Do one of the following actions based on your operating system:
UNIX: Log in (using telnet, NFS, or Samba) as root . Windows: Log in as Administrator.
2. Copy your content files into the new workarea (default location):
UNIX: iwmnt/default/main/branchname/WORKAREA/
workareaname
Windows: 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. When copying files on UNIX, use tar to maintain file permissions and timestamps (that is, make a tar file of your content, copy the file to the workarea, and then untar the file). 3. Navigate to the workarea and ensure the file permissions are correct before submitting the files to the staging area; if not, set standard Windows ACLs (Windows) or permissions (UNIX) on the content files. On UNIX, use chown and chgrp to limit access to files by changing the owners and groups for these files. For more information on the chown and chgrp commands, refer to a UNIX reference manual. Because TeamSite considers a change in ACLs (Windows) or permissions (UNIX) 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
159
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 files 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 (refer to the TeamSite Administration Guide) if you do not want to set permissions manually. To set permissions on content files and directories on Windows: 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 opens. 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.
Submit 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 becomes 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 need to click All at the bottom of the dialog box to ensure that all files and directories appear. 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 opens. 4. Type the appropriate information and comments in the text boxes. Required text boxes have an asterisk (*) after the text box name. You can use two comments text boxes:
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.
160
Load Content Files
You can also use the iwsubmit (iwsubmit.exe on Windows) command-line tool to submit files to the staging area (refer to the TeamSite Command-Line Tools guide for details).
Publish 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 with ContentCenter Professional 1. From the Branch view, click the New Editions link. 2. Complete the form that opens in the right pane. a. Type the name of the edition. b. Type any comments you have in the Description text box. c. Click OK. The contents of the staging area are published as an edition. You can also use the iwpublish (iwpublish.exe on Windows) command-line tool to publish an edition (refer to the TeamSite Command-Line Tools Guide for details).
The ContentCenter Interfaces

This section introduces the ContentCenter Standard and ContentCenter Professional interfaces, and describes the various modules, the information displayed in them, and if they are configurable (by modifying TeamSite configuration files) or customizable (by using the ContentServices User Interface ToolKit).
Display 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
161
My Favorites My Forms Work in Progress
This list also appears in the My Workareas view in ContentCenter Professional.
Display 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 of:

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 list
For example, Figure 40 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 list in the background).
162
Load Content Files
Figure 40 ContentCenter Standard New Forms module
Refer to the TeamSite User Interface Customization Guide for information about changing the default configuration.
Click Workarea Names

Clicking the workarea name in the ContentCenter Standard My Workareas module (or in a Task Detail dialog box) can be configured to display either the directory Web page and VisualPreview or the directory list page. To configure the link to display the index page and VisualPreview, consider the following issues:
Your content Web server (for example, Apache or IIS) must be configured to redirect requests for directories to a file (typically an index.html page). For detailed information about this setting, see Web Server Plug-ins and VisualPreview on page 137. Failure to configure this correctly can cause a Web server error, or your Web server displaying a Web server-generated directory list (not a TeamSite directory list) as shown in Figure 41.
163
Figure 41 Non-TeamSite browser directory list
When your content Web server forwards directory requests to files, iwproxy needs assistance to follow this forwarding (as described in Web Server Plug-ins and VisualPreview on page 137). Failure to do this results in the correct page being displayed, but with VisualPreview acting like it is pointing at a directory (as shown in Step 41). In ContentCenter Standard, VisualPreview displays a warning that it cannot 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.
Display Forms in the New Forms Module

Each workarea that appears in the New Forms module is populated with the forms specified in templating.cfg. This file is located by default in ts-home/ local/config. (See Figure 42.)
164
Load Content Files
Figure 42 ContentCenter Standard New Forms module
The category name=intranet and template name=deptInfo.tpl form being displayed in ContentCenter
In pre-6.0 versions of TeamSite, all sample templates (silent installation input files) 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 results 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.
Display Files in the Work in Progress Module

Table 10 shows whether a file displays in the Work In Progress module of ContentCenter Standard for nine different file states. Whether a file displays in the Work In Progress module is the same for all out-of-the-box TeamSite user roles. Table 10 File status and display in ContentCenter Standard File State
Modified by me, unlocked Modified by me, locked by me Modified by me, locked by someone else Modified by someone else, unlocked
Displayed in Work In Progress Module?

Yes Yes No No
165
Table 10 File status and display in ContentCenter Standard (continued) File State
Modified by someone else, locked by me Modified by someone else, locked by someone else Unmodified, unlocked Unmodified, locked by me Unmodified, locked by someone else
Displayed in Work In Progress Module?

No No No Yes No
The files listed in the Work In Progress module look similar to Figure 43. Figure 43 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.
Display My Tasks
The ContentCenter Tasks module displays the following types of tasks (see Figure 44).

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.
166
Load Content Files
Figure 44 ContentCenter Standard Tasks module
For detailed information about assigning and completing tasks, refer to the online help.
Configure 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 opening to your users, configure Local File Manager as described in Install Local File Manager on page 142. 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.
167
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.
Display Task Variables

By default, the ContentCenter interfaces display the Priority and Due Date task variables (see Figure 45). Figure 45 ContentCenter Standard Task Details
Link to VisualPreview Editing Variables that cannot be customized or changed
Default variables that can be customized
NOTE 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 appear in the Task Details dialog box using the User Interface ToolKit (UITK). Refer to the TeamSite User Interface Customization Guide for information about customizing task variables.
168
Load Content Files
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
Resolve Task Conflicts

The TeamSite Content Servers 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 users task list with an indication that a conflict exists. ContentCenter Standard users having the Editor, Administrator, or Master roles may have a conflicting submit task in the Task list. Because the ContentCenter Standard interface does not enable users to resolve conflicts, these users must use ContentCenter Professional to resolve any conflicts.
Configure 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 users 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 dialog box opens inside a wizard. The workflow instantiation dialog box that opens in ContentCenter Standard and ContentCenter Professional are similar, but not identical.
169
Eliminate Tagging Steps in Wizards

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

The TeamSite installation program creates a UI daemon user called iwui to restrict access to the session cookie encryption password stored in ts-home/ private/etc/passphrase. The UI daemons (iwwebd and iwjbossd) and iwproxy must be able to read the password to issue and validate session cookies. Currently, iwwebd and iwjbossd run as iwui, and iwproxy runs as root. The iwui user has no privileges except for being able to read the passphrase file:
-r------- 1 iwui passphrase adm 94 Aug 1 16:20 /usr/ts-home/private/etc/
The iwui user also has the following characteristics:
Member of the system group nobody. This ensures that there are as few privileges associated with this user as possible. Membership in other groups that own no files on the system would be equivalent. Owns the iwwebd and iwjbossd processes. For more information about iwwebd and iwjbossd, refer to the TeamSite Administration Guide. Is hard coded as iwui in the iwsessionkeygen CLT. Therefore you should not change the name of this user. Impersonation user for Tomcat. Provides the ability for the user logged into the browser interface to execute a program on the TeamSite server and have that program behave as if it were run by the logged in user and not iwui, nobody, or root. User Id. By default, is assigned the next available user ID (UID) by the installation program: Creating Interwoven TeamSite UI Daemons User (iwui)... choose a UID for the new user, or press <Enter> to accept the next available UID.
Home directory is ts-home. If you do not want this system user to have a UID mixed in with your regular user accounts, manually assign a UID during the installation (system accounts typically have a lower UID).
170
CHAPTER 7
Configure ReportCenter
This section describes the TeamSite Reporting service configuration file.

TeamSite Report Server Configuration File Configure TeamSite Configure OpenDeploy
TeamSite Report Server Configuration File

The iw-home/tsreport/conf/spring-config.xml file is used to configure reporting. The information in this file is created during the TeamSite installation. Most changes to this file are made using the iwconfigtsreport command-line tool. However, you need to manually edit this file if you want to capture extended attributes and workflow variables (see Reportable Extended Attributes on page 175). This section shows snippets of the file as an example and then describes the configuration parameters in each area and specifies the information to modify. Most of the information in this file is derived from the TeamSite installation.
171
Chapter 7 Configure ReportCenter
Database
The installation software enters the following information into the file.
<bean autowire="default" class="com.interwoven.tsreport.server.RCDataSource" dependency-check="default" id="tsreport.DataSource" lazy-init="default" scope="prototype"> <property name="driverClassName"> <value>com.microsoft.sqlserver.jdbc.SQLServerDriver</value> </property> <property name="url"> <value>jdbc:sqlserver:// win-db2-wince:1433;databaseName=tsreports;selectMethod=cursor;</ value> </property> <property name="username"> <value>sa</value> </property> </bean>
The value of the <driverClassName> element refers to the required database driver. The <URL> element is the URL connect string. The <username> element refers to the database user. During installation, you are also prompted for this users password. It is stored in a different file and can be changed using iwconfigtsreport CLT.
CSSDK
The installation software enters the following information into the file.
<bean autowire="default" class="com.interwoven.tsreport.server.CssdkConnectionPool" dependency-check="default" id="tsreport.CSSDKConnectionPool" lazy-init="default" scope="singleton"> <constructor-arg value="C:\PROGRA~1\INTERW~1\TeamSite\cssdk\ cssdk.cfg" /> <constructor-arg value="C:\PROGRA~1\INTERW~1\TeamSite\local\ config\ssl\tsreport" /> <constructor-arg value="localhost" /> <constructor-arg value="en" /> <constructor-arg value="1" /> </bean>
172
You do not normally need to edit this section.

<constructor-arg value="C:\PROGRA~1\INTERW~1\TeamSite\ cssdk\cssdk.cfg" /> provides the location of the configuration file. <constructor-arg value="C:\PROGRA~1\INTERW~1\TeamSite\ local\config\ssl\tsreport" /> setting points to the location of the SSL certificate. This is used to establish trusted client connections to the TeamSite server. The certificate is included with TeamSite Report Server. <constructor-arg value="localhost" /> identifies the TeamSite server. <constructor-arg value="en" /> identifies the language of the server. <constructor-arg value="1" /> describes the number of connections to the TeamSite server; leave this at one.
If the report server is being run under an account other than root (UNIX) or SYSTEM (Windows), that user account must be a TeamSite user assigned as Master user.
Receiver
<bean autowire="default" class="com.interwoven.tsreport.server.receiver.JmsReceiver" dependency-check="default" id="tsreport.JmsReceiver" lazy-init="default" scope="prototype"> <property name="jmsProperties"> <props merge="default"> <prop key="java.naming.factory.initial">org.exolab.jms.jndi.InitialConte xtFactory</prop> <prop key="java.naming.provider.url">tcp://localhost:3035/</prop> <prop key="TopicConnectionFactory">JmsTopicConnectionFactory</ prop> </props> </property> <property name="listeners"> <list merge="default"> <ref bean="tsreport.JmsListener" /> </list> </property> </bean> NOTE In <prop key="java.naming.provider.url">tcp:// localhost:3035/</prop>, 3035 is the JNDI port.
173
Hibernate Properties
You can tune the hibernate properties to achieve optimal performance.
<bean autowire="default" class="org.springframework.beans.factory.config.PropertiesFactoryB ean" dependency-check="default" id="tsreport.HibernateProperties" lazy-init="default" scope="singleton"> <property name="properties"> <props merge="default"> <prop key="hibernate.hbm2ddl.auto">update</prop> <prop key="hibernate.dialect">org.hibernate.dialect.SQLServerDialect</ prop> <prop key="hibernate.show_sql">true</prop> key="hibernate.c3p0.acquire_increment">1</prop> key="hibernate.c3p0.idle_test_period">100</prop> key="hibernate.c3p0.minPoolSize">5</prop> key="hibernate.c3p0.maxPoolSize">20</prop> key="hibernate.c3p0.timeout">600</prop> key="hibernate.c3p0.max_statements">50</prop> key="hibernate.c3p0.testConnectionOnCheckout">false</prop> </props> </property> </bean> <prop <prop <prop <prop <prop <prop <prop
<prop key="hibernate.show_sql">true</prop>. Enables logging of the SQL statements executed by the hibernate framework. The logs are located in the tsreport_out.log file. <prop key="hibernate.c3p0.acquire_increment">1</prop>. Denotes the incremental number of connections created by hibernate. <prop key="hibernate.c3p0.idle_test_period">100</prop>. Specifies the time, in seconds, for the database connections in the pool to be validated. <prop key="hibernate.c3p0.minPoolSize">5</prop>. Denotes the initial and minimum number of database connections obtained for the pool. <prop key="hibernate.c3p0.maxPoolSize">20</prop>. Denotes the maximum of database connections obtained for the pool. <prop key="hibernate.c3p0.timeout">600</prop>. Denotes the maxium idle time for a connection in seconds. <prop key="hibernate.c3p0.max_statements">50</prop>. Denotes the maximum number of statements in the cache.
174
<prop key="hibernate.c3p0.testConnectionOnCheckout">false</ prop>. Validates the connection when it is obtained from the pool. Autonomy recommends to leave this value as it is for performance reasons.
DAO
 <bean autowire="default" class="com.interwoven.tsreport.server.orm.dao.impl.CoreDAOImpl" dependency-check="default" id="tsreport.dao.coreDAO" lazy-init="default"> <property name="sessionFactory"> <ref local="tsreport.SessionFactory" /> </property> </bean> <bean autowire="default" class="com.interwoven.tsreport.server.orm.dao.impl.WorkflowDAOImpl " dependency-check="default" id="tsreport.dao.workflowDAO" lazy-init="default"> <property name="sessionFactory"> <ref local="tsreport.SessionFactory" /> </property> </bean>
To use a custom DAO: 1. Copy the original bean snippet for the DAO that needs to be customized from the spring-config.xml file and paste it in the same file. 2. Replace the id attribute value to customer.tsreport.dao.coreDAO. 3. Replace the class attribute value with the fully qualified name of the custom class that handles the CoreDAO.
Reportable Extended Attributes

This section should be manually edited.
<bean autowire="default" class="java.util.ArrayList" dependency-check="default" id="tsreport.ReportableExtendedAttributes" lazy-init="default"> <constructor-arg> <list merge="default"> <value>key</value> <value>key1</value> <value>key2</value> </list>
175
</constructor-arg> </bean>
You need to specify values for the element named Reportable Extended Attributes. Replace key, key1, and key2 with the names of extended attributes to be reported on. Add additional value elements as needed. If the EAs in metadata.cfg are to be reported on, the full name should be specified, such as TeamSite/Metadata/EAName. If you have installed ReportCenter and want to generate a Content Expiration report, you must configure this section as mentioned in Content Expiration on page 86.
Job Variables
The jobvariables section captures workflow and task variables. Job variables are captured on WorkflowActivate events, and task variables are captured on TaskInactivate events. You need to specify the variables in this section. Both job and task variables are entered in the same section.
<bean autowire="default" class="java.util.ArrayList" dependency-check="default" id="tsreport.JobVariables" lazy-init="default"> <constructor-arg> <list merge="default"> <value /> <value /> <value /> </list> </constructor-arg> </bean>
You must restart the Report Server after making these changes in order for them to take effect. Windows: From the Services option in the Administrative Tools menu, stop and start Autonomy TeamSite Report Service. UNIX: /etc/init.d/iw.tsreport stop /etc/init.d/iw.tsreport start
Configure TeamSite
Some of the user events, identified in Table 2 on page 13, must be turned on in the TeamSite iw.cfg file. Add the following entries to the [iwserver] section of the iw.cfg file.
[iwserver]
176
Configure OpenDeploy
log_createfse=true log_destroyfse=true log_renamefse=true log_modifyfse=true log_syncmodify=true log_syncdestroy=true log_syncrevert=true log_setea=true log_deleteea=true log_createea=true log_truncateea=true log_writeea=true
To query on workflow events in Table 3 on page 20, modify the TeamSite iw.cfg file so jobs are not deleted from the content store when they are completed. The entry in the [workflow] section should be:
[workflow] delete_jobs_on_completion=false
If this entry is not included in the iw.cfg file, the workflow events are not available to ReportCenter. After these events have been used by ReportCenter, they are deleted from the content store.
Configure OpenDeploy
OpenDeploy must be configured such that:
The Reporting user interface provides you with the options to generate OpenDeploy related reports. Complete the following steps for the OpenDeploy out-of-the-box report generation features (DAS Activity and Deployment Activity) to be available in the reporting user interface. Typically, you complete these steps after the installation of TeamSite.
NOTE You must have the od-admin role to perform this configuration.
a. Go to Administration Console and click Servers. The available servers appear in the left pane. b. Select OpenDeploy. c. Click Edit. The Edit OpenDeploy Server Settings dialog box opens. d. Replace the default or edit the entry in the Address text box to the correct hostname.
177
e. Click Save.
Before generating any OpenDeploy reports, you must ensure that the reporting database gets populated with the generated OpenDeploy events, which can be queried to generate OpenDeploy related reports. Refer to the OpenDeploy documentation to configure the OpenDeploy configuration files.
178
CHAPTER 8
Install Search
This section provides a walkthrough of the Search installation process. For information on pre-installation tasks, see Search Prerequisites on page 40. Refer to the Web Solutions Installation Planning Guide for information on hardware requirements.

Install Search Uninstall Search
Install Search
Use this procedure to install TeamSite Search.
To install Search on your server 1. Log in as Administrator on the system where you want to install Search. 2. From the Autonomy download site, copy the IWOVInstaller-platform-version.exe file to a temporary directory on a local drive. 3. Double-click IWOVInstaller-platform-version.exe.
179
Chapter 8 Install Search
The installer launches and the Introduction dialog box opens.
TIP In the installation wizard, you can move between text fields by either clicking a field or by pressing Tab.
4. Click Next. The Select Installation Type dialog box opens. 5. Select Install and click Next. The Component Selection dialog box opens (see Figure 46). Figure 46 Component Selection
components to the list. 6. Select TeamSite Search, and click Next.
180
Install Search
The Select Base Directory for Installation dialog box opens (see Figure 47). Figure 47 Select Base Directory for Installation
7. Type or choose the installation location for the selected components and click Next. The Autonomy License Agreement dialog box opens. 8. Read the license agreement and if you agree to its terms, select I accept the terms of the License Agreement and click Next.
181
The TeamSite Server Host dialog box opens (see Figure 48). Figure 48 TeamSite Server Host
9. If you are installing Search on the same system as TeamSite, leave the default localhost value. If you are installing Search on a separate system, type the name of the system where TeamSite is installed. Click Next.
182
Install Search
The Search Server Port dialog box opens (see Figure 49). Figure 49 Search Server Port
10. Type the port number of the search server, and then click Next.
183
The Index Server Port dialog opens (see Figure 50). Figure 50 Index Server Port
11. Type the Index Server Port Number, and then click Next.
184
Install Search
The Event Subsystem JMS Server Port window dialog box opens (see Figure 51). Figure 51 Event Subsystem JMS Server Port
12. Type the Event Subsystem JMS Server Port number. This service is installed on the TeamSite host. Click Next.
185
The Get IDOL Server Ports dialog box opens (see Figure 52). Figure 52 Get IDOL Server Ports
13. Type:
IDOL Query Port. The port number that the IDOL server listens to for
query related requests.

IDOL Index Port. The port number that the IDOL server listens to for
indexing related requests.

IDOL Service Port. The port at which the IDOL server is running.
These IDOL port numbers can also be changed later after the installation using the iwsearch-home/etc/search.properties and iwsearch-home/idol/AutonomyContent.cfg files. If you change the IDOL port numbers, ensure that you restart the IDOL, Index, and Search Servers. 14. Click Next.
186
Install Search
The Get IDOL Category Server Ports dialog box opens (see Figure 53). Figure 53 Get IDOL Category Server Ports
15. Type the IDOL Category Action Port and IDOL Category Service Port numbers. Click Next.
187
The Get IDOL Community Server Ports dialog box opens (see Figure 54). Figure 54 Get IDOL Community Server Ports
16. Type the IDOL Community Action Port and IDOL Community Service Port numbers. Click Next.
188
Install Search
The Get Agent Store Server Ports dialog box opens (see Figure 55). Figure 55 Get Agent Store Server Ports
17. Type the Agent Store Action Port and Agent Store Service Port numbers. Click Next.
189
The Get TeamSite Connector Server Ports dialog box opens (see Figure 56). Figure 56 Get TeamSite Connector Server Ports
18. Type the TeamSite Connector Action Port and TeamSite Connector Service Port numbers. Click Next.
190
Install Search
The Get Connector Framework Server Ports dialog box opens (see Figure 57). Figure 57 Get Connector Framework Server Ports
19. Type the Connector Framework Action Port and Connector Framework Service Port numbers. 20. Click Next. The Process Confirmation dialog box opens and has the following details:
Install location Components to install Disk space details
21. Click Next. The installer completes the installation and configuration process and the Summary dialog box opens. 22. Click Done to exit the installer.
191
Uninstall Search
Use this procedure to uninstall TeamSite. To uninstall Search 1. Log in as Administrator on the system where you want to uninstall Search. 2. Navigate to the temporary directory on the local drive where you downloaded the IWOVInstaller-platform-version.exe installer. 3. Double-click IWOVInstaller-platform-version.exe. The installer launches. The Introduction dialog opens. 4. Click Next. The Select Installation Type dialog box opens. 5. Select Uninstall and click Next. The Select Components to Uninstall dialog box opens. 6. Select TeamSite Search and click Next. The Process Confirmation dialog box opens. 7. Click Next. The Summary dialog box opens. 8. Click Done to complete the uninstallation.
192
CHAPTER 9
Configure Search
TeamSite Search allows users to search common document types and data records from TeamSite. A number of files are used to configure Search. Command-line tools (CLT) are also available for system administrators to perform queries and to set up index and search functionality; refer to TeamSite Command-Line Tools.

Configure the Index and Search Managers Field Mapping Configuration
Configure the Index and Search Managers

The iwsearch-home/etc/search.properties file is used to configure the index manager and the search server. This file is used to set parameters in the following areas:

Generic Configuration Index Server Configuration Search Server Configuration Logging Configuration IDOL Server Configuration
The following sections show the configuration parameters in each area and describe the information that can be modified. The file reflects settings made
193
Chapter 9 Configure Search
during the Search installation; other items may need to be modified to enhance Search performance. On Windows platforms, after modifying the configuration file, you must restart the index and search services. The search.properties file cannot contain non-English characters.
CAUTION The iwsearch-home/etc/ search.private.properties file contains settings
you do not normally need to adjust. Do not modify this file unless specifically instructed to do so by an Autonomy Technical Support representative.
Generic Configuration
This section of search.properties identifies the TeamSite server. It is normally set by the installation program, however, if your TeamSite server changes, you need to modify this section. You also need to specify the locale of the index manager and search manager. This value typically refers to the same language or country as specified for the locale of the TeamSite server.
################################################################## # Generic configuration items (common for index server and search) ################################################################# # TeamSite host iw.teamsite.server.host=_IW_TS_HOST_NAME_ # Locale of index/search server. The values should be one of # English_UnitedStates, French_France, Korean_Korea, Japanese_Japan, # SimplifiedChinese_China, # TraditionalChinese_Taiwan and German_Germany. Else, it will default # to English_UnitedStates. iw.server.locale=English_UnitedStates
Index Server Configuration

This section of search.properties is used to configure the index manager. You need to set or modify these options.
iw.index.server.port Change the value for iw.index.server.port to reflect your actual TCP
194
port. This is the TCP port that the index manager monitors for API requests, such as requests from CLTs and the user interface.

java.naming.provider.url Specify the value for java.naming.provider.url. iw.index.markpartial.duration The iw.index.markpartial.duration parameter specifies how old (in hours) an index can be before it is considered to be a partial (or out-of-date) index. Search compares the last indexed edition with the current edition; if they are not the same, this value is used to determine whether the index is partial. iw.index.maxidxsize The iw.index.maxidxsize parameter controls how many files are optimally submitted to be indexed at a time. iw.index.scipool.max and iw.index.scipool.warm The session pooling parameters control the number of connections open to TeamSite. The iw.index.scipool.max parameter specifies the maximum number of connections that can be opened. The iw.index.scipool.warm parameter specifies the number of connections that are always open, whether they are used. iw.index.binaryextension The iw.index.binaryextension parameter indicates types of files that will not have their content indexed. For example, graphics files do not have content that can be indexed. Any metadata set for these files will, however, be indexed. Refer to for more details. iw.index.maxfilesizetoindex The iw.index.maxfilesizetoindex parameter indicates the maximum size of the file in megabytes that will be indexed by the index manager. If the size of the file is larger than the value specified by this parameter, the contents of this file will not be indexed. iw.index.events.enable The iw.index.events.enable parameter indicates whether the index should be updated whenever a file is submitted. A value of true indicates that the index should be updated when a file is submitted; otherwise, set it to false. If you set incremental indexing to false, you can use the iwndxrefreshbr CLT to incrementally index a specific branch. iw.index.events.listen.attempts and iw.index.events.listen.wait You can control the number of times the index manager attempts to listen to the TeamSite Event Subsystem using the iw.index.events.listen.attempts parameter; this value must be a
195
positive integer. You can also specify the number of seconds the index manager waits between attempts to listen to the TeamSite Event Subsystem using the iw.index.events.listen.wait parameter.
iw.index.iwserver.connect.attempts and iw.index.iwserver.connect.wait You can control the number of times the index manager attempts to connect to the TeamSite server by using the iw.index.iwserver.connect.attempts parameter. You can also specify the number of seconds the index manager waits between attempts to connect to the TeamSite server using the iw.index.iwserver.connect.wait parameter. iw.index.optimalWaitMins When the iw.index.events.enable parameter is set to true, the iw.index.optimalWaitMins parameter indicates that events should be queued before being indexed and specifies the number of minutes to wait before starting the index job. Using this feature allows grouping submissions so multiple files are indexed at once. If numerous updates are occurring, you may want to set a higher value to get maximum performance; however, your index may become slightly out-of-date. iw.index.wamodifications.enable The iw.index.wamodifications.enable parameter controls at a global level whether indexing of and searching across modifications in workareas of indexed branches is turned on. A value of true indicates that this feature is turned on; a value of false indicates that this feature is turned off. The default setting is true, workarea indexing is enabled. iw.index.wamodifications.branchcreation.default The iw.index.wamodifications.branchcreation.default parameter controls whether indexing the modifications of all the workareas of an indexed branch should begin when that indexed branch is loaded in the index server memory. This could happen the first time the branch is indexed or when the index server is restarted and the indexing information for that branch is read from the relevant branch collection. The only permissible values for this parameter are all or none. A value of all indicates that all the workareas of the relevant indexed branch will be indexed. A value of none indicates that none of the workareas of the relevant indexed branch will be indexed. This feature is useful if you need to either index all of the workareas of the indexed branches or none of the workareas of the indexed branches at one time. The iwdxwamodificationsbr CLT provides the ability to control indexing of the modifications in workareas on a per-branch level. The default setting is all. iw.index.wamodifications.frequency The iw.index.wamodifications.frequency parameter controls how often (in minutes) the workarea indexer module inside the index server goes
196
through all the relevant workareas of the indexed branches and indexes the modified files. The default is 10 minutes, which is the minimum value. After the workarea indexer module has completed one cycle, it waits for the remainder of the time specified by this parameter before it repeats its cycle, however, if the amount of time taken by the workarea indexer module to complete one cycle is greater than the time specified by this parameter, the next cycle of indexing begins immediately.
iw.startup.autoscan Automatically scan and index all TeamSite branches on Index Server startup that are not previously indexed. Set it to true to enable the autoscan. The default is false. iw.bulkindex.latest.edition.only The default is false. When set to true, the bulk indexer will start the indexing with the latest content in staging only, then incrementally index all new coming changes. This potentially speeds up the initial bulk indexing performance.
################################################################## #### # Index server configuration ################################################################## #### # Server configuration iw.index.server.port=_IW_INDEX_PORT_ # TeamSite JMS producer side details java.naming.provider.url=tcp://_IW_TS_HOST_NAME_:_IW_EVENT_PORT_/ # How old (hours) the index needs to be (relative to current edition) # for it to be considered partial iw.index.markpartial.duration=24 # Max number of files for IDX iw.index.maxidxsize=4000 # TeamSite session pooling iw.index.scipool.max=10 iw.index.scipool.warm=1 # Binary extensions. The content in these files will not be indexed, although metadata will be. iw.index.binaryextensions=exe,jpg,gif,psd,tif,tiff,au,wav,bmp,rif, zip, swf,db,png,class,pdb,3gp,mp3,mov,mpeg,mp4,jar # Maximum size of the file (in megabytes) to be indexed.
197
iw.index.maxfilesizetoindex=20 # Event-based updates are enabled iw.index.events.enable=_IW_INCR_UPDATES_ENABLED_ # Number of times Index server attempts to listen to # TeamSite event system before giving up iw.index.events.listen.attempts=10 # Number of seconds Index server waits between attempts to listen to # TeamSite event system iw.index.events.listen.wait=12 # Number of times Index server attempts to connect to # TeamSite server before giving up iw.index.iwserver.connect.attempts=10 # Number of seconds Index server waits between attempts to connect to # TeamSite server iw.index.iwserver.connect.wait=12 # Optimal wait time before received events are processed (in minutes) iw.index.optimalWaitMins=1 # Indexing workarea modifications # Control whether indexing of and searching across modifications in # workareas of indexed branches is turned on or not. iw.index.wamodifications.enable=false # Control whether indexing the modifications of ALL the workareas of a # branch at the time the branch is first indexed should be turned on or # off (permissible values are none and all). iw.index.wamodifications.branchcreation.default=none # Control how often (in minutes) an attempt is made to index the modified # files in the relevant workareas of all the relevant indexed branches. # minimum value is 10mins iw.index.wamodifications.frequency=10 # Scan and index all branches on startup, defaults to false iw.startup.autoscan=false
198
# Bulk index latest content in staging only to start with, then incrementally index all new changes. # Set to true to speed up initial bulk indexing. Defaults to false. iw.bulkindex.latest.edition.only=false
Search Server Configuration

This section of search.properties contains parameters that control the search manager.
iw.search.server.port Change the value for iw.search.server.port to reflect your actual TCP port. This is the TCP port that the search manager monitors for API requests, such as requests from CLTs and the user interface. iw.search.server.threadpool.warmthreads The search manager uses a pool of worker threads for servicing client requests. Each client connection, whether from a CLT or the user interface, is served by its own worker thread. When the search manager starts, it creates threads specified by the value of the iw.search.server.threadpool.warmthreads parameter. If a new client connection is made and none of these threads is available to service the connection, a new thread is created, thus growing the thread pool. iw.search.server.threadpool.maxthreads The thread pool growth is capped by the value of the iw.search.server.threadpool.maxthreads parameter. This value determines the maximum number of simultaneous client connections that can be serviced by the server. iw.search.server.threadpool.keepalivetime When a thread has been idle for longer than the millisecond time out specified by the value of the iw.search.server.threadpool.keepalivetime parameter, it is terminated by the server to conserve resources. If iw.search.server.threadpool.keepalivetime is set to a value of -1, the threads are never reclaimed. iw.search.query.maxOpenQueriesPerUser The iw.search.query.maxOpenQueriesPerUser parameter indicates the maximum number of queries an individual user can have open. If they exceed that number of queries, the earliest ones are no longer valid. iw.search.query.defaultQueryLocale The iw.search.query.defaultQueryLocale parameter provides a default locale to use to process queries when the query locale is not specified.
199
iw.index.server.host Change the value for the iw.index.server.host parameter if the index manager is on a different host computer than the search manager. iw.search.cache.raw.entries.capacity, iw.search.cache.raw.entries.grace, iw.search.cache.raw.validity.mins, and iw.search.cache.processed.size You can modify the cache configuration. The raw cache contains the results of a query as they are retrieved. Post-processing filters the results from the raw cache and writes the results to the processed cache until enough results are found to return the first page of results. The values for iw.search.cache.raw.entries.capacity and iw.search.cache.raw.entries.grace are used to control the total number of queries kept in the system and the extra capacity that can be used when managing the number of queries. For example, the default settings indicate 100 queries are kept in the system, but that number can go to 110 (10 grace queries) and then 10 queries would be deleted at one time to return to the 100-query capacity. This is more efficient than deleting one extra query at a time. The iw.search.cache.raw.validity.mins parameter specifies the validity time for the queries kept in the system. The iw.search.cache.processed.size parameter specifies the size of the processed cache. iw.search.scipool.max, iw.search.scipool.warm, iw.search.scipool.max, and iw.search.server.threadpool.maxthreads The session pooling parameters control the number of connections open to TeamSite. The iw.search.scipool.max parameter specifies the maximum number of connections that can be opened. The iw.search.scipool.warm parameter specifies the number of connections that are open, whether they are used. The value for iw.search.scipool.max should be less than half the value of iw.search.server.threadpool.maxthreads, but should not generally exceed 25 for the best performance.
################################################################## #### # Search server configuration ################################################################## #### iw.search.server.port=_IW_SEARCH_PORT_ iw.search.server.threadpool.maxthreads=50 iw.search.server.threadpool.warmthreads=10 iw.search.server.threadpool.keepalivetime=60000 iw.search.query.maxOpenQueriesPerUser=2
200
iw.search.query.defaultQueryLocale=en # change this if the index server is on a different host than the # search server iw.index.server.host=_IW_INDEX_HOST_ #Cache configuration #Raw cache iw.search.cache.raw.entries.capacity=100 iw.search.cache.raw.entries.grace=10 iw.search.cache.raw.validity.mins=240 #Processed cache iw.search.cache.processed.size=100 # TeamSite session pooling. iw.search.scipool.max=10 iw.search.scipool.warm=1
Logging Configuration
The logging configuration section in search.properties applies to both the index manager and the search manager. The first part of the value for the log4j.logger.com.interwoven parameter specifies the log level for the server. The set of possible log levels (in increasing order of verbosity) are FATAL, ERROR, WARN, INFO, and DEBUG. Normally, the server should be run with the log level of INFO. You can control the maximum log file size using log4j.appender.mainLogger.MaxFileSize and specify the number of archived or backup log files using log4j.appender.mainLogger.MaxBackupIndex.
####################################################### # Logging configuration ####################################################### log4j.logger.com.interwoven=INFO, mainLogger log4j.appender.mainLogger.MaxFileSize=5000KB log4j.appender.mainLogger.MaxBackupIndex=10
IDOL Server Configuration

This section of search.properties identifies the IDOL server. It is normally set by the installation program, however, if your IDOL server changes, you need to modify this section.
iw.idol.server.host The iw.idol.server.host parameter indicates the machine where the
201
IDOL server resides. This should be on the same machine as where the index and search server are located.
iw.idol.index.port The iw.idol.index.port parameter specifies the port that the IDOL server listens to for indexing related requests. iw.idol.query.port The iw.idol.query.port parameter specifies the port that the IDOL server listens to for query related requests.
####################################################### # IDOL server configuration ####################################################### iw.idol.server.host=_IW_IDOL_HOST_ iw.idol.index.port=_IW_IDOL_INDEX_PORT_ iw.idol.query.port=_IW_IDOL_QUERY_PORT_
Relocate the TeamSite Search Collection Folder

By default, the TeamSite Search collection folder, which stores the IDOL databases, is located in the <SEARCH_HOME>/idol folder. You may want to move the folder to another drive if you run out of disk space on the original drive. To change the default location of the IDOL database, you must modify the [Paths] section of the IDOL configuration file. The IDOL configuration file is called AutonomyContent.cfg and is located in the <SEARCH_HOME>/idol folder. To change the default location of the IDOL database 1. Open the AutonomyContent.cfg file in a text editor. 2. Locate the [Paths] section in the file. By default, the path locations are set as follows:
[Paths] DyntermPath=./dynterm NodetablePath=./nodetable RefIndexPath=./refindex MainPath=./main StatusPath=./status TemplateDirectory=./templates NumericPath=./numeric TagPath=./tagindex StatePath=./storedstate SortFieldPath=./sortfield IndexTmpPath=./indextmp IndexQueuePath=./indexqueuepath
202
Field Mapping Configuration
3. For each parameter in the [Paths] section, specify the full path to the new location. The example below stores all IDOL database files in C:/database on Windows:
[Paths] DyntermPath=C:/database/dynterm NodetablePath=C:/database/nodetable RefIndexPath=C:/database/refindex MainPath=C:/database/main StatusPath=C:/database/status TemplateDirectory=C:/database/templates NumericPath=C:/database/numeric TagPath=C:/database/tagindex StatePath=C:/database/storedstate SortFieldPath=C:/database/sortfield IndexTmpPath=C:/database/indextmp IndexQueuePath=C:/database/indexqueuepath
4. Save the AutonomyContent.cfg file, and restart the IDOL service, TeamSite Search Index Manager, and Search Server. 5. If you have indexed content prior to changing the location of the folder where the index databases are stored, then you must do the following: a. Stop The IDOL Service, TeamSite Search Index Manager, and Search Server. b. Delete branches.db and branches.db.bak files from the <SEARCH_HOME>/... folder. c. Start the IDOL service, TeamSite Search Index Manager, and Search Server. d. Re-index your content.

The field mapping configuration file (iwsearch-home/etc/ FieldMapping.xml):

Defines the extended attributes that will be indexed by the index manager. Defines the templating attributes for the specified template type that will be indexed by the index manager.
If you make changes to FieldMapping.xml, such as adding another attribute, you must:

In Windows: Stop and restart the index and search services. In UNIX: Stop and restart the index and search services.
203
You also need to force the index manager to re-index all of the files. Use the iwndxpurgebr CLT to remove the collection; then add the branch to the index again. The FieldMapping schema (in iwsearch-home/etc/FieldMapping.xsd) provides the schema for creating the FieldMapping.xml configuration file. In addition to these extended and templating attributes that are defined in the field mapping configuration file, there are a set of attributes and file properties that will always be indexed. These are defined in an internal standard field mapping configuration file. The StandardFields schema defines these fields and they cannot be changed. In the field mapping configuration file, the globalFields element contains extendedAttributeFields elements that contain the fieldSpecification element for each field that will be indexed. The templates element contains a template element for each FormsPublisher template used. The template element includes a templateType element that identifies the FormsPublisher template (or form). The fields within the form that will be indexed are identified in the templatingFields element, which contains one or more templatingField elements. Each templatingField element contains an xpath element and a fieldSpecification element. The templatingField element defines a mapping from the xpath of a templating entry to the field definition that is used to store it. A fieldSpecification element has the following elements:
A fieldName element. Any typical name can be chosen for this element. This name is used for building queries that are submitted to the search manager. This name should be unique across all fieldName entries in the FieldMapping.xml file. Also, none of the fieldName entries must match those that are listed in Table 11 on page 205. The fieldName must be in the same language as it is in the datacapture.cfg file for indexing to occur. A fieldType element. The possible values are string, int, float, and date. An optional formatString element. This element is relevant and required only if the fieldType element has a value of date. This element specifies the date-time format for the relevant extended attribute in one of the JDK-defined standard forms. For example, it could be yyyy-mm-dd (see Configure Date Fields on page 206). A fieldStorage element
If the fieldType element is a string, then this element needs to be of the
form zone:variable-name. The variable-name specified here should be unique across all fieldStorage entries in the
204
FieldMapping.xmlfile. None of the fieldStorage entries must match those that are listed in Table 11 on page 205.
If the fieldType element is int, float, or date, the fieldStorage
element should respectively be one of CustomInt1 through CustomInt5, CustomFloat1 through CustomFloat5, or CustomDate1 through CustomDate5. This entry should be unique across all fieldStorage entries in the FieldMapping.xml file. None of the fieldStorage entries must match those that are listed in Table 11 on page 205.
NOTE The fieldName and fieldStorage elements defined in globalFields must be unique. The fieldName and fieldStorage elements defined for a single template type may be reused in other template types. This means two different templates could have fields that share names or storage; however, these cannot conflict with a global field.
The value for a zone name must be a valid XML name; it cannot have spaces. Names are case insensitive. They can consist of all alphabetic characters (upper and lower case), numeric characters, the dash (-), the underscore (_), or the number sign (#). Table 11 fieldName and fieldStorage entries fieldName Entries
PrimaryDCR PrimaryDocumentType Type Creator CreateDate AreaRelativePath Version BranchId OwningAreaId LastModifier LastModifiedDate
fieldStorage Entries
IWTemplatingPrimaryDCR IWTemplatingPrimaryDocuemntTy pe ContentType Creator CreateDate AreaRelativePath Version BranchId OwningAreaId LastModifier LastModifiedDate
205
Table 11 fieldName and fieldStorage entries (continued) fieldName Entries

Indexed IndexedDate Size Title Author Keywords
fieldStorage Entries
Indexed IndexedDate FileSize DocMetadataTitle DocMetadataAuthor DocMetadataKeywords
Configure Date Fields

If a custom field is of type date, the formatString setting corresponding to the field must be configured in FieldMapping.xml. The formatString element tells the index manager how to parse dates during the indexing process. The index manager and search manager will not start without formatString for date fields. As shown in this example, the value of formatString specifies the pattern of the data and time strings.
<fieldSpecification> <fieldName>TeamSite/Metadata/Launch Date</fieldName> <fieldType>date</fieldType> <formatString>yyyy-MM-dd</formatString> <fieldStorage>CustomDate1</fieldStorage> </fieldSpecification>
Explanation of pattern letters:

y M d a|p h m year Month (in numeric form) Day in month AM or PM marker Hour Minute
206
The following examples show how index manager interprets the date and time patterns. Table 12 Interpretation of time and date patterns Pattern
MM/dd/yyyy yyyy-MM-dd hh:mm a yyyy-MM-dd hh:mm a
Date
08/30/20011 2011-08-30 06:30 AM 2011-08-30
Interpretation
30 Aug 2011 30 Aug 2011 06:30 AM 30 Aug 2011 12:00 AM
Example FieldMapping.xml File

The following code is an example of a FieldMapping.xml file. It includes some of the default FormsPublisher forms that ship with TeamSite. This file is located at iwsearch-home/\etc/\FieldMapping.xml.example. If desired, you can use snippets of this file to create your FieldMapping.xml file.
<?xml version="1.0" encoding="UTF-8"?> <searchFieldMapping xmlns="http://www.interwoven.com/products/ teamsite /search/config/FieldMapping.xsd" xmlns:xsi="http://www.w3.org/2001 /XMLSchema-instance" xsi:schemaLocation="http://www.interwoven.com /products/teamsite/search/config/FieldMapping.xsd FieldMapping.xsd"> <globalFields>  <extendedAttributeFields>  <fieldSpecification> <fieldName>TeamSite/Metadata/Description</fieldName> <fieldType>string</fieldType> <fieldStorage>zone:Description</fieldStorage> </fieldSpecification> <fieldSpecification> <fieldName>TeamSite/Metadata/Business Unit</fieldName> <fieldType>string</fieldType> <fieldStorage>zone:Business Unit</fieldStorage> </fieldSpecification>  <fieldSpecification> <fieldName>TeamSite/Metadata/Expiration Date</fieldName> <fieldType>date</fieldType> <formatString>yyyy-MM-dd</formatString>
207
<fieldStorage>CustomDate2</fieldStorage> </fieldSpecification> </extendedAttributeFields> </globalFields> <templates>  <template> <templateType>intranet/weather</templateType> <templatingFields> <templatingField> <xpath>/Announcement</xpath> <fieldSpecification> <fieldName>Announcement</fieldName> <fieldType>string</fieldType> <fieldStorage>zone:WeatherAnnouncement</fieldStorage> </fieldSpecification> </templatingField> </templatingFields> </template> <template> <templateType>internet/yacht</templateType> <templatingFields>  <templatingField> <xpath>/General Info/Length</xpath> <fieldSpecification> <fieldName>YachtLength</fieldName> <fieldType>int</fieldType> <fieldStorage>CustomInt1</fieldStorage> </fieldSpecification> </templatingField> </templatingFields> </template> <template> <templateType>internet/auction</templateType> <templatingFields>  <templatingField> <xpath>/Minimum Bid Amount</xpath> <fieldSpecification> <fieldName>MinBidAmount</fieldName> <fieldType>float</fieldType> <fieldStorage>CustomFloat1</fieldStorage> </fieldSpecification> </templatingField> </templatingFields> </template>
208
<template>  <templateType>internet/careers</templateType> <templatingFields> <templatingField> <xpath>/Responsibilities List</xpath> <fieldSpecification> <fieldName>Responsibilities</fieldName> <fieldType>string</fieldType> <fieldStorage>zone:Responsibilities</fieldStorage> </fieldSpecification> </templatingField> </templatingFields> </template> <template>  <templateType>internet/pr</templateType> <templatingFields> <templatingField> <xpath>/Story[1]/Section Paragraphs[1]/Paragraphs</xpath> <fieldSpecification> <fieldName>FirstStoryParagraph</fieldName> <fieldType>string</fieldType> <fieldStorage>zone:FirstStoryParagraph</fieldStorage> </fieldSpecification> </templatingField> </templatingFields> </template>  <template> <templateType>xml/press-release</templateType> <templatingFields> <templatingField> <xpath>/press-release/head/byline/@author</xpath> <fieldSpecification> <fieldName>PR_Author</fieldName> <fieldType>string</fieldType> <fieldStorage>zone:PR_Author</fieldStorage> </fieldSpecification> </templatingField> <templatingField> <xpath>/press-release/body/section/subheading</xpath> <fieldSpecification> <fieldName>Subheading</fieldName> <fieldType>string</fieldType> <fieldStorage>zone:PR_Subheading</fieldStorage>
209
</fieldSpecification> </templatingField> </templatingFields> </template> </templates> </searchFieldMapping>
210
CHAPTER 10
Install LiveSite Content Services Authoring

To facilitate the authoring, preview and delivery of online content, LSCS includes components that must be installed in both the authoring and runtime environments. This chapter describes the procedures for installing LiveSite Content Services (LSCS) in the authoring environment.

Before You Begin Install the Authoring Server Post-Installation Tasks Upgrade LSCS
Before You Begin

For details on planning your configuration, installation prerequisites (including system requirements), a table of the abbreviations used in the installation instructions, the required format for path names and character encodings, and pre-installation tasks, see LSCS Authoring Prerequisites on page 40.
NOTE If a preview instance of LSCS is to be installed in the authoring environment, it requires a similar configuration to the runtime environment.
211
Chapter 10 Install LiveSite Content Services Authoring
Install the Authoring Server

The LSCS installation program is an interactive, GUI-based method for installing LSCS. It can be run on Windows, Solaris, and Linux systems. While this document details the steps to install LSCS on Windows, a similar set of steps can be followed to install LSCS on Solaris or Linux systems. For the next procedure, it is assumed that you already installed TeamSite and infrastructure components. If required, you can install LSCS, TeamSite, infrastructure components, and other components at the same time.
NOTE LiveSite Content Services Authoring requires TeamSite and OpenDeploy. If they are not installed, you can continue with the installation but the application may not work correctly.
To install the authoring server 1. Log in as Administrator on the system where you want to install LiveSite Content Services Authoring. 2. Download the IWOVInstaller-platform-version.exe file. 3. Double-click IWOVInstaller-platform-version.exe. The installer launches and the Introduction dialog box opens. Click Next. 4. Click Next. The installation program detects Common Services on your system and the Select Installation Type dialog box opens.
NOTE In the installation wizard, you can move between text fields by either clicking a field or by pressing Tab.
If the installation program does not detect Common Services on your system, the Add or Locate Common Services dialog box opens. For information on adding, locating, or skipping common services, see Install TeamSite on page 43.
212
5. Select Install from the Installation Type dialog box and click Next. The Select Components to Install dialog box opens (see Figure 58). Figure 58 Component selection
components to the list. 6. Select LiveSite Content Services Authoring and click Next.
213
The Select Base Directory for Installation dialog box opens (see Figure 59). Figure 59 Base directory for installation
7. Type or select the installation location for LSCS and other selected components. Click Next. The License Agreement dialog box opens. 8. Read and accept the terms of the License Agreement and click Next.
214
The OpenDeploy configuration dialog box opens (see Figure 60). Figure 60 OpenDeploy configuration
9. Type the location of OpenDeployNG Home and the OpenDeployNG WebService Port. Click Next. The Configuration Details dialog box opens (see Figure 61).
215
Figure 61 Configuration details
10. Type appropriate values for Authoring Host Name, Runtime Host Name, and Runtime Port and click Next. The JDK configuration dialog box opens (see Figure 62).
216
Figure 62 JDK configuration
11. Type the appropriate JDK Home location and click Next. The TeamSite Home location configuration dialog box opens (see Figure 63).
217
Figure 63 TeamSite Home configuration
12. Type the location of TeamSite Home, and then click Next. The Configure TeamSite User dialog box opens (see Figure 64). Figure 64 Configure TeamSite User
218
13. Type the TeamSite User Name and Password and click Next. The Destination Node and Area configuration screen opens (see Figure 65). Figure 65 Destination Node and Area
14. Type appropriate values for:

Destination Node. The production runtime server name. Destination Area. The LSCSRT store location where files and metadata
will be deployed. Click Next. The Preview configuration dialog box opens (see Figure 66).
219
Figure 66 Preview configuration
15. Type the following information:

Interwoven Application Container Port. The TCP Port number on which
TeamSite is running.
TeamSite Mount Path. The path to the TeamSite virtual file system.
Click Next. The second Preview configuration dialog box opens (see Figure 67).
220
Figure 67 Preview configuration (IDOL details)
16. Type the appropriate IDOL server ports:

IDOL Server Host. Host on which TeamSite Search has installed IDOL. IDOL Action Port. TCP port number on which the IDOL Server is
accepting action requests.

IDOL Index Port. TCP port number on which the IDOL Server is accepting
index requests.
IDOL Service Port. TCP port number on which the IDOL Server is
accepting service requests.

IDOL Category Port. TCP port number on which the IDOL Server is
accepting action requests. Click Next. The Preview (targeting) configuration dialog opens (see Figure 68).
221
Figure 68 Preview (targeting) configuration
17. Choose whether to Enable Targeting or Disable Targeting and click Next. The Process Confirmation dialog opens. 18. Click Next to install and configure the selected components. The Installation Summary dialog box opens when the installation process is complete. If there were any installation errors, they are described on the dialog box. 19. Click Done.
Perform the following tasks after completing the installation: 1. Perform either of the following tasks:
Copy the license file LSCS.lic to lscsrt-home/runtime/webapps/
lscs/WEB-INF/classes/.
Modify the following section in lscs-conf.properties: # content root directory
222
Upgrade LSCS
content.root=C:/LSCSAuth-Store license.filePath=__LSCS_LICENSE_LOCATION__
If the license file is not named LSCS.lic or stored in the default path (lscsrt-home/runtime/webapps/lscs/WEB-INF/classes/), replace __LSCS_LICENSE_LOCATION__ with the correct path and file name. 2. Restart the Autonomy OpenDeploy service. 3. Restart JBOSS by running ts-home/bin/iwreset ui. 4. Test the LSCS Web service. 5. To verify that the index service is running correctly, use a Web browser to connect to the following URL:
http://<auth-host>:<auth-port>/<auth-context>/v1/admin/status
The expected response to this command is:

<?xml version="1.0" encoding="UTF-8"?> <adminResponse status="UP"/>
6. Test a simple deployment to the Preview instance of LSCS as follows: a. Create a branch and a workarea in TeamSite (for example, /default/ main/testauth and /default/main/testauth/WORKAREA/wa, respectively) b. Create a file in the workarea and submit it. c. Verify that the content has been deployed to the preview instance:
http://<auth-host>:<auth-port>/<auth-context>/v1/ document$?q=*
Upgrade LSCS
Upgrade of LSCS from 7.1 to the current version is supported. To upgrade from a version of LSCS other than 7.1, uninstall your previous LSCS installation and then install the current version of LSCS. During an upgrade, the database schema and IDOL configuration is changed and the IDOL server is re-initialized. You must re-index (redeploy) all previously deployed content. You must also manually modify any Open Deploy configuration files that were previously customized.
223
224
CHAPTER 11
Configure LiveSite Content Services Authoring

This section describes administrative tasks and provides instructions on how to configure the LSCS sample applications and customize deployments.

Configure LSCS Sample Applications Content and Metadata Deployment Administrative Tasks Enable Secure Communications on the Authoring Server
Configure LSCS Sample Applications

The TeamSite installation includes a TeamSite archive (SPAR) file for installing the LSCS sample application, sample data, and a sample workflow for deploying content to the LSCS server. The Publish to LiveSite Content Services workflow provides a way from the ContentCenter User Interface to deploy content from TeamSite to the LSCS production server. Users might find the workflow more convenient to use than the command-line driven LSCS StartDeploy scripts.
225
Chapter 11 Configure LiveSite Content Services Authoring
NOTE There is another workflow, Publish LiveSite Content, which is used with SitePublisher and LiveSite Display Services for deploying LiveSite content.
The sample application is a Web-based program that makes calls to the LSCS server to retrieve and present the content and metadata in a browser window. There are two versions of the program included: JavaScript/AJAX-based and JSP-based. The sample data contains sample XML files tagged with metadata to be deployed from a TeamSite workarea and used in conjunction with the sample application. This section describes how to install and configure the sample application, data, and workflow.
Configure TeamSite
Use this procedure to configure LSCS. To configure LSCS Authoring 1. Create a project branch and a shared workarea. 2. Log in to TeamSite as an administrative user and create a branch and workarea for the first project. The recommended branch name is /default/ main/livesitecs/samples and the recommended workarea name is shared. 3. Configure the LSCS Authoring service to recognize the TeamSite extended attributes that need to be deployed by editing lscsauth-home\ authoring\etc\deployment\config\lscs-authoring.xml and adding the following <attributeinfo> elements:
<attributeinfo name="TeamSite/Metadata/Year" type="String" facet="true"/> <attributeinfo name="TeamSite/Metadata/Category" type="String" mvfdelimiter="," facet="true"/> <attributeinfo name="TeamSite/Metadata/Month" type="String" facet="true"/>
4. Install the LSCS SPAR.
NOTE You should be logged in as an administrative user (Administrator in Microsoft Windows and root in UNIX).
226
Using the command line, change to the ts-home/install directory and run the archive installation script as follows:
Windows: \iw-perl\bin\iwperl install_archive.ipl
lscs-sample.spar <project-shared-workarea>
UNIX: /iw-perl/bin/iwperl install_archive.ipl
lscs-sample.spar <project-shared-workarea> This can take several minutes. 5. Confirm the following information:
The sample content has been stored in the project shared workarea. Metadata has been set on the sample data in the press-release/data/
200* directories. Confirm that sample files in the project-shared-workarea/press-release/data/200* directories have the following extended attributes:
TeamSite/Metadata/Month TeamSite/Metadata/Year TeamSite/Metadata/Category TeamSite/Metadata/Title Figure 69 Metadata for sample data
6. Edit the TeamSite file, deployment.properties, available in /iwadmin/ main/spars/WORKAREA/Installed/lscs-sample/t oolkit_src/ etc/conf/lscs-sample, and replace LSCSHome with the value of lscsauth-home. For example:
227
LSCSHome=C:/Interwoven/LiveSiteCSAuth
7. Copy build.xml and maketoolkit.bat (for Windows) or maketoolkit.sh (for UNIX) from /iwadmin/main/spars/WORKAREA/ Installed/lscs-sample/toolkit_src/build to /iwadmin/main/ spars/WORKAREA/Installed/lscs-sample/toolkit_src. 8. From the command prompt, change the directory to /iwadmin/main/ spars/WORKAREA/Installed/lscs-sample/toolkit_src. 9. If you are running Microsoft Windows:
Run the command maketoolkit.bat tk_war. Re-install all toolkits by running ts-home/install/
install_webapps.bat -f content_center. If you are running UNIX:

Run the command maketoolkit.sh tk_war. Re-install all toolkits by running ts-home/install/
install_webapps.sh -f content_center. This takes a few minutes. 10. The Publish to LiveSite Content Services workflow is now set up for deployment to the production instance of LSCS. To invoke it, select files/ folders and click Submit. The Select a Workflow dialog opens. 11. Verify the content deployment. To verify that the index service is running correctly, use a Web browser to connect to the following URL:
http://auth-host:auth-port/auth-context/v1/document$?q=*& project=branch vpath for sample data
12. Navigate to the workarea in ContentCenter and click the link for the index.html file. This opens a window with the sample application in the preview environment (using the content from the preview or development instance of LSCS) (see Figure 70).
228
Figure 70 Sample application
If no data appears in the sample application, it can be because the sample data was not deployed to the default project. To change the default project to match the project for the sample data, add or change the following line in lscs-conf.properties file in the lscsrt-home/runtime/webapps/ lscs/WEB-INF/classes folder:
defaultProject=vpath to branch with sample data
Example:
defaultProject=/main/livesitecs/samples
13. Restart TeamSite UI using the following command:

ts-home/bin/iwreset -ui
Configure the LSCS Sample Application

After installing the LSCS Sample SPAR, you can also install the sample application in the runtime environment and populate it with sample data.
229
To install the sample application in the runtime environment and populate it 1. Set up the Web service context file in Tomcat on the runtime server. a. Edit the lscs-sample.xml context file in lscsrt-home/install/ tomcat, changing __LSCS_HOME__ to lscsrt-home. b. Copy the file to tomcat-home/conf/Catalina/localhost. c. Restart Tomcat. 2. To deploy the sample content using the sample deployment workflow, click Submit (see Figure 71). Figure 71 Deploying sample content
3. Verify the content deployment. To verify that the index service is running correctly, use a Web browser to connect to the following URL:
http://runtime-host:runtime-port/runtime-context/v1/ document$?q=*&project=<branch vpath for sample data>
4. Explore the sample applications. After the deployment, you can view the same content using both the AJAX and JSP sample applications (see Figure 72). Use the following URLs:
230
AJAX: http://runtime-host:runtime-port/lscs-sample/
extjssample
JSP: http://runtime-host:runtime-port/lscs-sample/
jspsample Figure 72 Explore a sample application
If no data appears in the sample application, it can be because the sample data was not deployed to the default project. To change the default project to match the project for the sample data, add or change the following line in lscs-conf.properties file in the lscsrt-home/runtime/webapps/ lscs/WEB-INF/classes folder:
defaultProject=vpath to branch with sample data
Example:
defaultProject=/main/livesitecs/samples
5. Restart Tomcat.
Remove the Files Installed by the LSCS Sample SPAR

Use this procedure to uninstall LSCS toolkit files.
231
To uninstall the lscs-sample toolkit 1. In ts_home/local/config/lib/content_center/toolkits.xml remove the following entry:

<toolkit id="lscs-sample_spar" path="Y:/iwadmin/main/spars/ WORKAREA/Installed/lscs-sample/toolkit/lscs-sample.tk.war"/>
2. Reinstall ContentCenter: a. Open a command prompt and change to the ts_home/install directory. b. Run the following command:
install_webapps.ipl -f content_center
3. In the default store, delete the branch in which the SPAR is installed. 4. Delete the following workflow files:
//iwadmin/main/workflowModels/WORKAREA/iw-wa/Models/ Deploy_To_LSCS.ipm //iwadmin/main/workflowModels/WORKAREA/iw-wa/Models/ Deploy_To_LSCS_config
5. Remove the following entry from the available_models.xml.

<model debug="true" active="true" filename="Deploy_To_LSCS" name="LSCS Deploy"> <allowed> <and> <vpath-regex regex=".*"/> </and> </allowed> </model>
6. Submit //iwadmin/main/workflowModels/WORKAREA/iw-wa.
Content and Metadata Deployment

This section details the deployment process and customizing deployments.
Deployment Process Overview

The LSCS deployment components coordinate the process of collecting content and metadata from the TeamSite environment, securely transferring it to the runtime environment and making it available to the Web site presentation layer via the LSCS Web Service API. This process can be initiated using the startdeploy command line scripts or the provided TeamSite workflows. When initiated, the components perform the following steps (see Figure 73).
232
Phase 1Deployment Launcher

Identifies assets to be deployed using a submitted file list (workflow), an override manifest file (script), or area-difference comparison (default). Extracts the assets and metadata from TeamSite to a temporary directory for deployment. Calls the OpenDeploy Web services to create a new deployment job from the template deployment configuration, providing parameters from either the invocation or the deployment configuration files.
Phase 2OpenDeploy Base Server, Receiver and Import Delivery Adapter

Securely transfers the content and metadata from the authoring environment to the runtime environments. Notifies the LSCS Web service of a new deployment transaction.
Phase 3LSCS Web Service Import Resource

Stores transaction information in the relational database. Indexes metadata in the embedded IDOL database. Notifies the Import Delivery Adapter of success or failure. If all runtime nodes import successfully, a commit deployment runs to notify all runtime nodes to commit. If any runtime nodes import fails, the import adapter notifies all nodes to rollback the update.
Phase 4OpenDeploy Base Server, Receiver and Commit Delivery Adapter

Notifies the LSCS Web service that the update should be committed If all runtime nodes commit successfully, the deployment job completes successfully If any runtime nodes commit fails, the commit adapter notifies all nodes to rollback the update.
233
Figure 73 LiveSite Content Services deployment process

Deployment Launcher OpenDeploy Base Server OpenDeploy Receivers LSCS Web Service
2, 4
2, 4 3, 4
TeamSite Web Service
Runtime File system
IDOL
SQL
Customize Deployments
The deployment process is configured using the deployment-source.properties and lscs-authoring.xml files located in lscs-home/authoring/etc/deployment/config. In addition, the LSCS TeamSite workflows use the deployment-nodes.properties inside the workflow helper toolkit.
Override Default Values

When launching the deployment process via the startdeploy script, you can override the default parameter values in the deployment-source.properties by providing command line arguments of the form -<property-name> <property-value>.
NOTE Be sure to enclose the property value in quotes so that it is recognized by the operating system as a single parameter value.
Control Comparison and Faceted Search

By default, TeamSite extended attributes are deployed as single-valued searchable text fields. To enable comparison (< or >) or faceted (aka, parametric) search on a field, the field name must be added to the /authoring/etc/ deployment/config/lscs-authoring.xml file. This file allows specific fields to be treated as numeric values, dates or strings (text). In addition, it allows
234
for the field to be enabled for faceted search. Lastly, it enables a field to be split into multiple separate values using a delimiter character such as comma or vertical bar.
<attributetypemap> <attributeinfo name="price" type="numeric" /> <attributeinfo name="BottledDate" type="date" /> <attributeinfo name="country" type="text" mvfdelimiter=","/> <attributeinfo name="rating" type="string" facet="true"/> </attributetypemap> NOTE The project repository should be reset after each change to the lscs-authoring.xml file.
For details on the override manifest format, refer to the LiveSite Content Services Technical Reference Guide.
Fan-out Deployment
LSCS supports OpenDeploy configurations that deliver content and metadata to multiple runtime servers simultaneously. For example, LSCS can be configured to deploy content to separate servers running in different data centers in North America, Asia and Europe to provide customers in different regions a faster browsing experience. To configure the base server configuration 1. Add <node> entries for each target production server in the OpenDeploy host configuration file (odnodes.xml). 2. Add multiple node references to <replicationFarm> in the LSCS Area-Difference deployment configuration file (OD-Home/conf/lscs/ teamsite-areadiff.xml). For example:
<replicationFarm name="MYFARMNAME"> <nodeRef useNode="$destinationNode"/> <nodeRef useNode="lscs-north-america"> <targetRules area="C:/var/lscs/content"/> </nodeRef> <nodeRef useNode="lscs-asia"> <targetRules area="C:/var/lscs/content"/> </nodeRef> </replicationFarm>
3. For multiple destination nodes, specify sets of parameters under the odAdapter "parameter" attribute.
235
Each set of parameters is separated by a LSCS_RUNTIME_SEPARATOR delimeter.The parameter set that does not contain the lscsRuntimeCanonicalHostName parameter is considered a global set. This means, the setting applies to all destination nodes.You can specify node-specific parameters by using the LSCS_RUNTIME_SEPARATOR delimiter to distinguish the set from the global set or other nodes, and using the lscsRuntimeCanonicalHostName parameter to uniquely identify one destination node. For example:
<odAdapter name="LSCS Import Delivery Adapter" class="com.interwoven.wcm.iwrr.deployment.adapter.delivery.Impo rtDeliveryAdapter" parameter=" lscsRuntimeTransport=$lscsRuntimeTransport; lscsRuntimeHostname=$lscsRuntimeHostname; lscsRuntimePort=$lscsRuntimePort; lscsRuntimeContext=$lscsRuntimeContext; deploymentContextId=$deploymentContextId; destinationArea=$destinationArea; projectName=$projectName; lscsRuntimeKeyStore=$lscsRuntimeKeyStore; lscsRuntimeKeyStoreType=$lscsRuntimeKeyStoreType; lscsRuntimeKeyStorePassword=$lscsRuntimeKeyStorePassword ; lscsRuntimeTrustStore=$lscsRuntimeTrustStore; lscsRuntimeTrustStoreType=$lscsRuntimeTrustStoreType; lscsRuntimeTrustStorePassword=$lscsRuntimeTrustStorePass word; lscsRuntimeProtocolHandler=$lscsRuntimeProtocolHandler LSCS_RUNTIME_SEPARATOR lscsRuntimeCanonicalHostName=lscs-north-america.interwov en.com; lscsRuntimeTransport=http; lscsRuntimeHostname=lscs-north-america; lscsRuntimePort=1876; lscsRuntimeContext=lscs; deploymentContextId=$deploymentContextId; destinationArea=C:/var/lscs/content; projectName=$projectName; lscsRuntimeKeyStore=my_runtime_keystore_1; lscsRuntimeKeyStoreType=$lscsRuntimeKeyStoreType; lscsRuntimeKeyStorePassword=password; lscsRuntimeTrustStore=my_runtime_truststore_1; lscsRuntimeTrustStoreType=$lscsRuntimeTrustStoreType; lscsRuntimeTrustStorePassword=password; lscsRuntimeProtocolHandler=$lscsRuntimeProtocolHandler" LSCS_RUNTIME_SEPARATOR lscsRuntimeCanonicalHostName=lscs-asia.interwoven.com;
236
lscsRuntimeTransport=http; lscsRuntimeHostname=lscs-asia; lscsRuntimePort=1876; lscsRuntimeContext=lscs; deploymentContextId=$deploymentContextId; destinationArea=C:/var/lscs/content; projectName=$projectName; lscsRuntimeKeyStore=my_runtime_keystore_1; lscsRuntimeKeyStoreType=$lscsRuntimeKeyStoreType; lscsRuntimeKeyStorePassword=password; lscsRuntimeTrustStore=my_runtime_truststore_1; lscsRuntimeTrustStoreType=$lscsRuntimeTrustStoreType; lscsRuntimeTrustStorePassword=password; lscsRuntimeProtocolHandler=$lscsRuntimeProtocolHandler" async="no" logLevel="DEBUG"/> </odAdapterSet>
4. Add multiple node references to <replicationFarm> in the LSCS Commit deployment configuration file (OD-Home/conf/lscs/ commit-deploy.xml). For example:
<replicationFarm name="MYFARMNAME"> <nodeRef useNode="$destinationNode"/> <nodeRef useNode="lscs-north-america"> <targetRules area="C:/var/lscs/content/dummytarget"/> </nodeRef> <nodeRef useNode="lscs-asia"> <targetRules area="C:/var/lscs/content/dummytarget"/> </nodeRef> </replicationFarm>
5. Edit the LSCS commit deployment configuration adapter parameters as described in Step 3 on page 235. 6. Add multiple node references to <replicationFarm> in the LSCS Rollback deployment configuration file (OD-Home/conf/lscs/rollback.xml). For example:
<replicationFarm name="MYFARMNAME"> <nodeRef useNode="$destinationNode"/> <nodeRef useNode="lscs-north-america"> <targetRules area="C:/var/lscs/content/dummytarget"/> </nodeRef> <nodeRef useNode="lscs-asia"> <targetRules area="C:/var/lscs/content/dummytarget"/> </nodeRef> </replicationFarm>
237
7. Edit the LSCS Rollback deployment configuration adapter parameters as described in Step 3 on page 235.
Administrative Tasks
This section contains information about reinitializing a project repository and how to restrict access to LiveSite Content Services.
Reinitialize a Project Repository

To reset/reinitialize a project repository, you must perform the next procedure.
NOTE Reinitializing makes the project inaccessible on the target host.
To reset/reinitialize a project repository 1. Stop the application context using the Java Servlet Container tools. 2. Reinitialize the RDBMS data used by this project by running the appropriate SQL script from <lscs-home>/install/sql. 3. Reinitialize the IDOL data used by this project by running:
http://<runtime-host>:10001/
DREDELDBASE?DbName=<project>
http://<runtime-host>:10001/
DREDELDBASE?DbName=<project>Archive 4. Delete all content from the project file store. 5. Start the application context using the Java Servlet Container tools. 6. Perform a full content deployment to the reinitialized context by running the startdeploy script with an empty edition as the previous edition.
238
Administrative Tasks
Restrict Access
To restrict access to a project, configure the project security in the Web application descriptor (<project>/WEB-INF/web.xml). Refer to your Java Web Application Container for details on the syntax and in configuring the user database for authentication.
NOTE The deployment logic only supports BASIC authentication and requires an additional configuration file named deployment.properties in the runtime <od-home>/ userlib directory. The entries are: <project-context>.username=<username> <project-context>.password=<password>
The fragment below illustrates the web.xml portion of this process:

<security-constraint> <web-resource-collection> <web-resource-name>LSCS Client</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <auth-constraint> <role-name>lscs-client</role-name> </auth-constraint> </security-constraint>  <login-config> <auth-method>BASIC</auth-method> <realm-name>lscs-realm</realm-name> </login-config>  <security-role> <description> LiveSite Content Services Access </description> <role-name>lscs-client</role-name> </security-role>
239
Enable Secure Communications on the Authoring Server

To enable secure communication on the LSCS Authoring server, follow the procedures in these sections:

Enable Secure Communication on the OpenDeploy Base Server on page 240 Configure the Authoring Server to Access Runtime through SSL on page 244
NOTE Before setting up secure communications with the Authoring server, you must set up security on the Runtime server. Refer to the Web Solutions Runtime Components Installation Guide.
Enable Secure Communication on the OpenDeploy Base Server

Communication between the Authoring server and OpenDeploy Base server can be secured through HTTPS Transport Security protocol. To enable secure deployment of content from the LSCS authoring server to the OpenDeploy Base server, follow the procedures in these sections:

Enable HTTPS Transport on OpenDeploy Web Services on page 240 Set up the LSCS Authoring Server Client Certificate on page 243 Configure the LSCS Authoring Server on page 244
Enable HTTPS Transport on OpenDeploy Web Services

To enable HTTPS transport on OpenDeploy Web services, follow the procedures in these sections:

Create a Keystore File on page 241 Enable Web Services for the OpenDeploy Server on page 242
240
Create a Keystore File To use HTTPS transport for OpenDeploy Web services, you must create a keystore file named serverkeys in the od-home/websvc/conf/serverkeys directory. The file must contain the certificate that is specified in the httpsTransport element in the odbase.xml or odrcvr.xml file. To create a keystore file 1. Navigate to the od-home/bin directory. 2. To create the certificate, run the following command:
iwodkeystorecreatecert -c myODcert -p myODcertpd
where,
-c is the certificate name. -p is the certificate password.
This creates the certificate in the od-home/websvc/conf/serverkeys keystore file. If the serverkeys keystore file does not exist, it is created. If the serverkeys keystore file already exists, the new certificate is added to the existing serverkeys file. 3. At the prompts, type keystore password and certificate information. For example:
Enter keystore password: password What is your first and last name? [Unknown]: John Smith What is the name of your organizational unit? [Unknown]: Application Development What is the name of your organization? [Unknown]: Autonomy What is the name of your City or Locality? [Unknown]: San Jose What is the name of your State or Province? [Unknown]: CA What is the two-letter country code for this unit? [Unknown]: US Is CN=John Smith, OU=Application Development, O=Autonomy Interwoven, L=San Jose, ST=CA, C=US correct? [no]: yes Finished creating certificate test in "C:\Interwoven\ OpenDeployNG\websvc\conf\serverkeys"
4. To verify the certificate is in the serverkeys file, run the following command:
iwodkeystorelist
241
Enable Web Services for the OpenDeploy Server After the keystore file is created, you must update the OpenDeploy server configuration file to enable Web services for the OpenDeploy server. To update the OpenDeploy server configuration file 1. Open the odbase.xml or odrcvr.xml file and remove the comments preceding the webServices element. 2. Enable transport in the webServices element by setting the following attributes in the httpTransport element and/or httpsTransport element:
Port. The port number used for HTTP or HTTPS transport. If you specifiy
both HTTP and HTTPs transport elements, the port numbers must be different.
Host. The host name of OpenDeploy Base server. certPasswd. The password to myODcert certificate. This is only
required when HTTPS transport is enabled.

storePasswd. The password to keystore serverkeys. This is only
required when HTTPS transport is enabled. For example:

<webServices enabled="yes" > <httpTransport port="9273" host="myhost"> </httpTransport> <httpsTransport port="9274" host="myhost" certPasswd="myodcertpd" storePasswd="myodstorepd"> </httpsTransport> </webServices>
To disable HTTP or HTTPs transport, remove the appropriate element. 3. Restart the OpenDeploy server to reflect these changes. 4. Check the OpenDeploy server log:
<od-home>/log/<hostname>_odbase.log <od-home>/log/<hostname>_odrcvr.log
Messages are logged there on which Web services transports have been started. 5. After the Web service has started, you can view the Web service's WSDL file from a browser using the following URLs:
242
If HTTP transport is started:

http://<http-hostname>:<http-port>/iw/services/cd/1.2/ opendeployservice?wsdl
If HTTPS transport is started:

https://<https-hostname>:<https-port>/iw/services/cd/1.2/ opendeployservice?wsdl
Set up the LSCS Authoring Server Client Certificate

You must now set up the LSCS Authoring Server Client Certificate to connect to the OpenDeploy Web services through HTTPS transport. To set up LSCS Authoring Server Client Certificate to connect to OpenDeploy Web services 1. Extract the certificate from the OpenDeploy Web services's keystore serverkeys file. On UNIX, you need to be root. a. Go to the od-home/bin directory. b. Run the following command:
iwodkeystoreexportcert -c myodcert
This extracts the specified certificate from od-home/websvc/conf/ serverkeys and stores it in the file od-home/websvc/conf/ certName.crt. For example:
od-home/websvc/conf/myodcert.crt
2. Copy the certificate file to the LSCS authoring server deployment configuration directory, or any directory you would like to store the certificate. For example:
LiveSiteCSAuth-home/authoring/etc/deployment/config/ myodcert.crt
3. Create the OpenDeploy Web services client keystore using the certificate. You must create a keystore that the Apache Axis Web services client can use. a. Use Javas keytool command to create the client keystore. For example, in LiveSiteCSAuth-home/authoring/etc/deployment/config directory, run the following command:
od-home/jre/bin/keytool -import -v -file myodcert.crt -keystore clientkeystore -storepass mykeystorepwd -alias myodcert
b. At the following prompt, type y:

Trust this certificate? [no]: y
243
You should see the file clientkeystore created. c. To verify the certificate is in clientkeystore, run the following command:
od-home/jre/bin/keytool -list -v -keystore clientkeystore -storepass mykeystorepwd
Configure the LSCS Authoring Server

You must now specify the OpenDeploy security information in the LSCS Authoring server. Modify the OPENDEPLOY SERVICE_PROPERTIES section of the deployment-source.properties file. The file is stored in the LiveSiteCSAuth-home\authoring\etc\deployment\config\ directory. For example:
################################ OPENDEPLOY SERVICE PROPERTIES ################################ # the host on which the Interwoven OpenDeploy Service runs OpenDeployService_Hostname=myhost # the transport to send commands to the Interwoven OpenDeploy Service OpenDeployService_TransportType=https # the port on which the Interwoven OpenDeploy Service runs OpenDeployService_Port=9274 # the client keystore location for the OpenDeploy web services when transport is set as https OpenDeployService_ClientKeystore=path_to_od_client_keystore
where, path_to_od_client_keystore is LiveSiteCSAuth-home/ authoring/etc/deployment/config/clientkeystore.
Configure the Authoring Server to Access Runtime through SSL

To configure the LSCS Authoring server to access LSCS Runtime server through an SSL connection 1. In the lscs-authoring.xml file, set lscsRuntimeTransport to https for global branch-level preview or production nodes configuration.
NOTE If lscsRuntimeTransport is not defined in global- or branch-level configuration, it is set to http. If it is set to https in the global configuration, and is not set or is set to "" in the branch-level configuration, then the global https transport is used.
244
2. If lscsRuntimeTransport is set to true, configure the following attributes:

lscsRuntimeKeyStore. This is the location of the client keystore. For
example, LiveSiteCSRT-home\runtime\etc\client.jks.
lscsRuntimeKeyStoreType. This is the client keystore type. The type
is jks by default.
lscsRuntimeKeyStorePassword. This is the client keystore password
you used to protect your keystore.

lscsRuntimeTrustStore. This is the client truststore, which contains
the server public certificate. For example, LiveSiteCSRT-home\ runtime\etc\client.jks.

lscsRuntimeTrustStoreType. This is the client truststore type. The
type is jks by default.

lscsRuntimeTrustStorePassword. This is the client truststore
password you used to protect your truststore. For example, the global or branch configuration could look like this:
<production lscsContext="lscs" lscsRuntimeTransport="https" lscsRuntimePort="9443" destinationArea="C:/LSCSRT-Store" destinationNode="LSCSRuntime" lscsRuntimeKeyStore="<LiveSiteCSRT-home>\\runtime\\etc\\ client.jks" lscsRuntimeKeyStoreType="jks" lscsRuntimeKeyStorePassword="password" lscsRuntimeTrustStore="<LiveSiteCSRT-home>\\runtime\\etc\\ client.jks" lscsRuntimeTrustStoreType="jks" lscsRuntimeTrustStorePassword="password" />
NOTE On Windows, you must use \\ as the file separator.
3. For better security, the password defined in the lscsRuntimeKeyStorePassword and lscsRuntimeTrustStorePassword attributes can be protected using the encryptpassword script LiveSiteCSAuth-home\install\bin\ encryptpassword.bat.
245
After encrypting the KeyStore password and TrustStore password, update the lscs-authoring.xml file. The encrypted password must be enclosed in ENC( and ).
lscsRuntimeKeyStorePassword="ENC(encrypted_password)" lscsRuntimeTrustStorePassword="ENC(encrypted_password)"
The OpenDeploy receiver on the LSCS Runtime host should be restarted whenever the following security attributes are changed on the Runtime node defined in lscs-authoring.xml:
lscsRuntimeTransport lscsRuntimeKeyStore lscsRuntimeKeyStoreType lscsRuntimeKeyStorePassword lscsRuntimeTrustStore lscsRuntimeTrustStoreType lscsRuntimeTrustStorePassword
Now you are ready to deploy with a secure connection from the LSCS Authoring server to the Runtime server through the LSCS delivery adapter.
246
CHAPTER 12
Troubleshooting
This section covers troubleshooting and supplemental information for Web Solutions Authoring Components.

TeamSite ReportCenter
TeamSite
This section provides the following troubleshooting information.

Troubleshoot the TeamSite 7.x Installation Installed Diagnostics Clean or Remove the Installation Manually Make iwserver.exe 3GB Switch Aware (Windows Only) Configure the Database Manually Compile the UVFS Module Troubleshoot the IIS Web Server Perform Post-Installation Steps Manually Preserve Custom Configurations for PLC Adjust the Java Virtual Machine (JVM) Stack Size
247
Chapter 12 Troubleshooting
Troubleshoot the TeamSite 7.x Installation

This section points you to various logs that you can reference as you evaluate why your TeamSite installation failed. It also presents steps that you can follow to avoid repeating the entire installation process on a Linux machine.
Use TeamSite Logs to Evaluate your Installation Results

If your TeamSite 7.x installation is not successful, the following logs will assist you in your troubleshooting efforts. This information is applicable to TeamSite installations on all platforms. Regardless of whether your installation is successful, you may find it helpful to review these logs for errors, especially for errors that occurred when scripts were executed during installation. If you identify any script execution failures, supply that information to Autonomy Customer Support.
<iwinstall>/logs/installer.log and /tmp/stderr.log. Check these logs if the TeamSite installer quits or the installation reports an error. Also, check them at the end of a successful installation for any noticeable warnings. <iwhome>/local/logs/iwserver.log and <iwhome>/local/logs/ iwtrace.log. Check these logs for errors if the iwserver service does not start. <iwhome>/local/logs/iwui/*.log and <ApplicationContainerHome>/server/default/logs/ server.log. Check these logs for errors if the iwserver service is running, but the UI does not start. /Interwoven/iwinstall/private/config/Inventory.XML and installer.properties. These files provide information about the components that were added and their status. <ApplicationContainerHome>/server/default/logs/ commonservice.log. Useful for debugging common services problems. <iwhome>/local/logs/iwui/content_center.log. <ApplicationContainerHome>/server/default/logs/ iwjboss_server_err.log and iwjboss_server_out.log. These logs provide information about any JBoss related errors, general installation problems, and indicate if the service is not up. <ApplicationContainerHome>/server/default/logs/ cssdk_soap.log. Use this log to debug cssdk_soap issues. You can enable additional debugging by updating CSSDKSoapServices/config/ log4j.xml and restarting the UI.
248
TeamSite
If you review the preceding information sources and do not find any errors, you can also use the following commands to check the services status:

<iwstat> gives iwserver service status <iwutildstat> gives utild service status
Address Interwoven Registry Service Problems

For Interwoven Registry (IR) Service problems, run IWIRStat (/Interwoven/ CommonServicesClient/bin/iwirstat). If you receive any errors, verify that:
The JBoss service is up and running. Check all of the logs listed in Use TeamSite Logs to Evaluate your Installation Results on page 248 for errors that may prevent the JBoss service from starting, because many of the services are hosted through JBoss. IW Database instances are up and running. Components are correctly registered by running /Interwoven/ CommonServicesClient/bin/iwirmapping. IWIRMapping output should match with IR_SERVICEINFO table for respective component (TeamSite, AdminstationConsole, and so on.). Use the \Interwoven\CommonServicesClient\bin\iwirencryption command to decrypt and check the values.
Complete an Unsuccessful Installation

If the TeamSite installation fails in the post-reboot phase on Windows or Solaris, or in the final phase on Linux (no reboot required), you can use the procedure in this section to avoid having to completely reinstall TeamSite. Installing TeamSite on the Linux environment does not require a reboot. Consequently, if your TeamSite installation is not successful, you must completely re-start the installation process. However, you can complete the following steps to avoid repeating the entire installation process (because you cannot reboot the Linux machine). You can also use the troubleshooting information presented earlier in this section to evaluate why your TeamSite installation failed. To avoid repeating the entire installation process, perform the next procedure to complete your TeamSite installation. For Windows, use \ in file paths instead of /. To avoid repeating the installation process 1. (Linux only) Add execute permission to all scripts in <iwhome>/install/ livesite/install_scripts (chmod +x <iwHome>/install/ livesite/install_scripts/*.sh).
249
2. Run <iwHome>/install/livesite/install_scripts/ sitepub_component_install.sh. 3. Run install_webapps -f (<iwhome>/install/ install_webapps.ipl). 4. Run <iwHome>/install/livesite/install_scripts/ sitepub_mount_install.sh. 5. Run <iwHome>/install/livesite/install_scripts/ sitepub_role_install.sh. 6. Copy the database (SQLServer) drivers from <tsreport>/lib/ to the following locations:
<iwHome>/servletd/lib <iwHome>/httpd/webapps/db/drivers
7. Configure the following information: <iwHome>/iw-perl/bin/iwperl <iwHome>/tsreport/bin/ iwconfigtsreport.ipl -dbtype=<databasetype> -dbserver=<database server> -dbport=<database port>-dbname=<tsreportsDbName> -dbuser=<TSReportsdbUser> -dbpasswd=< TSReportsdbUser > <iwHome>\local\logs -jndiport=3035 -iwHome=<iwHome> <databasetype> - database type (mssql | oraclerac | oracle | mysql | db2 ) 8. Create a row for the TSREPORTS component (with the componentName column set to TSREPORTS). With the exception of the dbType field and the userPwd field, this row contains standard fields. 9. In the IR_DBINFO table, create a row for the TSREPORTS component (with the componentName column set to TSREPORTS). With the exception of the dbType field and the userPwd field, this row contains standard fields. Possible dbType (Database) values include:
mssql - MSSQL Server mysql - MySql oracle - Oracle oraclerac - Oracle RAC db2 - IBM DB2 custom - any other db
250
TeamSite
NOTE To obtain the encrypted password for the userPwd field: Go to iw-home\CommonServicesClient\bin and execute iwirencryption.bat -e. At the prompt to type the text to encrypt, type in the db password and press ENTER. You are presented with the encrypted text. Copy only the encrypted text without any spaces before and after and paste it into the IR_DBINFO table.
10. Register TeamSite by running Iwirregister and supplying the following information:
Component: TeamSite Version: TeamSite version getting installed. Install dir: iwHome Hostname: customer machine name
For example, to register the InterwovenAdministrationConsole component: Iwirregister.sh -c "TeamSite" "Autonomy TeamSite" "<Server Hostname>" "C:\Interwoven\TeamSite" "" "" "lin" If the registration is successful, IWIRREGISTRY will return the service id. 11. Create the file <iwHome>/etc/serviceid, then copy the IWIRREGISTRY service id string (returned as part of Step 10) into it. You have now updated the TeamSite component statuses to COMPLETED, similar to infrastructure components. This completes your TeamSite installation on a Linux machine.
Installed Diagnostics
The TeamSite Diagnostics tool is a Perl script that collects information about your TeamSite installation. It generates an XML file from which you can view the state of the entire TeamSite system. You may be asked to provide the XML file to an Autonomy Customer Support representative when filing a case. The script is located in the iw-home/install directory. The Solaris script is ts_diagnostics_sol.ipl, the UNIX script is ts_diagnostics.lnx.ipl, and the Windows script is ts_diagnostics_win.ipl. Set the PATH environment variable to ts-home/bin before running the diagnostic tool. Run the script from the command line. It generally takes under five minutes to run on one Content Store. Larger and additional Content Stores require additional time.
251
Open the XML output file using Internet Explorer, which renders browsable HTML.
NOTE An older version of xml transformation, <xsl:stylesheet xmlns:xsl="http://www.w3.org/ TR/WD-xsl"> is used for compatibility with IE 5.x and 6.x. The file does not render in Netscape/Mozilla.
Solaris
The following commands run as part of the ts_diagnostics_sol.ipl and ts_diagnostics_lnx.ipl scripts:
iwgetstore /usr/bin/uptime $home/bin/iwserver -v iwgetlocation -c iwconfig $iwhome/bin/iwquerytasks netstat -naP tcp | grep -v TIME_WAIT /usr/sbin/ifconfig -a /usr/bin/pkginfo /usr/bin/showrev -a /usr/sbin/modinfo cat /var/adm/messages /usr/bin/ps -eo pid,ppid,uid,gid,vsz,rss,pmem,pcpu,s,time,stime,etime,args /usr/bin/ps -ef | grep iw /usr/proc/bin/ptree /usr/bin/nfsstat -n /usr/bin/nfsstat -r /usr/sbin/pwck 2>&1 /usr/sbin/grpck 2>&1 /usr/sbin/showmount -a /usr/sbin/fuser -cu $iwmount 2>&1 /usr/bin/w /usr/sbin/swap -s; /usr/sbin/swap -l /usr/bin/iostat -E /usr/bin/mpstat 5 6 /usr/bin/vmstat 5 6 /usr/bin/iostat 5 6 /usr/sbin/prtconf /usr/bin/uname -m /usr/platform/$uname/sbin/prtdiag -v /usr/bin/uname -m /usr/platform/$uname/sbin/prtdiag -v /usr/sbin/psrinfo file /core ls -l /core file $iwhome/bin/core
252
TeamSite
ls -l $iwhome/bin/core file $iwhome/httpd/iw-bin/core ls -l $iwhome/httpd/iw-bin/core /usr/bin/uname -a $ddhome/bin/iwdd.ipl -v $odhome/bin/iwodstart -v $mthome/install/iw.mtserver -v df -k $iwstore 2>&1 df -k $iwhome 2>&1 df -k 2>&1
Windows
The following commands run as part of the ts_diagnostics_win.ipl script:
$iwhome\\bin\\iwgetstore iwserver -v 2>&1 $iwstat -c 2>&1 $iwhome/bin/iwquerytasks iwgetwfobj $iwhome/bin/iwquerytasks 2>&1 < c:/stalled.txt netstat -na ipconfig /all winmsd /f /a ; iwgetstore cmd /c "dir $drv:\\"
Clean or Remove the Installation Manually

If you cannot install TeamSite because of a previous installation and you cannot uninstall because it has been removed or deleted, you can clean or remove the installation manually. The next procedure removes all traces of TeamSite from your system.
Clean or Remove the Installation on Linux

Use this procedure to manually uninstall TeamSite on a Linux platform. To remove the TeamSite installation on Linux 1. Delete /etc/defaultiw* files. 2. Delete the <ts-home> directory. If you have any customizations, first create a backup of the whole directory. 3. Delete all the scripts in /etc/init.d/ that begin with iw* (iw.samba, etc.). 4. Delete /etc/iw.* files. 5. Delete /iwinstall directory.
253
6. Delete the K and S (Kill and Start) scripts in /etc/rc2.d that pertain to TeamSite. Use ls *iw* to list those ''''iw'''' scripts that need to be deleted:
# ls *iw* K16iw.server K99iw.local S70iw.wfs
Delete the following files from /etc/rc2.d/ directory:

/etc/rc2.d/K16iw.server /etc/rc2.d/K99iw.server /etc/rc2.d/S70iw.wfs
7. Delete S (Start) scripts in /etc/rc3.d directory that pertain to TeamSite. Use ls *iw* to list those ''''iw'''' that need to be deleted:
# ls *iw*

/etc/rc3.d/S30iw.server /etc/rc3.d/S50iw.samba /etc/rc3.d/S99iw.local Remove TeamSite entry row from database IR_SERVICEINFO table.
8. Reboot the server. You can now perform a fresh installation of TeamSite on the server. 9. Start JBOSS service if required. It is stopped by default after the uninstall.
Clean or Remove the Installation on Solaris

Use this procedure to manually uninstall TeamSite on a Solaris platform. To manually remove TeamSite installation on Solaris 1. CD to /etc and run ls defaultiw*. Delete the following files from the /etc directory:
/etc/defaultiwhome /etc/defaultiwlog /etc/defaultiwtrace /etc/defaultiwelog /etc/defaultiwinstall /etc/defaultiwmount /etc/defaultiwstore
2. Delete the entire ''ts-home'' directory (that is, /opt/ts-home). 3. Delete /usr/bin/iwgethome. 4. Delete /etc/iw directory and the following lines are also deleted:
254
TeamSite
# cd /etc/iw # ls iwfs_hijack iwovwfs.devlink.tab wfs_device_path Delete iw* content in etc/init.d by running ls iw* in etc/init.d as follows: # cd /etc/init.d # ls iw*
5. Delete the following files from /etc/init.d/ directory:

/etc/init.d/iw.local /etc/init.d/iw.samba /etc/init.d/iw.server /etc/init.d/iw.wfs /etc/init.d/iw.local.bak /etc/init.d/iw.samba.bak /etc/init.d/iw.server.bak /etc/init.d/iw.wfs.bak
6. Delete /usr/kernel/drv/iwovwfs. This is the iwovwfs device driver that was copied from /iwov/ts-home/kernel/drv/wfsdrv32.2.9 to / usr/kernel/drv/iwovwfs during the initial install. 7. Delete /usr/kernel/drv/sparcv9/iwovwfs. This is the iwovwfs device driver that was copied from /iwov/ts-home/kernel/drv/ wfsdrv64.2.9 to /usr/kernel/drv/sparcv9/iwovwfs during the initial install. 8. Delete /usr/kernel/drv/iwovwfs.conf. This is the iwovwfs device driver that was copied from /iwov/ts-home/kernel/drv/ iwovwfs.conf to /usr/kernel/drv/iwovwfs.conf during the initial install. 9. Delete /etc/iwovwfs.devlink.tab. This is the iwovwfs device driver that was copied from /iwov/ts-home/kernel/drv/ iwovwfs.devlink.tab to /etc/iwovwfs.devlink.tab during the initial install. 10. Delete /dev/iwovwfs symlink. 11. Delete K and S (Kill and Start) scripts in /etc/rc2.d that pertain to TeamSite. Use ls *iw* to list those ''''iw'''' scripts that need to be deleted:
# ls *iw* K16iw.server K99iw.local S70iw.wfs

/etc/rc2.d/K16iw.server /etc/rc2.d/K99iw.local /etc/rc2.d/S70iw.wfs
255
12. Delete K and S (Kill and Start) scripts in /etc/rc2.d that pertain to TeamSite. Use ls *iw* to list those ''''iw'''' scripts that need to be deleted:
# ls *iw*

/etc/rc3.d/S16iw.server /etc/rc3.d/S50iw.samba /etc/rc3.d/S99iw.local
13. Remove TeamSite entry row from database IR_SERVICEINFO table. 14. From the shell prompt, run init 6 to reboot the system.You can now perform a fresh installation of TeamSite on the server. 15. Start JBOSS service if required. It is stopped by default after the uninstall.
Clean or Remove the Installation on Windows

Use this procedure to manually uninstall TeamSite on a Windows platform. To manually remove TeamSite installation on Windows 1. Stop all TeamSite related processes. 2. Delete or rename ts-home folder. 3. Delete or rename iwinstall folder. 4. Rename iw-store folder. 5. Delete iwsetuid.dll and iwgethome.exe from C:\WINDOWS\ system32. 6. Delete IWTemp folder. 7. Delete iwfsd.sys, iwfsd.pdb, iwfsd.map and iw_tmp from C:\ WINDOWS\system32\drivers. 8. Delete or rename C:\Program Files\Interwoven folder.
CAUTION Delete the Registry entries carefully. Autonomy recommends backing up the Registry before you delete any entries.
9. From regedit, delete iwinstall, TeamSite, and TeamSite Templating from:

HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven
10. From regedit, delete all iw* folders from the following locations:
256
TeamSite
HKEY_LOCAL_MACHINE \SYSTEM\ CurrentControlSet\Services HKEY_LOCAL_MACHINE \SYSTEM\ ControlSet001\Services HKEY_LOCAL_MACHINE \SYSTEM\ ControlSet002\Services
Reboot the windows system before you install the TeamSite again.
Make iwserver.exe 3GB Switch Aware (Windows Only)

Operating systems based on Microsoft Windows NT technologies always provide applications with a flat 32-bit virtual address space that describes 4 GB of virtual memory. The address space is usually split, so that 2 GB of address space is directly accessible to the application and the remaining 2 GB is only accessible to the Windows OS. With the 3GB switch, Windows kernel uses only 1GB and the applications use the remaining 3GB. To make iwserver.exe 3GB switch aware 1. Shut down all the TeamSite processes. 2. Back up iwserver.exe and boot.ini files. 3. Edit boot.ini file add the /3GB switch and /Userva=2800, save the file, and reboot the server. Example:
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /NoExecute=OptOut /3GB / Userva=2800
4. Run editbin.exe /LARGEADDRESSAWARE iwserver.exe with which iwserver.exe becomes 3GB aware. editbin.exe is a component of Microsoft Visual Studio. Before running this step, ensure you have installed Microsoft Visual Studio. If not, perform the following steps: a. Copy the iwserver.exe to the machine where you have Microsoft Visual Studio. b. Run the command editbin.exe /LARGEADDRESSAWARE iwserver.exe. c. Copy back the 3GB aware iwserver.exe to your production server. 5. In iw.cfg under the [iwserver] section, change the cache size to 200000.
257
See the following example:

[iwserver] cachesize=200000
6. Start all the TeamSite processes. In future, if you install any regular TeamSite maintenance updates, you have to rerun the steps listed above without fail. Otherwise, your iwserver.exe is not 3GB aware. To find out more about 3GB switch, refer to following Microsoft links:

http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx http://msdn.microsoft.com/en-us/library/wz223b1z(VS.80).aspx http://support.microsoft.com/kb/316739
Configure the Database Manually

If the installer fails to configure the database connection credentials for TeamSite Reports or OpenDeploy Reports due to any reason, you can configure them manually using the js-jboss-ds.xml file located at Interwoven\ ApplicationContainer\server\default\deploy.
Compile the UVFS Module

Before installing TeamSite on Linux, download and compile uvfs version 2.x.x from the following location:
http://sourceforge.net/projects/uvfs
Compile the uvfs module on the same system that hosts the TeamSite installation to insure compatibility, and ensure that the files are located somewhere on the TeamSite server system. To compile the uvfs module 1. Ensure that gmake is installed. 2. Extract the uvfs source code.
tar -xvzf uvfs_2.x.x.tar.gz
3. Change to the extracted directory.

cd uvfs_2.x.x
4. Run gmake without any arguments.

gmake
258
TeamSite
During the TeamSite installation procedure, you receive a prompt to specify the location of the files so that the TeamSite installer can install them in ts-home/ kernel. To manually install the uvfs module to use with TeamSite 1. Copy pmfs.ko and uvfs_signal files to the ts-home/kernel directory. 2. Run gmake. 3. Verify that pmfs.ko and uvfs_signal files are present in the uvfs_2.x.x folder.
Troubleshoot the IIS Web Server

If you use an IIS Web server and SSI requests are not executing properly, use the next procedure. To troubleshoot the IIS Web server 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.
Perform Post-Installation Steps Manually

If the post-install process stops, run the following .bat files to manually perform the post-install process:
C:\Interwoven\TeamSite\install\livesite\install_scripts\ sitepub_component_install.bat C:\Interwoven\TeamSite\install\livesite\install_scripts\ sitepub_mount_install.bat C:\Interwoven\TeamSite\install\livesite\install_scripts\ sitepub_role_install.bat C:\Interwoven\iwinstall\bin\IWOVInstaller-<platform>.exe f C:\ Interwoven\iwinstall\private\config\installer.properties
259
Preserve Custom Configurations for PLC

The Installer does not preserve the custom configuration entries done for PLC and you may lose the customized configurations after an upgrade. This file is overwritten on upgrade. To preserve custom configurations for PLC 1. Use the CCPro versions link to access old versions of the configuration file. TeamSite backing store maintains the versions of the configuration file. 2. Save the last two versions of the configuration file. 3. Compare these versions and identify the changes you have made to the base version. 4. After identifying the changes, re-apply them in the current version of the file. 5. Submit the updated file.
Adjust the Java Virtual Machine (JVM) Stack Size

You may see the following error in server.log of ApplicationContainer for TeamSite:
java.lang.OutOfMemoryError: unable to create new native thread
If you see this error, the default JVM stack size may be set too high. To reduce the size of the JVM stack size 1. Access the JVM stack size setting through one of the following methods, depending on your OS.
On Windows: Run regedit and select the following registry key. HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/ iwjbossd/Parameters/JVM Option Number [15]
In the key, change -Xss2m to -Diw.Xss=2m.

On Unix: Edit /Interwoven/ApplicationContainer/bin/
iw_jboss_run.conf and remove the -Xss2m setting from the JAVA_OPTS string. 2. Restart JBoss with the following command.
ts-home/bin/iwreset -ui
260
ReportCenter
ReportCenter
Some of the scenarios that you may encounter after the ReportCenter installation and how to troubleshoot them are mentioned in the following sections.
Access the ReportCenter User Interface

If you face any issues in accessing the ReportCenter user interface, restart the JBoss service.
Generate Reports
At times when you generate a report, the reports may be empty. Ensure that the following tasks are completed.
If you have installed ReportCenter on a Solaris platform over Sparc architecture, then set the ts.server.endian property to big in the cssdk.cfg file. Database is configured properly. Follow the next procedure to ensure that the database configuration file has the correct values.
To ensure that the database configuration file has the correct values 1. Navigate to /ApplicationContainer/server/default/deploy and open the js-jboss-ds.xml in a text or XML editor. This file contains the JNDI data source bindings with the following JNDI names:
jdbc/jasperserver-pro jdbc/odreportdb jdbc/tsreportdb
2. Verify whether the placeholders have been replaced by the correct data source connectivity information for each of the JNDI bound data sources. If not, replace them with the correct values. Usually, the ReportCenter installer configures these entries. The sample configuration file is documented in Sample js-jboss-ds.xml File on page 262. a. The first section of the file with the JNDI data source name, jdbc/ jasperserver-pro contains the data source information that was entered at the time of ReportCenter installation. If there are any errors, make the changes as needed by replacing the placeholders shown below with the correct values:
<local-tx-datasource> <jndi-name>jdbc/jasperserver-pro</jndi-name>
261
<connection-url>__ADV__CONNECTIONURL__</ connection-url> <driver-class>__ADV__DBDRIVER__</driver-class> <user-name>__ADV__USERNAME__</user-name> <password>__ADV__PASSWORD__</password> <min-pool-size>5</min-pool-size> <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> </local-tx-datasource>
b. The second and third sections of the file with the JNDI data source names, jdbc/odreportdb and jdbc/tsreportdb contain the database information pertaining to the databases that store OpenDeploy and TeamSite related events, respectively. The ReportCenter installer updates these sections by reading the details from the Autonomy Registry. Ensure that the following placeholders are replaced with the correct database credentials. For OpenDeploy:
<local-tx-datasource> <jndi-name>jdbc/odreportdb</jndi-name> <connection-url>__OD__CONNECTIONURL__</ connection-url> <driver-class>__OD__DBDRIVER__</driver-class> <user-name>__OD__USERNAME__</user-name> <password>__OD__PASSWORD__</password> <min-pool-size>5</min-pool-size> <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> </local-tx-datasource> For TeamSite: <local-tx-datasource> <jndi-name>jdbc/tsreportdb</jndi-name> <connection-url>__TSREPORTS__CONNECTIONURL__</ connection-url> <driver-class>__TSREPORTS__DBDRIVER__</driver-class> <user-name>__TSREPORTS__USERNAME__</user-name> <password>__TSREPORTS__PASSWORD__</password> <min-pool-size>5</min-pool-size> <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> </local-tx-datasource>
Sample js-jboss-ds.xml File

<?xml version="1.0" encoding="UTF-8"?> <datasources> <local-tx-datasource>
262
ReportCenter
<jndi-name>jdbc/jasperserver-pro</jndi-name> <connection-url>jdbc:sqlserver:// testServer:1433;databaseName=dbRep;SelectMethod=cursor</ connection-url> <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</ driver-class> <user-name>testUser</user-name> <password>testPass</password> <min-pool-size>5</min-pool-size> <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> </local-tx-datasource> <local-tx-datasource> <jndi-name>jdbc/odreportdb</jndi-name> <connection-url>jdbc:sqlserver:// testServer:1433;databaseName=dbOD</connection-url> <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</ driver-class> <user-name>testUser</user-name> <password>testPass</password> <min-pool-size>5</min-pool-size> <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> </local-tx-datasource> <local-tx-datasource> <jndi-name>jdbc/tsreportdb</jndi-name> <connection-url>jdbc:sqlserver:// testServer:1433;databaseName=dbTS</connection-url> <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</ driver-class> <user-name>testUser</user-name> <password>testPass</password> <min-pool-size>5</min-pool-size> <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> </local-tx-datasource> </datasources>
263
264
Index
Symbols
.shtml files 132 authoring server screen 214 branches creating 157 restrictions on names 158 setting locking model 158
A
access restricting 239 TeamSite 143 activating backing stores 153 administrative tasks 238 ampersand (&) 100 Apache configuring 129 configuring MIME types 134 authoring host name 216 authoring server installation prerequisites 42 installing 212 post-installation tasks 222 authoring server screen Base Directory for Installation 214 component selection 213 Installation Summary 222 Installation Type 213
C
CGI tasks 167 configuring in ContentCenter GUIs 167 character encoding 42 Client Certificate 243 clients Microsoft network 143 NFS 145 TeamSite 143 CLTs iwreset 153 iwstoreadm 153 comments publish 161 submit individual file 160 keywords 160 submit operation 160 common services screen 212 components 26 configuring CGI programs 132 FieldMapping.xml 203 IIS 129 index manager 193 iPlant Web server 129 iw-mount alias 131 MIME types, Apache 134 OpenDeploy 177
265
B
backing store activating 153 comments 152 encoding of names 151 location 44 moving 154 multibyte characters 151 Base Directory for Installation
Index
OpenDeploy after installing SitePublisher 78 search manager 193 TeamSite Report Server 171 Web servers 129 connecting to TeamSite by FTP 34 content deployment 232 controlling comparison 234 faceted search 234 creating branches 157 workareas 158 customizing deployment 234
text editors 152 encryption 101 execution permissions 103 extended attributes for TeamSite Report Server 176 extendedAttributeFields 204
F
faceted search, controlling 234 fan-out deployment 235 FieldMapping.xml configuring 203 file 207 location 203 FieldMapping.xsd 204 fieldName 204 entries 205 fieldSpecification 204 fieldStorage 204 entries 205 fieldType 204 file system interface and FTP 143 network connection 34 using 34 files FieldMapping.xml 203, 207 FieldMapping.xsd 204 parsing .shtml 132 search.private.properties 194 search.properties 193 submitting to the staging area 160 tsreport.xml 171 format for path names 42 formatString 204 FTP and the file system interface 143 clients, using 145 connecting to the TeamSite server 34
D
datacapture.cfg 204 delete_jobs_on_completion 177 delimiter, ampersand (&) 100 dependency migration tool 123 deploying content 232 deployment content 232 customizing 234 fan-out 235 launcher 233 metadata 232 phase 1 233 phase 2 233 phase 3 233 phase 4 233 process 232 destination area 219
E
editions initial 158 new 161 publishing 161 encoding of backing store names 151 of contents of iw.cfg 151
G
globalFields 204
266
H
hardware requirements 41 hibernate 174 HTTPS requests, redirecting 139 HTTPS transport 240
I
IBM HTTP Server 129 IDOL server configuration 201 relocate Search Collection folder 202 IIS, configuring 129 index manager, configuring 193 initial edition 158 installation common services screen 212 pre-installation tasks 40 prerequisites 41 authoring server 42 Targeting 82 terms 41 Installation Summary authoring server screen 222 installation tasks 82 installing authoring server 212 LSCS 211 required access for 49 required information 47 TeamSite 48, 49, 95, 109 internationalization, text editor encoding 151 iPlanet Web server configuring 129 iw.cfg 176 activating change to 153 delete_jobs_on_completion 177 encoding of 151 workflow 177 iw.index.binaryextension parameter 195 iw.index.events.enable parameter 195 iw.index.events.listen.attempts parameter 195 iw.index.events.listen.wait parameter 196 iw.index.iwserver.connect.attempts parameter 196
iw.index.iwserver.connect.wait parameter 196 iw.index.markpartial.duration parameter 195 iw.index.maxfilesizetoindex parameter 195 iw.index.maxidxsize 195 iw.index.optimalWaitMins parameter 196 iw.index.scipool.max parameter 195 iw.index.scipool.warm parameter 195 iw.index.server.host parameter 200 iw.index.server.port parameter 194 iw.index.wamodifications.branchcreation.default parameter 196 iw.index.wamodifications.enable parameter 196 iw.index.wamodifications.frequency parameter 196 iw.search.cache.processed.size parameter 200 iw.search.cache.raw.entries.capacity parameter 200 iw.search.cache.raw.entries.grace parameter 200 iw.search.query.defaultQueryLocale parameter 199 iw.search.query.maxOpenQueriesPerUser parameter 199 iw.search.scipool.max parameter 200 iw.search.scipool.max parameter, recommended value 200 iw.search.scipool.warm parameter 200 iw.search.server.port parameter 199 iw.search.server.threadpool.keepalivetime parameter 199 iw.search.server.threadpool.maxthreads parameter 199 recommended value 200 iw.search.server.threadpool.warmthreads parameter 199 iw-home 44 about 44 iw-mount alias 131 iwreset 153 iwservletd 170 iwsessionkeygen 170 iwstoreadm 153 iwui user 170 iwwebd 170
267
Index
J
java.naming.provider.url 195 JavaScript 141
K
key-value pairs 99
non-root support 122 role information 125 user information 125 user/group ID 126 MIME types, configuring 134 moving backing stores 154 multibyte characters in backing store names 151
L
loading content 149 local domains 34 Local File Manager about 143 installing 143 locale, search manager 194 location FieldMapping.xml 203 FieldMapping.xsd 204 search.private.properties 194 search.properties 193 locking model 158 log 174 configuration 201 log4j.appender.mainLogger.MaxBackupIndex parameter 201 log4j.appender.mainLogger.MaxFileSize parameter 201 log4j.logger.com.interwoven parameter 201 logging 201 LSCS installing 211 sample applications 225
N
NetBEUI 144 network drive 143 network file system 34 NFS and the file system interface 34 clients 143, 145 server mount point 131 nobody user 170 non-English character search.properties 194
O
OpenDeploy configuring 177 server 242 Web services 240 overriding deployment default values 234
P
parameter iw.index.binaryextension 195 iw.index.events.enable 195 iw.index.events.listen.attempts 195 iw.index.events.listen.wait 196 iw.index.iwserver.connect.attempts 196 iw.index.iwserver.connect.wait 196 iw.index.markpartial.duration 195 iw.index.maxfilesizetoindex 195 iw.index.optimalWaitMins 196 iw.index.scipool.max 195 iw.index.scipool.warm 195 iw.index.server.host 200 iw.index.server.port 194
M
metadata deployment 232 migration access to branches 126 checklist 120 configuration files 128 customizations 127 dependency 123
268
iw.index.wamodifications.branchcreation.default 196 iw.index.wamodifications.enable 196 iw.index.wamodifications.frequency 196 iw.search.cache.processed.size 200 iw.search.cache.raw.entries.capacity 200 iw.search.cache.raw.entries.grace 200 iw.search.query.defaultQueryLocale 199 iw.search.query.maxOpenQueriesPerUser 199 iw.search.scipool.max 200 iw.search.scipool.max parameter 200 iw.search.scipool.warm 200 iw.search.server.port 199 iw.search.server.threadpool.keepalivetime 199 iw.search.server.threadpool.maxthreads 199 recommended value 200 iw.search.server.threadpool.warmthreads 199 java.naming.provider.url 195 log4j.appender.mainLogger.MaxBackupIndex 201 log4j.appender.mainLogger.MaxFileSize 201 log4j.logger.com.interwoven 201 parsing .shtml files 132 password encryption 101 path names, format 42 pcnfsd 34 permissions 103 phase 1 deployment 233 phase 2 deployment 233 phase 3 deployment 233 phase 4 deployment 233 port Web server 130 post-installation tasks authoring server 222 prerequisites for installation 41 product 26 program files default location 44 project repository, reinitializing 238 properties files 99 publishing editions about 161
adding comments 161 first edition 161 through the command line 161 through the TeamSite GUI 161
R
redirecting HTTPS requests 139 redirector module introduced 133 reinitializing project repository 238 requirements hardware 41 software 41 response files 99 restricting access 239 root access gaining 49 installing TeamSite 49 runtime host name 216 runtime port 216
S
Samba connecting to the file system interface 34, 143 sample applications 225 screen common services 212 Search configuring 193 IDOL server configuration 201 locale 194 logging configuration 201 upgrading 223 Search Collection folder, relocate 202 search manager configuring 193 search.private.properties 194 search.properties generic configuration 194 IDOL server configuration 201 index server configuration 194
269
Index
location 193 logging configuration 201 non-English character 194 search server configuration 199 servers authoring installation prerequisites 42 installation summary 222 iPlanet Web configuring 129 OpenDeploy 242 Sun ONE 140 Web aliases 44 configuring 129 port number 130 stopping and starting 139 Sun ONE 140 supported 129 server-side includes 132 services OpenDeploy Web 240 shared volume 34, 143 silent installation input files 99 SitePublisher configuring OpenDeploy 78 software requirements 41 SSIs, enabling 133 SSL connection 244 staging area 158 StandardFields 204 submit filtering 160 submit task, ownership 169 submitting, files to staging 160 Sun ONE Web server aliases 140 supported Web servers 129
CGI 167 ownership 169 pre-installation 40 TeamSite accessing 143 through the ContentCenter 83 through the file system 143 through the GUI 142 troubleshooting 144 clients 141, 143 installing 49, 95, 109 mounting 143 TeamSite Report Server configuring 171 CSSDK 172 DAO 175 database 172 extended attributes 176 hibernate 174 job variable 176 user information 173 templates 99, 204 templateType 204 templatingField 204 templatingFields 204 text editor encodings 152 tsreport.xml 171
U
upgrading 223 users iwui 170 nobody 170
V
VisualPreview for SSIs 133 required plug-ins 137
T
Targeting 82 tasks administrative 238
W
Web servers
270
aliases 44 configuring 129 port number 130 stopping and starting 139 Sun ONE 140 supported 129 window.opener Javascript object 168 Windows networking 34 workareas creating 158 naming conventions 158 private 159 shared 159 submitting to the staging area 160 workflow query events 177
X
xpath 204
Z
zone name 205
271
Index
272

WS Authoring 7.3 Install Rev4 en

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

WS Authoring 7.3 Install Rev4 en

Încărcat de

Drepturi de autor:

Formate disponibile

Web Solutions Authoring Components Installation Guide

Trademarks and Copyrights

Notice to Government End Users

Chapter 1 Introduction ................................................................................................................................. 25

Web Solutions Authoring Components Installation Guide

Chapter 2 Installation Prerequisites ....................................................................................................... 31

Chapter 3 Install TeamSite ......................................................................................................................... 43

Web Solutions Authoring Components Installation Guide

Chapter 4 Silent Installation Options ...................................................................................................... 99

Chapter 5 Upgrade and Migrate TeamSite .......................................................................................... 107

Web Solutions Authoring Components Installation Guide

Chapter 6 Configure TeamSite ............................................................................................................... 129

Web Solutions Authoring Components Installation Guide

Chapter 7 Configure ReportCenter ........................................................................................................ 171

Chapter 8 Install Search ............................................................................................................................ 179

Web Solutions Authoring Components Installation Guide

Uninstall Search ....................................................................................................................... 192

Chapter 9 Configure Search .................................................................................................................... 193

Chapter 10 Install LiveSite Content Services Authoring ................................................................ 211

Chapter 11 Configure LiveSite Content Services Authoring......................................................... 225

Web Solutions Authoring Components Installation Guide

Chapter 12 Troubleshooting....................................................................................................................... 247

Web Solutions Authoring Components Installation Guide

Web Solutions Authoring Components Installation Guide

Web Solutions Authoring Components Installation Guide

Web Solutions Authoring Components Installation Guide

Web Solutions Authoring Components Installation Guide

Web Solutions Authoring Components Installation Guide

Web Solutions Authoring Components Installation Guide

Web Solutions Authoring Components Installation Guide

About This Document

The topics in this section include:

Web Solutions Authoring Components Installation Guide

About This Document

documents related to IDOL Server, Virage Videologger, or KeyView Filter.

could retrieve documents related to the Content or Category component in IDOL.

Web Solutions Authoring Components Installation Guide

Web Solutions Authoring Components Installation Guide

About This Document

Web Solutions Authoring Components Installation Guide

Command-line Syntax Conventions

Web Solutions Authoring Components Installation Guide

About This Document

CAUTION A caution indicates an action can result in the loss of data.

IMPORTANT An important note provides information that is essential to completing a task.

Autonomy Customer Support

Web Solutions Authoring Components Installation Guide

To contact Autonomy Customer Support by e-mail or phone, go to http://www.autonomy.com/content/Services/Support/index.en.html

North and South America

Web Solutions Authoring Components Installation Guide

About This Document

Web Solutions Authoring Components Installation Guide

The Autonomy Installer

Web Solutions Authoring Components Installation Guide

Components used by the Installer

Web Solutions Authoring Components Installation Guide

Components used by the Installer

Web Content Authoring

Web Content Management

Web Solutions Authoring Components Installation Guide

Web Content Runtime

License the Products

Web Solutions Configuration Overview