Setting Environment path variables allows a user to input on command line a Interwoven command line tool rather than also entering the path and the name of the command line tool

e.g. The TeamSite reset command is iwreset.  Without the environmental path variable set, the command on command prompt would be required to be inputted as;

C:/iw-home/bin/iwreset.exe

With the Environmental path variable set, the command on command prompt would be inputted as;

iwreset (This could be from any location on the command line)

Setting Environment Variables

1. Right Click ‘My Computer’.  You will see the properties option in the context menu.  Select this option
2. A properties window will appear.  Select the ‘Advanced Tab’
3. Now select the button ‘Environment Variables’
4. A new window will appear displaying information regarding Environment Variables.  Scroll down to the option path under system variables.  Highlight this option by selecting it
5. Select the edit option for the variable path
   
6. A new window will appear.  This is the area where you add all the Interwoven Command Line Tools paths e.g C:/iw-home/bin.  For each path you add, you need to add a semicolon (;) at the end.  Thereafter you can enter the next path.Depending on the Interwoven Software, there are many Interwoven Command line tools which are in various paths. Entering them all here will save an abundance of time when using the command line for important commands
7. Select ok, close all windows and reboot the server

You can now enter commands such as iwreset without paths on the command line

Below are useful Search Command Line tools.  They will help with managing the index and search servers

iwsrchgethome - Displays the location of the TeamSite Search home directory.
iwndxmgrfreeze - Freezes and unfreezes the index manager.
iwndxmgrstatus - Determines the current status of the index manager (active or frozen).
iwndxmgrstop - Shuts down the index manager.
iwndxstatus - Displays the index status for branches.
iwndxlistbr - Lists all the indexed branches.
iwdxpurgebr - Removes the index collection associated with the branch.
iwndxaddbr - Adds a branch to be indexed by the index manager.
iwndxrmbr - Removes a branch so it is no longer indexed by the index manager.
iwndxfreezebr - Freezes or unfreezes a branch that is being indexed by the index manager.
iwndxrefreshbr - Reindex the branch using either the bulk or incremental queue.
iwndxregsrchsvr - Register a search server with the index manager.
iwsrchndxstatus - Displays the index status for branches from the search server.
iwsrchquery - Returns the first page of the query output in XML format.
iwsrchgetpage - Displays a page of results from a previously performed query.
iwsrchmgrstop - Shuts down the search server.
iwsrchmgrping - Pings the search server.
iwsrchndxstatuschg - Notifies the search server of changes in the index manager status.
iwsrchattrib - Displays a list of field specifications for indexed attributes.

From my experience there are a few things to bear in mind when installing Interwoven Software.  These include

1. Always install your software as administrator or full root (for solaris/Linux).  In respects to root access it must be full root not any sppof such as sudo. At the lease su root would be acceptable.  There have been installs where I have seen the installer not correctly installing, after which issues later arise.  Another reason to install as full root or administrator is that Interwoven will only support the software if they are installed by these users.
2. Always read the release notes, and ensure you fulfill the pre-requisites.
3. When selecting the install path, don’t leave any spaces.  I like to install as below;
   C:/Interwoven/TeamSite or C:/Interwoven/MediaBin
4. Keep a record of your actions whilst the install take place; will come in handy to document and to analyse any potential issues arising at a later date
5. Follow up your installation by executing any actions that are required after the install

Providing you have TeamSite installed along with TeamSite Search (Both in working order), you can configure TeamSite Search to search within a Data Capture Template (DCT)/ TeamSite template for a specified field

e.g. Organisation ID

The file you need to configure to allow this to happen is FieldMapping.xml, located in search-home/etc

An example of the code you would input here can be found below;

<templates>
<!– * Organisation ID * –>
<template>
<templateType>contactinformation/building</templateType>
<templatingFields>
<templatingField>
<xpath>/main/organisation</xpath>
<fieldSpecification>
<fieldName>OrganisationsID</fieldName>
<fieldType>string</fieldType>
<fieldStorage>zone:contact_info_Organisations_ID</fieldStorage>
</fieldSpecification>
</templatingField>
</templatingFields>
</template>
</templates>

For more information on how you would code this, please contact us and we can expand further on this article

Platform: Linux
TeamSite Version: 6.7.1

I was involved in a recent project where each time the client logged out of TeamSite, they would get a log out error.  Initially we weren’t sure why the error was appearing.  After thorough investigation of the TeamSite logs I came across some errors/warnings in the file servletd_out.log (located in logs/iwui).  Errors included;

The errors did not actually say that there was something wrong in respect to the solution given below, but it got me thinking in respects to the locations it mentioned in the log. I did a search of the location;

/iw-home/servletd/work/Catalina/localhost/iw-cc/org/apache/jsp/teamsite/common/

compared them to a working TeamSite directory from Interwoven Support.  I found the files;
start_jsp.class,
start_jsp.java
were missing in that location.

Solution:

- Get the missing files from Interwoven Support and place them in the location above
- Reset user & group permissions from the directory /iw-home/servletd/work/ onwards to the user iwui and group nobody

TeamSite now logged out with no errors

If you have TeamSite or Search installed on seperate servers, you are required to make configuration changes on both servers, so that they communicate with each other.

On the TeamSite Server:

Browse to iw-home/cssdk/cssdk.cfg. Edit the following entries (near the bottom of the file) according to your Search Server

search.server.host: <Search Server Hostname>
search.server.port: 6720

On the TeamSite Search Server:

Browse to search-home/etc/search.properties. Edit the following entries according to your TeamSite Server

iw.teamsite.server.host=<TeamSite Server Hostname>
java.naming.provider.url=tcp://< TeamSite Server Hostname>:3035/

iw.index.agent.idxdir=C:/iw-index
iw.search.agent.idxdir=C:/iw-index

Platform: Windows 2003 SP1
TeamSite Version: 6.7.1

A recent issue I experienced on TeamSite 6.7.1 was that I couldn’t get access to the TeamSite 6.7.1 interface on the browser.  I would get a HTTP 404 error appearing on the screen

Solution:

- Find the file libeay32.dll under the c:\program files\common files\Interwoven\lib directory.

- Replace the libeay32.dll under C:\Windows\System32 directory with the one in Interwoven directory (mentioned above)
Note: Remember to keep a backup of System32 directory before making the change.

- Reboot the server

Doing this resolved the HTTP 404 error

To index branches in TeamSite Search you need to edit the following file;

Search-home/etc/branches.cfg
(Note: Search-home is TeamSite Search Install Location)

Branches should be inputted as;

/default/main/branch1
/default/main/branch1/branch1a

Points to consider;
- If /default/main is not in use, it is not worth indexing
- You must input each and every branch you want to index including sub branches in the file individually

Process of indexing a branch;

1. Stop the TeamSite Search service
2. Stop the TeamSite Search Index Service
3. Edit the file mentioned above
4. Start the TeamSite Search Index Service
5. Start the TeamSite Search Service

This will begin the indexing of staging area of the inputted branches in step 3.  To enable workarea search, please refer to enable workarea search post.  The process above applies to all operating systems

Platform: Linux
TeamSite Version: 6.7.1

I was involved in a recent project where I was having webdeamon issues.  The service was not starting up, and in due course TeamSite interface could not be seen on the web.  The first thing I looked at was Apache.  However seem to be installed ok, and the service seem to be running ok.  After a thorough investigation of potential reasons why the service was failing to start we found the issue and the solution.

Issue:

The reason why the service fail to start was the nfslock service was disabled (not started in run level 345).

Solution:

Enable the nfslock service (rpc.statd and rpc.lockd)