Upgrade Technical Supplement

6.7.
1 Upgrade Supplement
Package
6.7.1 Upgrade Technical Supplement
Interwoven, Inc.
th
803 11 Avenue
Sunnyvale, CA 94089
Tel: 408-774-2000
Fax: 408-774-2002
www.interwoven.com Version 1.0
Interwoven Services
September 12, 2007
© Copyright 2007 Interwoven, Inc. All rights reserved. ANY RESOLUTION, ANYWHERE, CONFIRMSITE, CONTROLHUB,
DESKSITE, FILESITE, IMANAGE, IMANAGE & DESIGN, INTERWOVEN, INTERWOVEN & DESIGN, INTRAGO, LIVESITE,
MEDIABIN, METACODE, METAFINDER, METASOURCE, METATAGGER, OFFSITE, OPENDEPLOY, PRIMERA,
SMARTCONTEXT, SMARTPUBLISHER, STING, STING TECHNOLOGY & DESIGN, TEAMCATALOG, TEAMSITE,
TEAMTURBO, TEAMXML, TEAMXPRESS, WORKDOCS, WORKPORTAL, WORKROUTE, WORKSITE, WORKTEAM, the
respective taglines, logos and service marks are trademarks of Interwoven, Inc., which may be registered in certain jurisdictions.
All other trademarks are owned by their respective owners.
9/13/2007
Interwoven Confidential
Table of Contents
Introduction..................................................................................................................................... 4
Product Documentation .............................................................................................................. 4
Features and Effect on Upgrade...................................................................................................... 4
Flexible roles support in TeamSite 6.7 ....................................................................................... 4
TeamSite server running as non-root user on Solaris and Linux................................................ 6
Solaris 10 support in TeamSite 6.7 (Solaris 8 is no longer supported)...................................... 6
Search (if your current TeamSite version is 6.1 and before) ...................................................... 6
Features that can be implemented post upgrade ............................................................................. 6
User and Group Management Enhancements............................................................................. 6
New Workflow modeler Client to Design Workflows. .............................................................. 6
New user impersonation scheme on windows in TeamSite 6.7.1............................................... 7
TinyMCE support in addition to Ektron VFE in TeamSite 6.7.1. .............................................. 7
Existing configuration and Effect on Upgrade to 6.7.1 .................................................................. 7
Start with Cleanup....................................................................................................................... 7
Planning your Upgrade ............................................................................................................... 7
Upgrade vs. Fresh Install ............................................................................................................ 8
Migrating your backing store...................................................................................................... 8
Upgrade Approach Considerations ............................................................................................. 8
Upgrade Paths ................................................................................................................................. 8
Upgrade from 6.7.0 to 6.7.1........................................................................................................ 9
Upgrade from 5.5.2 or before to 6.7.1 ........................................................................................ 9
Upgrade on Windows 2000, Windows 2003 .............................................................................. 9
Checklist ................................................................................................................................. 9
Upgrade on Windows 2000, Windows 2003 Diagram ......................................................... 10
Upgrade on Solaris 9................................................................................................................. 11
Checklist ............................................................................................................................... 11
Upgrade on Solaris 9 Diagram.............................................................................................. 12
Fresh Installation on Windows 2000, 2003 and manual copy of old backing store ................. 13
Checklist ............................................................................................................................... 13
Fresh Installation on Windows 2000, 2003 and manual copy of old backing store Diagram
............................................................................................................................................... 14
Fresh Installation on Solaris 9 or 10 and manual copy of old backing store ............................ 15
Checklist ............................................................................................................................... 15
Fresh Installation on Solaris 9 or 10 and manual copy of old backing store Diagram ......... 16
Fresh Installation on Linux Redhat AS4 and manual copy of old backing store ..................... 17
Checklist ............................................................................................................................... 17
Fresh Installation on Linux Redhat AS4 and manual copy of old backing store Diagram .. 18
Detailed Description of Upgrade/Fresh Installation Steps............................................................ 19
Non-root support and migrate_non_root .................................................................................. 19
Running iwusermigrate............................................................................................................. 19
Running iwaccessmigrate – Associating user with particular roles on each branch ................ 20
Running iwidmap – Resolving user/group ids.......................................................................... 22
Interwoven Services ___________________________________________________________________

Page 2 of 26
9/13/2007
Running migrate_customtk.ipl - Flexible Roles UI customization .......................................... 22

