16 October 2008

TeamSite Skill Set

To learn the skills of TeamSite CMS, knowledge of with experience in usingTeamSite must be obtained. These knowledges are categories
and rated into four skill levels below. So for example, basic low skill levels for beginners will require basic fundamental knowledge of TeamSite. The higher the skill levels, the more tecnhnical knowledge of TeamSite is required to understand.

The skill levels are as follows:

Level 0: The Developer has no knowledge of or experience in the skill/knowledge area whatsoever.

Level 1: The Developer has a conceptual knowledge of the skill/knowledge area and has some limited commercial experience or may have experimented with the related concepts and/or supporting technologies in a non-commercial sense. The developer cannot apply this skill/knowledge area without direct supervision.

Level 2: The Developer is proficient in the skill/knowledge area with recent commercial experience in its application, can apply the skill/knowledge without direct supervision, but has insufficient experience/knowledge
to provide direction to others in the given area.

Level 3: The Developer can be considered an expert in the skill/knowledge area with considerable recent commercial experience in its application, with experience providing mentoring/guidance to others. The Developer has a detailed and broad understanding of the skill/knowledge area.

Note that each level described above subsumes all levels below it. Thus, in order for a TeamSite Developer to rate at Level 3, he or she must meet the criteria for Levels 1, 2 and 3.

The following area of TeamSite knowledge a TeamSite Developer need to obtain are broken down into each levels below:

Level 0

Introduction to Content Management System (CMS)
  • Can describe the definition of TeamSite
  • Can describe the features of TeamSite
  • Can describe the definition of CMS
  • Can describe the purpose of CMS
  • Can describe the content development life cycle
  • Cam describe the definition of an asset

Introduction to TeamSite Concept
  • Can define TeamSite server architecture
  • Can define TeamSite terminology like for example: i)
    Content stores ii) Branches ii)Workareas iv) Edition and Versionin v)Can describe the definition and what are the roles in TeamSite vi)Metadata vii)Can log in to a TeamSite server
  • Can describe and demonstrate and use the features in each version of ContentCenter User Interface

Level 1

Editing files

  • Can do simple and advance search for assets
  • Can describe and use TeamSite VisualPrevew tool
  • Can describe and use Local File Manager to edit files
  • Can describe and perform basic file operations like copy, rename, delete, create, move/rename, import/export and modifying properties of a file
  • Can view and set metadata
  • Can describe and demonstrate checking in/out a file and able to perform merges

Introduction to Workflows

Can describe the workflow terminology use in TeamSite, like for example understand the following:

  • Workflow
  • Job specification
  • Workflow Moder
  • Workflow template
  • Task
  • Activation
  • Transition
  • Links
  • Understand the difference between serial and parallel task
  • Workflow events

Introduction to Forms Publisher

Can describe the forms publisher terminology use in TeamSite, like for example understand the following:

  • Data Capture Templates (DCTs) / Data Capture Forms
  • Data Content Records (DCRs)
  • Presentation Template (PTs)

Level 2

Workflow Development

  • Can describe and demonstrate how to configure and set up out of the box workflows templates and workflow models
  • Can describe and demonstrate how to design, implement and deploy a workflow using the Workflow Modeler Tool
  • Can describe and demonstrate how to design, implement and deploy a customise workflow template using XML and Perl script

Form Publisher Development

  • Can describe and demonstrate how to develop Data Catpure Forms
  • Can describe and demonstrate how to develop Presentation Templates
  • Can describe and demonstrate how to use APIs and Command Line with Data Capture Forms


  • Can describe and demonstrate how to configure Open Deploy tool to deploy files to production server

Level 3

Advanced Workflow and Form Publisher Development

  • Can describe and demonstrate executing external programs
  • Can describe and demonstrate creating custom data source
  • Can describe and demonstrate using external database with Data Catpure Forms

TeamSite Administration

  • Can describe and install or upgrade TeamSite CMS, TeamSite Search, MetaTagger and Open Deploy
  • Can describe and demonstrate the process of configuring and reindexing TeamSite Search
  • Can demonstrate the maintenance process of creating, deleting, updating users, groups and roles in TeamSite
  • Can describe and demonstrate the process of backing and restoring content store
  • Can describe and demonstrate diagnosing error message with log files
  • Can configure file virtualisation in TeamSite

