Tag Archive: Enterprise Application Integration

Back with a  Bang, the new release of Interwoven TeamSite 6.7.2. It brings in lots of new features and improvements. Interwoven has been rated “Strong Positive” in Gartner’s “MarketScope for Web Content Management“. And that seems to me is because of Interwoven TeamSite. One of the strongest web CMS, so far I’ve seen.

Now lets take a look at the new features of Interwoven TeamSite which makes it so strong.

Merged Installation:

In the new installation of TeamSite has got the components (SitePublisher and Targetting ) merged with it. It earlier had the ReportCenter as a merged component. Still if anyone needs to install components seperately they can do it. However, the merged installation procedure reduces the pain for the configurations that have to be done after the seperate installaiton for other components.

New Server Platforms:

The new version of TeamSite supports latest operating systems.

  • Solaris 10, Solaris 10 LDOM
    • Solaris patch cluster containing OS and kernel patches are required prior the installation
    • TeamSite required to be installed in a Solaris 10 global zone; multiple zones are not
      supported as yet.
  • Red Hat Linux ES 4.0 and 5.0 (32-bit and 64-bit) on x86 and x86-64 platforms.
  • Windows 2003 SP1 and SP2 Enterprise and Standard Editions, Windows 2003 R2,
    Windows 32-bit OS on x86 and x86-64 platforms


TeamSite can now be run on VMware Server or VMware ESX.

New Application Servers:

The following applicaton servers are supported by TeamSite.

  • Tomcat 5.5.25 (Currently sitepublisher only supports Apache Tomcat only)
  • BEA WebLogic 10.2
  • IBM WebSphere 6.1.0 update 11

VisualFormat Editor (VFE) Integration:

VFE can now be integrated in to your custom pages

Workflow External Task commands using URLs:

An external task can now be configured to run a URL command. The URL command can be configured to run from the TS local server or a remote server. The server needs to use Java for the same. I liked this feature a lot. Coz now one can actually do a lot of stuff using this task and the possibilities are numorous.

These are some of the new TeamSite features. And there are a lot more. You can refer to the Interwoven Support website or the documentation for more details.


TeamSite 6.7.0 has been improved or enhanced drastically against TeamSite 6.5 in the areas of Users, Groups, Roles, and Workflow. It has been improved in the other areas as well which gives quiet a good flexibility to a developer. It makes development quiet fast and easy as in against TeamSite 6.5. The best thing I loved is the workflow modeler that has come in picture. Well I’ll talk about the workflow modeler later in another blog. Lets discuss the new features in TeamSite 6.7.0.


The enhancements or new features in installation are mentioned below:

  • OpenAPI is no longer supported or prompted for during installation.
  • The first step in role and permission migration is automatically performed by the installation program during the installation procedure.
  • The installation program now prompts for the Utility Daemon port.
  • MySQL is now offered as a choice for the Event Subsystem database.

Administration UI

The Administration UI has been modified and is available from CCPro for users in the Master role. The Master users can change configuration information, add OS users to TeamSite, create and edit roles, manage groups, view log files, abort the server process, and reset the server.

Users, Groups, and Roles

TeamSite provides five out-of-the-box flexible roles that allows a master user to modify them and/or create own roles. Users are not required to specify a role when they log in to TeamSite. Users and their roles are managed at the branch level. Also as part of defining roles, authority to manage branches and users can be delegated to users with a specific role. Managing branch includes tasks such as creating branches, adding users to branches, determining the role the user has in the branch, and restricting access on the branch. TeamSite Groups can be created and managed similarly as roles. The Actions menu has three new menu options—Manage Branches, Manage Groups, Manage Users—to facilitate these activities.


The enhancements or new features in installation are mentioned below:

  • Expand/Collapse All button has been added in data forms to expand or collapse all replicants(Containers). This feature is controlled by UITK
  • Replicant Titling: Displays the content of the first replicant in the replicant group’s title. This feature is controlled by the “isTitle” attribute of the element in datacapture.cfg.
  • The datacapture.cfg file now has been updated with the following:
    • The <root-container> element now has and <choice> as subelements.
    • The <container> element now has <choice> as a subelement.
    • The <choice> element now has the refid attribute.
    • The <label> attribute in the <itemref> element is now IMPLIED.
    • The <item> element now has the isTitle attribute.
    • The <browser> element now has <callout> as a subelement.
    • The <cred> element now has the group attribute.
  • The matching criteria for the role attribute of the <cred> element have been redefined to support flexible roles.
  • In the templating.cfg file, the <cred> element now has the group attribute.
  • Data Record Search: Lets users search an entire data record for data, even if it contains collapsed replicants. This feature is controlled by the UI Toolkit


The enhancements or new features in FormAPI are mentioned below:

  • IWItem.getLabel
  • IWItem.setLabel
  • IWItem.getDescription
  • IWItem.setDescription
  • IWDatacapture.getGroups
  • IWDatacapture.getRoles


The workflows can now be created using the workflow modeler GUI tool. This tool gives you the ability to create the workflows using the drag and drop functionality. Workflow modeler saves a lot of time compared to the earlier workflow development, which used to take days can now be done within hours.

Command-Line Tools (CLTs)