Configuration files .................................................................................................................... 22
Running iwmigrate.................................................................................................................... 25
References..................................................................................................................................... 26

Page 3 of 26
9/13/2007
Introduction
This document is intended to serve as a best practice guide for customers upgrading an existing
Interwoven installation to 6.7.1. The document will refer to support articles where necessary to
provide a detailed description of any given step in the upgrade. Interwoven’s goal as an
organization is to prepare you to go live with TeamSite 6.7.1.
It is strongly suggested that you read the product documentation before reading the upgrade
supplement. This will help you understand the supported platforms, new features of the
TeamSite 6.7.1 platform and the purpose of the upgrade steps. Please make sure that you are
installing TeamSite 6.7.1 to be followed by the latest patch or the latest service pack.
Product Documentation
Product Documentation 6.7.0 The TeamSite Administration Guide is a guide to
TeamSite Administration configuring and maintaining TeamSite. It is primarily
Guide intended for TeamSite Administrators and Master users, and
for web server administrators and system administrators.
Product documentation 6.7.0 The TeamSite Install Guide is a guide to installing TeamSite
TeamSite Installation Guide 6.7.X. It is intended primarily for TeamSite Administrators
who will perform the installation.
Product Documentation 6.7.0 TeamSite Command-Line Tools describes each TeamSite
TeamSite Command Line command-line tool (CLT) and command trigger, including
Tools syntax and usage examples. It is intended primarily for
TeamSite Administrators and Master users, and for web
server administrators and system administrators.
6.7.0 ContentCenter The TeamSite ContentCenter Professional User Guide is a
Professional User Guide guide to using the Professional interface of the TeamSite
product. It is primarily intended for advanced TeamSite
users.
6.7.0 ContentCenter Standard The TeamSite ContentCenter Standard User Guide is a guide
User Guide to using the Business User interface of the TeamSite product.
It is primarily intended for TeamSite authors.
Developers Guide The TeamSite FormAPI Developers Guide is a guide for
developing FormAPI for TeamSite forms. It is intended for
TeamSite developers.
FormsPublisher Developers The TeamSite FormsPublisher Developers Guide is a guide
Guide for developing TeamSite forms. It is intended for TeamSite
developers.
User Interface Customization The User Interface Customization Guide is a guide to
Guide customizing the TeamSite interface. It is intended for
TeamSite developers and administrators.
6.7.0 Workflow Developer The Workflow Developer Guide is a guide for building
Guide TeamSite workflows. It is intended for TeamSite developers

Page 4 of 26
9/13/2007
Product Documentation
and administrators.
Product Documentation 6.7.1 This document contains release notes for TeamSite® 6.7.1.
TeamSite Release Notes
Product Documentation The TeamSite Supplement describes TeamSite® features that

Supplement for TeamSite 6.7.1 are new or revised for this release. Information in this
document is intended for TeamSite end users, installers,
administrators, and customizers.
Workflow Modeler 1.0 This document provides an introduction to general workflow

models, the Interwoven Workflow Modeler functionality,
and TeamSite integration.
Features and Effect on Upgrade

The following are key new features in the TeamSite 6.7.1 platform. For more details please
review the 6.7.1 TeamSite Release Notes.
1. Flexible roles and delegated administration in TeamSite 6.7

2. User and Group management enhancements in TeamSite 6.7
3. Linux RedHat AS/ES4 platform support in TeamSite 6.7.1
4. Solaris 10 support in TeamSite 6.7 (Solaris 8 is no longer supported)
5. TeamSite server runs as non-root user on Solaris and Linux from TeamSite 6.7.1
6. New Workflow modeler toolkit to design workflows in addition to the current perl based
workflow templates (wft) in TeamSite 6.7.1
7. New user impersonation scheme on Windows in TeamSite 6.7.1
8. TinyMCE support in addition to Ektron VFE in TeamSite 6.7.1
9. For customers currently on TeamSite 6.1 and before, Search was added in TeamSite 6.5
The features below necessitate either additional migration steps during upgrade installation or
require a fresh installation followed by manual migration steps.
Flexible roles support in TeamSite 6.7

In 6.7.0, the TeamSite access model was enhanced to allow users the ability of different roles in
different branches rather than logging in with one global role. iwusermigrate,
iwaccessmigrate and migrate_customtk.pl command line tools are used to migrate to the
new model.