29 April 2008

Configuring .NET ASPX File Virtualization for TeamSite

The following configurations are necessary to successfully virtualize content from aspx files on a TeamSite Server where the .NET Framework is also installed on the same server.


  • Add the ASPNET user to the "TeamSite Web Preview" Group.
  • Ensure that .NET framework version 2 is already installed in the same server box that runs TeamSite.

If you are using Windows 2003 the following must also be done (until Bug 57146 has been fixed):
  1. If IIS was installed before you installed TeamSite then you need to delete the default website. Rename the current default website (e.g. “default website bkup”) and click the “Stop” button for the backup default website to stop IIS from running. Then create a new one (also name it “Default Web Site”), using port 81, set path to c:\inetpub\wwwroot and configure it for anonymous access using the IIS IUSR_ user. Click the “Start” button on the new created default website.
  2. Go to Default Web Site properties->ASP.NET tab and check the the .NET version. If there are two version of the .NET framework in the selected drop down box, select version 2.0.xxxx
  3. Go to Default Web Site and Add the SSI ISAPI filter as follows
  4. Right click Default Web Site > Properties > ISAPI Filters > Add, give a filter name like "iwrewrite" and point to \lib\iwproxy_isapi.dll
  5. Within the IIS Management console, under “default website” create a new virtual directory called "iw-mount" which points to the Y:\ drive directory. Anonymous access to this directory should be the TSIMP_ user.
  6. For the root directory (iw-mount), click the “Configuration” button and check the configuration of the defined application to ensure that at least the extensions ".aspx" points to the version 2 .NET framework of aspnet_isapi.dll. Further extensions pointing to this are asax, ascx, ashx, asmx & axd.
  7. Check in the Web Service Extensions that Active Server Pages and ASP.NET are enabled.
  8. Do step A to C **
  9. Set full permission to everyone on the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files folder
  10. Restart IIS and run “iwreset –a”
  11. You should now be able to run a simple ASPX. (just take a simple HTML page and rename it .asp/.aspx.
  12. Log into TeamSite and view a ASPX page.
  13. If you receive and error like "Access denied to 'Y:\default\main\WORKAREA\test, Failed to start monitoring file changes" then you need to check that all necessary parts of ASP.Net have the correct permissions as per Microsoft Knowledgebase articles 317955 & 316721. Interwoven KB article 53298 may also help to identify the problem.
  14. If all the steps are successful, then delete the old default web site that was renamed in step 1 (optional).
    The "C:\Inetpub\wwwroot\aspnet_client" directory contains JavaScript files used by .NET, and is automatically installed with the framework.

To enable the virtual system to locate this directory you may need to add a virtual directory at the root of the Workarea:

  • From within the IIS console, navigate to the Workarea (i.e. "\iw-mount")
  • Right-click on the Workarea; Select New > Virtual DirectoryEnter "aspnet_client" as the Alias
  • Enter "C:\Inetpub\wwwroot\aspnet_client" for the Directory
  • Use the default permissions

* *Ref:

A. From within the IIS console, navigate to the Workarea (e.g. "\iw-mount\default\main\uam\WORKAREA\load")

B. Right-click on the Workarea and click on "Properties", Under "Application Settings" click on "Create" button.

C. Restart IIS.

Further reading:

See knowledge article # 49749

17 April 2008

TeamSite Upgrades

TeamSite Upgrades Overiew

The overall plan for TeamSite (TS) upgrades are as follows:

Day 1

  • Perform back up procedures
  • Perform prerequisite requirements
  • Upgrade TeamSite and OpenDeploy (OD) with latest patch for TS and OD
  • Apply new licenses

Day 2

  • Upgrade TeamSite Search
  • Configure TeamSite Search
  • Fix any upgrade issues
  • Re-run toolkit.ipl for any UI customization

Day 3

  • Check accounts and permissions
  • Check basic functionalities works in the new upgrade of TS
  • Perform system testing
  • Test form publishing (DCT, DCR and PTs)
  • Test workflows
  • Test OpenDeploy and Data Deploy
  • Test View->My local files
  • Fix any issues found in testing

Day 4

  • Reserve day for fixing any upgrade issues

Bug upgrade report for TS v6.7.1 with SP1
There is a bug report with using VisualFormat editor in TS v6.7.1 Service Pack 1. When a user previews a Data Capture Form that has a text area field using Visual editor, an error pop up page will appear. Use TinyMce instead of using VF as a work around solution.
Latest patch installer for TS v6.7.1 SP1 has glitches with previewing a Presentation Template on the TS server that runs with a Semantic Anti-virus. Skip the step for installing the latest TS patch.


  • Back up the entire hard drive of where TS server and Search server was installed (e.g. if TS was installed at c:\interwoven, then backup the entire c drive).
  • Back up the entire iw-store. If iw-store was stored in a separate partition drive, then back up that entire drive.
  • Get Administrator login account details from the client.
  • Get Interwoven support login account from the client.
  • Notify TS users of outage.
  • Disable all antivirus software/services temporary on the TS and search server (if any), particularly if server has a Semantic virus running, as it will cause problem with new TS installations or upgrades (See knowledge article xx)
  • Check and confirm what current version of TeamSite is installed on all the server boxes that will be upgraded. This is done either by:
    Control panel->add/remove program; or
    Check iw-home\iwinstall\iwov-inventory.xml file
  • Download the relevant TS installation package software from Interwoven support website.

Upgrade instructions
The existing TS.lic license key used for TS v6.5 file would still be valid and useable after the upgrade. So there is no need to generate a new TS license key.

The upgrade path for various TS version on Windows OS is as follows whether the upgrade was on the same or on a different server box:

TS v6.5 upgrade path

  • Upgrade from v6.5 to v6.5 SP 2 (if haven’t done so)
  • Upgrade from v6.5 SP2 to v6.7.1
  • Upgrade from v6.7.1 to v6.7.1 SP1
  • Install only latest patch for v6.7.1 SP1

TS search v6.5 upgrade path

  • Upgrade from Upgrade from v6.5 to v6.5 SP 2 (if haven’t done so)
  • Upgrade from v6.5 SP2 to v6.7.1
  • Upgrade from v6.7.1 to v6.7.1 SP1

OD upgrade path

  • Install OD Base Server v6.1.1
  • Install OD Admin Server v6.1.1
  • Apply latest patch to OD server
  • Install OD receiver v6.1.1
  • Apply latest patch to OD receiver
    *Note: OD v6.1.1 is more stable to install than v6.2

TeamSite Upgrade steps
1. Download the following installer from Interwoven support site:

  • TS v6.7.1 installer
  • TS search v6.7.1 installer
  • TS v6.7.1 SP1 installer
  • TS search v6.7.1 installer
  • Patch update for v6.7.1 SP1

2. Login as Administrator on the TeamSite server machine
3. Backup all configuration files (*.cfg and xml files)
4. Manually stop all TS services and set them to manual on start up
5. Confirm step 4 by going to DOS prompt and type “netstart amore” and look for Interwoven port number
6. Manually stop all IIS
7. Install TS v6.7.1

  • Select “mssql” checkbox and select the SQL JDBC driver file (*.jar) from iw-home\TeamSite\eventsubsystem\lib folder
  • Select “No” for don’t overwrite existing jmsconfignew.xml file

8. Reboot server
9. Log into TeamSite via the internet browser and make sure that you can successfully login in
10. Run iwaccessmigrate with –m & -bg –n parameter
11. Run “iwreset –a”
12. Login into TS to ensure that TS is running after performing step 10
13. Manually stop all the TS services
14. Install TS v6.7.1 SP 1
15. Install the latest patch

  • Manually stop all TS services
  • Run the patch installer

16. Reboot server and login to TS to ensure that it is running
17. Check that event subsystem service is running
18. Decide whether the client will be using either TinyMCE or VisualFormat editor for published form.

  • If using VisualFormat (VF) editor, there is a required additional step to install client visual format on the entire client’s machine that will be using published forms. Location of visualformatclient.exe installer is found at C:\Interwoven\TeamSite\httpd\iw\ewebeditpro20\clientinstall folder. You can customize the VisualFormat toolbar by editing the visualformatconfig.xml file at iw-home\httpd\iw\ folder. (for more information read Form Publisher Developer Guide 6.7.1 release PDF doc)
  • If using TinyMCE, the advantage is that it is already installed with TS because it’s a Java app. However VF is more powerful than TinyMCE. The toolbar can be customized by editing custom_config.js

19. Run script (toolkit.ipl) to migrate any customize UI (if there are any UI customization)


  • Read the installation log file at c:\iwinstall\log folder for any unsuccessful installation
  • Read TS server log file iwtrace.log at iw-home\teamsite\local\logs folder
  • Read iwutid_cmdout.log file for any PT error message provide iwutild.cfg file debug mode enabled

TS search server upgrade steps
Note: If the search v6.5 was installed on a separate server box, then upgrading the TS server can be done independently without needing to wait for TS upgrades. So to save time TS Search upgrades can be simultaneously run in parallel with TS upgrade.

  1. Run TS search v6.7.1 installer on the search server box and install it at c:\interwoven\search folder
  2. Locate and enter the TS server host. Ensure that you can firstly ping the TS server host name to confirm that both search server and TS server box can communicate and ping each other
  3. Locate the shared file system. Usually at iw-home\new folder (create a new folder)
  4. Check that the search service are running
  5. Install the search v6.7.1 SP 1
    * Manually stop the search service
    * Run the installer
  6. Reboot the server
  7. Check that all search services (i.e. Interwoven TS Search & Index) are both running
  8. Configure the search
    * Edit iw-home\cssdk\cssdk.cfg file: Uncomment
    # search.server.host: localhost
    # search.server.port: 6720
    # search.server.maxConnectionLimit: 10
    * Edit iwseach-home\etc\branch.cfg file and add the branches that you want to index
    * Restart search and index services (Stop in order search and index. Start index and then search service)
    * Run CTL:
    iwndxlistbr - Display the list of branches that are index
    iwndxrefreshbr -b /default/brachname…
    iwndxrefreshbr –I /default/branchname.. (Incremental update on real time)

OD upgrades steps
Upgrade the following OD v6.1.1 in this order below.

  • OD base server
  • OD admin server
  • OD receiver server

1. Get a OD license key

  • Go to DOS command
  • Run java -cp od-home/lib/odng.jar com.interwoven.license.LicInfo
    -f output-file -p OD
  • Login the Interwoven support site and go to the OD generate license key webpage
  • Enter the server information generated into the form and submit it

2. Back up a copy of all files from iw-ODhome\config and etc folder.
3. Download v6.1.1 of OD base, admin server and OD receiver installer from Interwoven support site.
4. Stop all previous version of OD services
5. Run the OD base installer. Install it at c:\interwoven\ folder
6. Choose “upgrade” select box from the installation dialog screen
7. Follow the installation instruction on the screen to install it
8. Check the email that will receive the OD license key file
9. Copy OD.lic to iw-ODhome\etc folder
10. Reboot server
11. Check that OD base service is running (i.e. 62 services). If not, then restart it and set to automatic startup

12. Run the OD admin installer on the same server box that had OD base installed in step 5 and follow its instructions
13. Reboot the server
14. Ensure that OD admin server is running

15. Apply latest patch for OD server. Read the README.txt for further instructions on installing the patch. Basically the instruction will instruct you to:
* Stop all OD services
* Run the patch installer
* Update the registry
16. Reboot the server
17. Check that all OD services are running. If not then set OD services to automatic and start the OD Interwoven services (i.e. AccessService, UI admin and 62 services)

18. Run the OD receiver installer on the other receiver server box
19. Choose “upgrade” option box from the installation dialog box
20. Apply latest patch to OD receiver
21. Get OD receiver license key

Post installation

  • Enable the Symantec antivirus is back up and running after the whole TS installation package have been installed. Set the antivirus services back to automatic start up.

09 April 2008

Part 4 - Installing TeamSite Front-Office

TeamSite Front-Office (FO) is a interface tool that allow users access to their workarea & TS functionality within Windows explorer or Microsoft Office applications (e.g. MS Word) . FO consists of 2 components:

  • TeamSite Front-Office Server: Works with your TeamSite server to provide a framework for contributing content from development applications directly to TeamSite.

  • TeamSite Front-Office Client: A client-side application that enables content contributors to access TeamSite features directly from their development applications. This component includes the application plug-ins, the TeamSite Briefcase, and the TeamSite Front-Office Configuration Wizard.

Both of these 2 components will need to be installed individually, i.e. FO server is to be installed on the server that runs and host TS. The other is to be installed on the client's machine.

Installing & Configuring Front Office Server
The instruction below will be installign the latest version of FO version 5.6.6 at the time of writing this blog.

  1. Before you install FO server, ensure that all workarea branches and users with their roles has been added into TeamSite and that the users/group has been appropriate permission to access the workarea.
  2. Before you install the FO Windows server, you must have local Administrator
    privileges because the installation process needs to start and stop the iwwebd
  3. Download the FO server and client software from Interwoven support website. TFO_server566Buildxxx.exe & FTO_client566Buildxxx.exe
  4. Install Front -Office server (v5.6.6) on the server that had TeamSite install, by running TFO_server566Buildxxx.exe. Installation path shall be c:\interwoven\TeamSite Front-Office\ folder
  5. Configure users and workarea in iw-home\conf\iwwa.cfg file to give FO user(s)/group access to a workarea.
  6. Configure iw-home\etc\iw.cfg file under "[FrontOffice]" section.
  7. Configure iw-home\local\config\wft\available_templates.cfg file to add out of the box FO workflows (see availiable_templates.cfg.tfo.example) if submit operations from FO triggers a worflow, i.e. iw.cfg had "wf_submit=yes"
  8. Configure index_template.htx if FO auto-index is enabled in iw.cfg. Then copy the index_template.htx file to each directory within a workarea that you want to index.
  9. Reset Teamsite server with "iwreset -a" command in DOS prompt.

Installing and configuring Front-Office Client

  1. Run FTO_client566Buildxx.exe software on each client's machine that will be using FO.
  2. Follow the instruction on the setup screen.

Further reading
1. Front-Office Admin Guide (PDF version)

08 April 2008

TeamSite Search Overview


The primary use of TeamSite Search is to find a file for:

  • view, editing, copying & reuse

  • removing outdated file
  • reporting purposes

  • recovery purposes

There are other reasons why a user would want to use the search facility in TS but the above points are the common reasons for using a search.

Search facility is made up of 2 parts:

  • Index manager/server :- Controls indexing of content. Also uses a document cracker that looks into the content of a file or data record and provide metadata and full search content on it.

  • Search manager/server :- Performs queries on indices and returns the search result to queries. TS interface communicate with the search manager to request searches and to view the search results.

Both index and search server uses query agent, which is a processor use to perform indexing or querying documents.

So for example if you search for a content (case sensitive search), you send a query to the search manager. The search manager scans a search index for files that match your query, and returns a results page. The results page lists matching files in order of relevance.

There are two types of search methods in TS that user can do:

  1. Simple searches :- Before you can initiate a simple search, you must first navigate into an area on a branch
    that is indexed for search. A simple search query returns documents that contain any of your keywords. Phrase matching, wild cards, and Boolean logic—the use of “and”, “+”, “not”, “-”, and other operators in a search query—are not supported by simple search but is supported in advance search
  2. Advance searches

Configuring search
Search engine can be configured by editing either of the 4 files located in iwsearch-home/etc folder

  1. branches.cfg - Config file to tell the index manager which branch is to be index during startup time

  2. search.properties - Config file to tell the index and search server/manager which set of files is to be index when a user submits a set of fiels through TS.
  3. FieldMapping.xml - Allows additional attribute fields that will be indexed by the index manager.

  4. search.xml (located at: iwhome\httpd\webapps\conten_centerweb-inf\conf\search)

NOTE: Any update of the 4 search configuration fiels above will require a server reboot to take affect.

Provide search feature to control which branches will be index - See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/search4.html

Provide search feature such as:
  • Partial index

  • Controls how many files are submitted to be indexed at a time

  • Controls which files will not be index

  • Control size of file that will be index

  • Enable/disable index update whenever a file is submitted

See - http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/search7.html

07 April 2008

Part 3 - Installing OpenDeploy


  1. Ensure that the server that will have OpenDeploy install meets the system requirement according to the release note.

  2. If OpenDeploy is installed on a Windows OS, ensure that you DOS-compatible 8.3 format file names is enabled. Click here for further instructions.

  3. Ensure that NO other windows application is using RMI registry port 9173, because OpenDeploy will by default uses port 9173 and will need to run this port alone. There will be conflict issues if other non-Interwoven product uses port 9173. Search for port "9173" in the Windows registry system and in the file system to check if other applications uses this RMI port.

  4. You must have Administrator privileges to install OpenDeploy on your Windows server.

  5. Close all other open applications before installing OpenDeploy software on your
    Windows server.

  6. You must close the Services window (not just minimize it) prior to installing
    OpenDeploy on a Windows host. Otherwise, the Windows registry keys will not get
    updated properly.

  7. Go to Interwoven support site (you must have an existing support account), login and download the 3 latest release vesrion of OpenDeploy, i.e. Base server software(IWOVopendeployBaseFull.6.x.x.x.x.Buildyyyyy.Windows.exe), Receiver software(IWOVopendeployRcvr.6.x.x.x.x.Buildyyyyy.Windows.exe) & Administration package software(IWOVopendeployAdmin.6.x.x.x.x.Buildyyyyy.Windows.exe)

  8. Teamsite is already installed on the server.


OpenDeploy (OD) has 3 software components, each of which must be installed on the
appropriate server. Here are the components:

  • Base server software - this is the software which controls the management of
    deployments on the source server. This software permits the OpenDeploy server to
    send and receive deployed files.

  • Receiver software - this is the software that must be installed on each server
    designated only for receiving deployed files. Servers with the base server software
    installed do not need the receiver software.

  • Administration software package - Combine software with the reporting server (software for managing the storage and publication of event-based reports) and ContentServices Foundation (CSF) access service(software for authenticating individuals who will access OpenDeploy base servers or receivers through the
    browser-based user interface or web services)

  1. Install the base server software (see PDF link under "Further reading" section below for instructions) on the server. Accept all default values.

  2. Reboot the server.

  3. Install the administration software package. Accept all default values.Then reboot the server again.

  4. Ensure that the 3 OpenDeploy services are running, i.e. Interwoven "OpenDeploy service", "OpenDeploy SNMP" and "OpenDeploy UI Admin".

  5. Open internet browser and login to the UI admin webpage at http://:8081/iw/opendeploy/login

  6. Login using the bootstrap user account (usually the administrator) that was created during the administration installation. **

  7. Add appropriate users who will need access to OpenDeploy admin UI.
  8. Install the receiver software on the destination server that will receive the deployment.
  9. Obtain a license key by sending a request email to Interwoven support (see "How to obtain a license key" for more details)

**Note: If you are having problem logging into OD admin UI, with message saying something like "invalid user and/or password", then check deploy.cfg and look that the bootstrap user and domain name are correct. If not, you can edit/add another valid user from AD/LDAP. Save the deploy.cfg if there are any changes and restart all the 3 OD services.

How to obtain a license
Obtain a batch license activation for OpenDeploy base and receiver servers, i.e. an individual base server license key and receiver licensing. Licensing for OpenDeploy Administration is not required.

  • Base Server license: You can license your OpenDeploy base server software to operate as one of the following options,i.e. i)full feature version with no time limit; or ii)EasyDeploy, a restricted feature version with no time limit. So tell Interwoven Support which license option you want.
  • Receiver License: You must license and activate each OpenDeploy receiver installation. An expired
    receiver will only accept incoming license deployments.

Further reading

Part 1 - Intro To Using MetaTagger

MetaTagger is a automated process of tagging enterprise business content with descriptive metadata. How? MetaTagger accomplishes this by generating precise, accurate metadata associated with a particular document. In this way, solutions to business problems can be addressed by better organization and use of an institution’s content.

  • Metadata is useful for organizing, surveying, retrieving, and controlling access to content. It helps transform a loosely content into a efficient library catalog. Well-designed metadata can improve Internet or intranet search capabilities, portal personalization, and content distribution. With MetaTagger, you can tag enterprise assets quickly and consistently.
  • MetaTagger helps transform a loosely-organised content repository into a highly efficient library. MT allows you to share, manage, and resuse electronic content by analysing that content, identifying key concepts and organising that content in customised ways.

Example scanerio

Webcast: MetaTagger 4 Developer Introduction
1. PDF
Video (Download the videio player from webEx site)

Further reading

  • MetaTagger v4.1.1 User Guide (HTML version)