The following new CLTs are introduced.

  • iwaccess: Controls TeamSite user permissions for access to files, directories, areas, and jobs. Defines roles that one user can delegate to another.
  • iwaccessmigrate: Applies user and group permission entries for configurable roles and delegated administration following an upgrade from a pre-6.7 TeamSite release.
  • iwndxwamodificationsbr: Enables or disables indexing of workarea modifications for the specified index branch.
  • iwldapuserscache: Generates the tsldapusercache.xml file.
  • iwroleadm: Administers configurable roles for TeamSite users and groups.
  • iwuseradm: Add and remove TeamSite users, change user attributes, view and set user attributes, and perform other user administration activities.
  • iwutildreset: Resets utility daemon configuration settings.
  • iwutildstat: Displays active utility daemon operation statistics.

The following CLTs have been revised:

  • iwfsck
  • iwgroup (includes the ability to run as non-root)

TeamSite Server

The iwutild utility service performs tasks such as executing commands on behalf of trusted clients with impersonation, reading and writing configuration, and reading log files. The iwutild.cfg file can be edited.

OpenAPI and TeamXML are no longer supported.

Configuration Files

The enhancements or new features in configuration files are mentioned below:

  • The master.uid, administrator.uid, editor.uid, and author.uid files are no longer used. User information is stored in the tsusers.xml file.
  • The ldap_roles option in the iw.cfg file has historically contained the name of the LDAP attribute used to store TeamSite role information. This option is now used to store information on whether the user is a TeamSite user or Master and the preferred ContentCenter interface for the user.
  • The branch_owner_role option in the [iwserver] section of the iw.cfg file changes the default role given to the owner of branches being created.
  • The admin_roles in the [iwserver] section of the iw.cfg file determines the administrable branches of a user.
  • The ldapcache_thread_delay option in the [iwserver] section of the iw.cfg file specifies the frequency with which the ldapuserscache.xml file is updated.


TeamSite Search has been enhanced to provide indexing of and searching modifications in workareas of indexed branches. Four new parameters have been added to the
search.properties file. When users perform a search, modified content in workareas will be included in the search results.

Searching across branches or areas can be done using the Content Services API.
ContentCenter users cannot currently search across branches or areas.

Content Transformation Services

Content Transformation Services powered by CambridgeDocs provides a method for TeamSite users to convert Microsoft Word documents to PDF or HTML output. If the
content transformation engine is installed, the Convert menu item is added to ContentCenter menus.

User interface Tool Kit (UITK)

The UI Toolkit has the following new features:

  • Role permissions for custom menu items and tabs can refer to custom roles.
  • The file templates feature can be enabled and customized for ContentCenter Professional. A file template URL command has been added.
  • The default behavior of the ContentCenter interfaces can be further customized:
    • The default submission step can be turned off for non-submit wizards (such as copy or delete file) in ContentCenter Standard.
    • Searches can now be automatically restricted to not return Data Content Records.
    • Complex subsections of forms can now be set to not be automatically expanded when the forms containing them are displayed.

I’m starting this as the first post on my blog because I wanted to start with the past of TeamSite and then slowly move towards the present TeamSite. TeamSite 6.5 is a very old version. However, there are many companies still using the older version and the TeamSite developers working on the latest versions might not be aware of it. Also someone might need to check what the older version of TeamSite had and this could be a good reference.

License keys

The way for licensing TeamSite has changed from this version. You now have to acquire license key from Interwoven when you install TeamSite. Earlier there was a little complicated prosidure to install the license. In this version:

  • License keys resides in iw-home/etc/TS.lic (not in iw.cfg as in earlier releases).
  • The number of content stores and server CPUs is encoded in TeamSite license key.

Content Transformation Services

This services allows TeamSite users to convert MS Word documents to PDF or HTML format directly from ContentCenter Standard(CCStd) or ContentCenter Professional(CCPro). This service needs to be installed seperately.

Submit Wizard Configuration

The default behavior for CCStd is to invoke a submit wizard after the following file operations:

  • Create New DCR
  • Edit
  • Delete
  • Copy
  • Move
  • Rename
  • Import

CCStd can be configured to skip the submit wizard following these operations.

User and Group Access

The TeamSite server can be configured to use cached user and group information at startup and startup time can be significantly reduced. TeamSite roles can be stored in LDAP or Active Directory.

Configuring File System List Columns in CCPro

In this TeamSite release, the lists associated with the file system (files, directories, branches, workareas, and so on) can be customized for column display and order.

The iwfsck Command

This CLT has now several new and deleted options and was modified to improve performance.

Language Support

TeamSite is available in following non-English languages:

  • Simplified Chinese
  • Traditional
  • Chinese
  • French
  • German
  • Japanese
  • Korean


Searching on non-English language specific content is now available in the Advanced Search screen.Support for full text and metadata search is now available at the API level.


Dramatically improved performance of iw-webd in high-volume environments. Handling of Active Directory groups has been improved. Listing forms and generated assets and access control have also been improved.


Automatic edition numbering is now handled by TeamSite.


Workarea and folder restrictions can now be specified in available_templates.cfg

These are the features I’m aware of in TeamSite 6.5 SP2. If you think I’ve missed anything you can just post a comment to this blog. I’ll update the blog accordingly.