Page 5 of 26
9/13/2007
TeamSite server running as non-root user on Solaris and Linux

In 6.7.1, the TeamSite server process runs as a non-root user (iwts user). Previous versions of
the backing store and the iwhome installation directories were owned by root and the ownership
is changed using migrate_non_root script.
Solaris 10 support in TeamSite 6.7 (Solaris 8 is no longer supported)

If you are moving to TeamSite 6.7.1 on Solaris 10, the preferred process is to upgrade the OS to
Solaris 10 (or install Solaris 10 on new hardware) and do a fresh install of TeamSite 6.7.1. An
upgrade installation of TeamSite is not supported once the Solaris OS has been elevated to
version 10. Of course, if this is done on the same machine, you will want to back up the
TeamSite server content store and all configurations prior to beginning any work.
Search (if your current TeamSite version is 6.1 and before)

If you are installing Search for the first time, the early indexing phase puts undue stress on
iwserver process memory utilization. This can be controlled by running the iwmigrate
command line tool. Some migration steps are performed by the installer when doing an upgrade
installation and some steps need to be performed manually.
Features that can be implemented post upgrade

Additional features do not impact the upgrade and migration process and are available with the
new version of TeamSite. They can be considered after the upgrade is completed and the system
is in production. In this section, we will briefly explain the features and how they are
complimentary to existing functionality.
User and Group Management Enhancements.

Several enhancements to user and group management were done in TeamSite 6.7 platform. They
are automatically available with the upgrade and you can leverage them as you decide
appropriate.
New Workflow modeler Client to Design Workflows.

A Java based workflow modeler client has been introduced in TeamSite 6.7.1. This gives you a
new way of new designing workflows in addition to the existing perl based wft’s. All your
existing perl based wft’s will continue to work normally. If there is a need for designing new
workflows, it is recommended to use the new modeler. However, it does not preclude you to
write a new workflow using perl based wft’s if you so choose to. Please refer to the installation
package for documentation on the workflow modeler.
Workflow Modeler is installed separately from TeamSite, and must be integrated with TeamSite
following installation. A SOAP license is available to you for configuring the integration. For
information on the Workflow Modeler install please review this DevNet forum
http://devnet.interwoven.com/forums_vb/showthread.php?t=18319&forumid=11.

Page 6 of 26
9/13/2007
New user impersonation scheme on windows in TeamSite 6.7.1.

Workflow external task process on windows was owned by SYSTEM till TeamSite 6.7. Starting
in TeamSite 6.7.1, workflow external task processes are owned by the actual owner of the task.
This change is automatic when you upgrade to TeamSite 6.7.1 and there is no additional
migration step needed.
TinyMCE support in addition to Ektron VFE in TeamSite 6.7.1.

TinyMCE editor support is added in TeamSite 6.7.1 to format and fill datacapture forms in
FormsPublisher. However, Interwoven continues to support using Ektron VFE. All existing
DCTs and DCRs will work normally after the upgrade. When designing new DCTs, it is
recommended to use TinyMCE. However, it does not preclude you to continue using Ektron.
Existing configuration and Effect on Upgrade to 6.7.1

You may have customized code that will be affected by the Upgrade to 6.7.1. It is important to
understand your implementation and create a test plan to follow after the upgrade.
Start with Cleanup

An upgrade is a good time to clean up your implementation. You have been running TeamSite
in your organization for a while, but have you ever taken the time to clean up the files that you
are no longer using? We suggest you do the following:
Archive all old log files
Clean up the file versions of master.uid\
Remove excess editions
Identify a maintenance plan going forward for your TeamSite server, including backup
schedules and log rotation.
(https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=57603)
Planning your Upgrade

Revisit your content creation, approval, and other processes
Are they working?
Do they need to change?
Review templates
Are they being used?
Could the business users be empowered with additional functionality?
New hardware
Is it time for new hardware?
If on Solaris, are you on 9 or 10? Solaris 8 is not supported with TeamSite 6.7.1.
What new features are you interested in using?

Page 7 of 26
9/13/2007
Upgrade vs. Fresh Install

If you are planning to upgrade on the same server, you will be doing an upgrade. For supported
upgrade paths, please review the support article below:
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=57073
Please note that some upgrades will require a backing store migration.
In the following situations, it is necessary to do a fresh install rather than an upgrade.

Migrating from Solaris 9 to 10 = fresh install
Buying new hardware – Compatibility Matrix
Any platform change = new installation
Fresh install = backing store migration
Any Linux installation
Migrating your backing store

In the following situations, you will need to migrate your backing store:
You are doing a fresh install
If you are using search and need to cleanup and re-index
You are moving from a version of TeamSite earlier than TeamSite 6.5 SP2
This article explains the benefits of performing a migration on your backing store:
Upgrade Approach Considerations

Please consider the following while planning your upgrade:
Perform the upgrade on a development server first and test prior to performing the
upgrade on production
User and Group management enhancements
New Workflow modeler client to design workflows
TinyMCE support in addition to Ektron VFE in TeamSite 6.7.1
EventSubsystem: If you are not using DAS with OpenDeploy or TeamSite Reporting,
you should disable the EventSubsystem Reporting.
Upgrade Paths
The different upgrade paths are outlined in the table below and fully described in the following
sections.
Path Description
Upgrade from 6.7.0 to 6.7.1 You will be able to perform a straight upgrade.
Upgrade from 5.5.2 or before to 6.7.1 You are on a version that is no longer
supported, your upgrade might be complex. It
is suggested you call your consulting manager.

Page 8 of 26
9/13/2007
Path Description
Paths for Customers currently running TeamSite 6.5 SP3 or before
Upgrade on Windows 2000, Windows 2003 Applicable if your current TeamSite version is
6.5sp3 and before
Upgrade on Solaris 9 Applicable if your current TeamSite version is
6.5sp3 and before
Fresh installation on windows 2000, 2003 Applicable if backing store from current
and manual copy of old backing store TeamSite installation on windows 2000/2003
Fresh installation on Solaris 9 or 10 and Applicable if backing store from current
manual copy of old backing store TeamSite installation on Solaris 8, 9
Fresh installation on Linux Redhat AS 4 and Applicable if backing store from current
manual copy of old backing store TeamSite 6.1 Linux or TeamSite 6.1 AIX
installation or from current Solaris 8/Solaris
9/Solaris 10 TeamSite installations
Upgrade from 6.7.0 to 6.7.1

You will be able to perform a straight upgrade.
Upgrade from 5.5.2 or before to 6.7.1

You are on a version that is no longer supported and your upgrade might be complex. It is
suggested you call your consulting manager.
Upgrade on Windows 2000, Windows 2003

Checklist
Step # Description Complete
1 TeamSite installation
2 Map roles to new paradigm (using iwusermigrate)
3 Reboot server and verify if role mapping is correct
Verify all User IDs are present
4 Map user permissions to new paradigm (using iwaccessmigrate)
5 Map permissions for custom menu items (using
migrate_customtk.ipl)
6 Cleanup and re-index backing store if using search
Note: Review sections below for a detailed explanation of some of the steps with references to supporting articles

Page 9 of 26
9/13/2007
Upgrade on Windows 2000, Windows 2003 Diagram
TeamSite 6.5 sp3 and before on

Windows 2000/2003
TeamSite 671 installation
iwusermigrate
Server reboot and TeamSite

restarted
Verify if
tsusers.xml has
all TeamSite
users. See
Running
iwusermigrate Run iwmigrate if
section needed. See Running
iwmigrate section for
details
Iwaccessmigrate.
See section on
Running End
iwaccessmigrate
Migrate_customtk.ipl.
See Running
migrate_customtk.ipl
section for more
details

Page 10 of 26
9/13/2007
Upgrade on Solaris 9
Checklist
1 TeamSite installation
2 Map roles to new paradigm (using iwusermigrate)
3 TeamSite no longer runs as root (run migrate_non_root)
4 Reboot server and verify if role mapping is correct
6 Map permissions for custom menu items (using
7 Cleanup and re-index backing store if using search
See next page for diagram.

Page 11 of 26
9/13/2007
Upgrade on Solaris 9 Diagram
TeamSite 6.5 sp3 and before on TeamSite 6.5 sp3 and before on
Solaris 8 Solaris 9
Upgrade
Solaris 8 to
Solaris 9
TeamSite 671 installation
iwusermigrate Migrate_non_root
Server reboot and TeamSite

restarted
Verify if
tsusers.xml has
all TeamSite
users. See
Running
iwusermigrate Run iwmigrate if
section needed. See Running
details
Iwaccessmigrate.
See section on
Running End
iwaccessmigrate
See Running
section for more
details

Page 12 of 26
9/13/2007
Fresh Installation on Windows 2000, 2003 and manual copy of old backing store
Checklist
1 Freeze TeamSite server
2 Manual copy of backing store
3 6.7.1 TeamSite Installation
4 TeamSite reboots and Restarts
5 Stop TeamSite
6 Remap local OS user/group id info (using iwidmap)
7 Copy uid files or configure LDAP
8 Reboot server and Verify if role mapping is correct

10 Copy configuration files
11 Map permissions for Custom Menu items (using
12 Clean-up and Re-index backing store if using search (using
iwmigrate)

Page 13 of 26
9/13/2007
Fresh Installation on Windows 2000, 2003 and manual copy of old backing store Diagram

Page 14 of 26
9/13/2007
Fresh Installation on Solaris 9 or 10 and manual copy of old backing store

Checklist
3 Reset backing store ownership
6 Stop TeamSite
iwmigrate)

Page 15 of 26
9/13/2007
Fresh Installation on Solaris 9 or 10 and manual copy of old backing store Diagram
Copy uid files or

configure LDAP and run
iwusermigrate clt. See
Manual copy of backing store to
Running iwusermigrate
location “x” from previous versions
section for more details
of TeamSite (Ensure server is
stopped)
Reset backing store ownership to

iwts by running chown/chmod Start TeamSite
commands on location “x”. See
non-root support section
Iwaccessmigrate. See
section on Running
iwaccessmigrate
TeamSite 671 fresh installation on

Solaris 9/10 or Linux RedHat AS4
at backing store location “x”
Copy configuration files

from source system.
See configuration files
Installation reboots and restarts

TeamSite
See Running
section for more
details
Stop TeamSite
Run iwmigrate if
needed. See Running
more details
Run iwidmap on all stores for any

changes. See Running iwidmap
section for more details End

Page 16 of 26
9/13/2007
Fresh Installation on Linux Redhat AS4 and manual copy of old backing store
Checklist
3 Reset backing store ownership
6 Stop TeamSite
iwmigrate)

Page 17 of 26
9/13/2007
Fresh Installation on Linux Redhat AS4 and manual copy of old backing store Diagram
Copy uid files or

configure LDAP and run
iwusermigrate clt. See
Manual copy of backing store to
location “x” from previous versions
of TeamSite (Ensure server is
stopped)
Reset backing store ownership to

iwts by running chown/chmod Start TeamSite
commands on location “x”. See
non-root support section
Iwaccessmigrate. See
section on Running
iwaccessmigrate
TeamSite 671 fresh installation on

Solaris 9/10 or Linux RedHat AS4
at backing store location “x”
Copy configuration files

from source system.
See configuration files
Installation reboots and restarts

TeamSite
See Running
section for more
details
Stop TeamSite
Run iwmigrate if
needed. See Running
more details
Run iwidmap on all stores for any

changes. See Running iwidmap
section for more details End

Page 18 of 26
9/13/2007
Detailed Description of Upgrade/Fresh Installation Steps

Non-root support and migrate_non_root
In TS6.7.1, the iwserver process was changed to run as the iwts user, instead of root, on UNIX
platforms. This requires that all the files and directories in the backing store and some files under
iwhome are accessible by iwts. During the installation of TeamSite 6.7.1 (whether performing
upgrade or new install), the migrate_non_root script is invoked to walk the backing stores
found and change ownership and permissions on the backing store files to allow iwts user
access. (Note that this only affects backing store permissions; TeamSite users will not see files
owned by iwts) The script also changes ownership and permissions on the appropriate files in
iwhome.
After installation, if you do not have a 6.7.1 backing store, you MUST reset permissions and
ownership of the store or you will receive an error. Run the following UNIX commands to reset
permissions and ownership:
su - root
chown –R iwts bs_store_path
chmod –R +x bs_store_path
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 backing store may be a moderately lengthy process. It can take a short
number of hours to run over all the backing stores. Starting in TeamSite 6.7.1 SP1, you can
make use of a script iwhome/private/bin/walkArchive.pl which does the equivalent of
chown and chmod steps at a much faster pace.
Please refer to the following support article for additional information.

Prior to 6.7.0, user and role information were defined in either .uid files - i.e. author.uid,
editor.uid, admin.uid, and master.uid - or in attributes in LDAP, in the case where
TeamSite is configured to use the ldap_roles key in iw.cfg.
In 6.7, the 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
iwhome/conf/roles/tsldapuserscache.xml. In the latter case, 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 6.7 and has been moved to the
backing store. Each branch now contains a list of users and groups and the roles they have on

Page 19 of 26
9/13/2007
that branch. The only role information read from tsusers.xml or tsldapuserscache.xml is
master acess.
Iwusermigrate clt is used to process uid files (or LDAP) and produce tsusers.xml (or
tsldapuserscache.xml).
During an upgrade installation of 6.7.0 (or higher), 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,
please make sure to copy over uid files from your current installation to iwhome/conf/roles
directory. If your current TeamSite installation is configured to keep login role information in
LDAP, before running the iwusermigrate clt, please make sure to copy the [authentication]
section of iw.cfg from your current TeamSite installation to the new installation.
To verify whether iwusermigrate is run successfully, please run the command
$ iwhome/iw-perl/bin/iwperl –ne “/name=/” iwhome/conf/roles/tsusers.xml.

(Substitute tsldapuserscache.xml if LDAP is used)
The output of the command is a list of all TeamSite users. Please make sure that the list is
complete and no TeamSite users are missing.
Alternatively, when the server is started subsequently, you can run “iwuseradm list-users –
t” command to get the list of all TeamSite users in the system.
It is strongly recommended that you verify that the user list is complete before proceeding 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.
Running iwaccessmigrate – Associating user with particular roles on each branch

In 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).
Iwaccessmigrate is used to migrate to the new access model.
Iwaccessmigrate needs 5 pieces of information to successfully migrate to the new model.

Iwaccessmigrate can produce an incorrect migration if any of the information below is not
available or setup incorrectly. An incorrect migration can result in subsequent permission
problems.
1. List of all TeamSite users and their highest role. (from uid files or LDAP). Please keep in
mind that TeamSite roles in the old model are hierarchical. Master is the highest role,
followed by admin, editor and author in that order.

Page 20 of 26
9/13/2007
2. List of all groups a user is a member of. Iwaccessmigrate 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.
Iwaccessmigrate retrieves this information by making calls to the iwserver process.
4. The file-system permission of branch and workarea root directory of all branches and
workareas of all stores. Iwaccessmigrate retrives this information by making calls to
the iwserver process.
To ensure you have item 1 in the correct state, verify that iwusermigrate is run properly. See
“Running iwusermigrate” section for more details.
When the server is started with item 1 in the correct state, it will build 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 & 4 are in the correct state, verify that

• the backing store has been copied over properly
• iwidmap changes have been made, if needed (See “Running iwidmap” section)
• all stores are activated. If a store is inactive, iwaccessmigrate will exit 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.
• If the upgrade path you have chosen warrants the iwmigrate step to be run, please follow
the sequence described in the flow charts and perform the iwmigrate step *after* the
iwaccessmigrate step. (See “Running iwmigrate” section, also)
Once you have verified that all of the items above are in order, you can run the
iwaccessmigrate clt. When running the clt, it is strongly recommended that you first run it
with the –m option. This option will only create a manifest file,
iwhome/local/logs/accessresults.xml, and not apply the changes yet. You should consult
the manifest file and ensure that users are assigned correct roles to branches they are currently
using. Once you have verified that the accessresults.xml is correct, you can simply feed the
manifest file back to the iwaccessmigrate clt and apply the changes this time. You should use
–f <manifest-file> option for this.
In the event that you still needed to re-run iwaccessmigrate, the following support article
guides you with the re-run process.

Page 21 of 26
9/13/2007
Running iwidmap – Resolving user/group ids

If you are doing a fresh installation and copying the backing store over to the target system, you
might have the need to remap some local OS user/group id information. Please use the iwidmap
clt to perform the remapping. The link below gives access to a number of support articles
describing its usage.
https://support.interwoven.com/search/bnsearchmod.asp?cmd=search&charset=iso-8859-
1&ht=0&qc=&rq=0&la=en&qm=0&st=1&nh=10&rq=0&oq=&qp=&qs=&pw=100%25&ql=&s
i=1&qm=0&rf=0&lk=1&ws=0&col=rn&col=gen&col=technote&col=techdoc&col=tnotesin&c
ol=tdocsint&qt=iwidmap
Running migrate_customtk.ipl - Flexible Roles UI customization

In 6.5 and before, it was possible to restrict custom UI links (menu items and tabs) and
operations that invoke non-Interwoven functionality based on the user’s login role. This
restriction was specified by entering the operationIDs corresponding to the custom links in the
roles_custom.xml in the custom toolkit. In 6.7, 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
operationIDs in userops_custom.xml, not roles_custom.xml.
The migrate_customtk.ipl clt is used to populate the userops_custom.xml, reading it from

roles_custom.xml. Run the command <iwhome>/install/migrate_customtk.ipl to receive
the desired results.
Please note that for backward compatibility, TeamSite 6.7 continues to support the old method of
specifying role restrictions for custom menu items and tabs, but only for the predefined roles of
Author, Editor, Administrator, and Master. This allows customers to defer
migrating already defined custom menu items and tabs to the new permission scheme as
long as they are working with just the roles as defined out-of-the-box.
Please refer to the UI customization guide and the TeamSite 6.7.1 supplement guide Appendix B
(Migrating existing customization) for more details.
Configuration files
Changes in configuration and customization files will need to be brought over manually 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 will differ 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.

Page 22 of 26
9/13/2007
Below is a partial list of such files on a UNIX platform:
Configuration File Function

Specifies most of the settings of the
/etc/iw.cfg TeamSite server.
/etc/defaultiwhome Describes the location of the TeamSite
application software. The default location
is /usr/iw-home.
/etc/defaultiwstore Describes the location of the TeamSite
Content Store directory. The default
location is /usr/iw-store.
/etc/defaultiwmount Describes the location of the TeamSite
virtual mount point. The default location
is /iwmnt.
/etc/defaultiwlog Describes the location of the
iwserver.log file. The default location
is /var/adm/iwserver.log.
/etc/defaultiwelog Describes the location of the
iwevents.log file. The default location
is /var/adm/iwevents.log.
/etc/defaultiwtrace Describes the location of the
iwtrace.log file. The default location is
/var/adm/iwtrace.log.
iw-home/iw-samba/lib/iw.smb.conf Contains Samba configuration.
iw-home/local/config/submit.cfg Specifies all file permissions that are
automatically changed at submit time.
iw-home/local/config/autoprivate.cfg Specifies what types of files are
automatically marked private.
iw-home/local/config/file_encoding.cfg Contains rules that determine the
character encoding of the contents of
files that do not specify their encoding.
See Specifying Content Encoding for
information about creating these rules.
iw-home/local/config/templating.cfg Specifies the forms that are used in which
TeamSite areas and how the forms map
to presentation templates as well as
setting form display options.
iw-home/conf/roles/tsusers.xml Contains information on all TeamSite
users.
iw- Contains TeamSite users from LDAP
home/conf/roles/tsldapuserscache.xml files.

Page 23 of 26
9/13/2007
Configuration File Function

iw-home/conf/roles/roles.xml Contains information on operations
performed by each role, as set through
the Edit Roles screen.
iw-home/conf/tsgroups.xml Contains information on TeamSite
groups.
iw-home/local/config/transform.cfg Configures Content Transformation
Services.
iwsearch-home/etc/search.properties Configures the index server and search
server.
iwsearch-home/etc/branches.cfg Lists the branches to be indexed by the
index server.
iwsearch-home/etc/FieldMapping.xml Defines extended attributes and
templating attributes to be indexed.
iw-home/tsreport/conf/tsreport.xml Configures the EAs to be used by
TeamSite ReportCenter.
iw-home/eventsusbystem/conf/jmsconfignew.xml Configures the Event Subsystem.
iw-home/etc/iwutild.cfg Configures commands for the utility
service.
iw-home/local/config/datacapture.cfg Defines rule sets for capturing metadata
or forms.
iw-home/local/config/metadata- Provides information on mapping vpaths
rules.cfg to data capture rules.
iw-home/conf/roles/author.uid Specifies users who are in the author role
in TS6.5 and earlier.
iw-home/conf/roles/editor.uid Specifies users who are in the editor role
iw-home/conf/roles/admin.uid Specifies users who are in the admin role
iw-home/conf/roles/master.uid Specifies users who are in the master role
iw-home/local/entities Specifies user preferences. Note that the
host name is in some of the path
components in the entities files, so that
this information may need to be reset
when migrating to machines with
different names.
iw-home/cssdk/cssdk.cfg Specifies settings for Content Services.

Page 24 of 26
9/13/2007
Running iwmigrate
In TS6.5.0, the search facility was introduced. In some cases, for installations with pre-existing
backing stores from TS6.1 or earlier, the initial indexing phase of search would put undue stress
on the TeamSite server’s memory utilization. If these backing stores contain editions with large
directories, the server would run out of memory during indexing (at around 2GB on Solaris and
1.5GB on Windows) and crash.
Luckily, TS6.5.0 also introduced a more compact representation of directory metadata in the
backing store. This compact format consumes much less process memory, so search indexing of
6.5 stores do not cause the server to run out of memory and crash.
If your pre-6.5 backing store contains large directories then it may have to be converted using the
iwmigrate clt to the more compact representation before search can be enabled safely. To
determine whether your backing store has large directories, you can use a command line script
called chkfatdir.ipl. Please refer to the following support article for the script.
If the answer comes back yes, then please run iwmigrate. Please refer to the following support
article for proper usage of iwmigrate.
Please keep in mind that the iwmigrate clt only migrates editions. If you need to migrate the
workareas also, you will have to recreate the workareas on the target store and manually copy the
workarea content over using the file-system interface. Please ensure that you are using the
“preserve permission” option of the copy command. For example, if you use the UNIX cp
command, specify the “-p” option.
Running iwmigrate can be a lengthy process, potentially taking many hours, so plan
accordingly.
Below are additional support articles that can be useful. You can also search for ‘iwmigrate’ in
the support site for additional articles.

Page 25 of 26
9/13/2007
References
Below is a list of additional support articles that you can use as collateral in your upgrade
process.

Page 26 of 26

Upgrade Technical Supplement

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Upgrade Technical Supplement

Загружено:

Авторское право:

Доступные форматы

6.7.

6.7.1 Upgrade Technical Supplement

Interwoven Services ___________________________________________________________________

Running migrate_customtk.ipl - Flexible Roles UI customization .......................................... 22

Interwoven Services ___________________________________________________________________

Interwoven Services ___________________________________________________________________

Product Documentation The TeamSite Supplement describes TeamSite® features that

Workflow Modeler 1.0 This document provides an introduction to general workflow

Features and Effect on Upgrade

1. Flexible roles and delegated administration in TeamSite 6.7

Flexible roles support in TeamSite 6.7

Interwoven Services ___________________________________________________________________

TeamSite server running as non-root user on Solaris and Linux

Solaris 10 support in TeamSite 6.7 (Solaris 8 is no longer supported)

Search (if your current TeamSite version is 6.1 and before)

Features that can be implemented post upgrade

User and Group Management Enhancements.

New Workflow modeler Client to Design Workflows.

Interwoven Services ___________________________________________________________________

New user impersonation scheme on windows in TeamSite 6.7.1.

TinyMCE support in addition to Ektron VFE in TeamSite 6.7.1.

Existing configuration and Effect on Upgrade to 6.7.1

Start with Cleanup

Planning your Upgrade

Interwoven Services ___________________________________________________________________

Upgrade vs. Fresh Install

In the following situations, it is necessary to do a fresh install rather than an upgrade.

Migrating your backing store

Upgrade Approach Considerations

Interwoven Services ___________________________________________________________________

Upgrade from 6.7.0 to 6.7.1

Upgrade from 5.5.2 or before to 6.7.1

Upgrade on Windows 2000, Windows 2003

Interwoven Services ___________________________________________________________________

Upgrade on Windows 2000, Windows 2003 Diagram

TeamSite 6.5 sp3 and before on

TeamSite 671 installation

Server reboot and TeamSite

Interwoven Services ___________________________________________________________________

See next page for diagram.

Interwoven Services ___________________________________________________________________

Upgrade on Solaris 9 Diagram

TeamSite 671 installation

Server reboot and TeamSite

Interwoven Services ___________________________________________________________________

9 Map user permissions to new paradigm (using iwaccessmigrate)

See next page for diagram.

Interwoven Services ___________________________________________________________________

Interwoven Services ___________________________________________________________________

Fresh Installation on Solaris 9 or 10 and manual copy of old backing store

See next page for diagram.

Interwoven Services ___________________________________________________________________

Copy uid files or

Reset backing store ownership to

TeamSite 671 fresh installation on

Copy configuration files

Installation reboots and restarts

Run iwidmap on all stores for any

Interwoven Services ___________________________________________________________________

See next page for diagram.

Interwoven Services ___________________________________________________________________

Copy uid files or

Reset backing store ownership to