Understanding the teamsite directory structure

Posted: 1 November 2010 in Uncategorized
Tags: , , , ,
Windows Explorer in Windows 98

Image via Wikipedia

After you have installed Teamsite, you can check the directory structure of your Teamsite installation.

Here is what I make of the various folders

  • bin => this folder contains the binaries of teamsite, such as tslicinfo which verifies the information you need to license teamsite
  • cluster => ??
  • conf => this folder stores the information about who has been granted access to teamsite
  • cssdk => java jar files for the content services software development kit. You will most likely put these jars on the classpath
  • custom => This is your directory to place your custom scripts (bin) and other custom files. It is a good idea not to place your custom files anywhere else as it facilitates upgrades.
  • derby => the derby database
  • etc => the configuration files such as the teamsite license and the configuration file iw.cfg are located here
  • eventsubsystem => the event subsystem records all the events occuring in the teamsite environment.
  • examples => some random example of files you may wish to investigate
  • httpd => the apache installation document root. contains /iw files (such as images, tinymce), /iw-bin (for cgi scripts), /iw-icons (for icons). The webapps folder is not served from there. This is where the tomcat web applications are stored (see servletd)
  • ilog => the ilog system is used for targeting. this is where your targeting rules are engineered
  • install => the installation directory keeps track of the installed modules. Do not play about with this folder.
  • iw-perl => the perl installation within teamsite
  • iw-webd => an apache installation, whose main purpose is to act as a “controller” and redirect the requests to the tomcat/servletd container, iwproxy for previewing files or serve static files and cgi-scripts (see httpd)
  • kernel => ??
  • lib => the java libraries used by teamsite, the and system libraries (dlls and other .so libraries).
  • Livesite => the livesite data and rules are stored there
  • local => custom configuration files (templating, datasources, meta data tagging) and custom toolkits reside here.
  • log => teamsite log files
  • msg => ??
  • private => mostly contains the “dangerous” binaries such as start /stop and iwfsfix
  • report => possibly something to do with crystal reports???
  • samba => samba installation, so that windows users can access Teamsite files from Windows Explorer.
  • servletd => the Tomcat installation, that serves the /iw-cc, iw-preview, /iw-rta and /iw_eventsubsystem webapps.
  • src => source code part of the apache /iw-mount custom plugin by Interwoven.
  • tmp => temporary directory for writing your own temporary files.
  • tools => the java sdk, ant tools
  • tsreport => reporting tool for teamsite
  1. I discovered your blog site on google and check a few of your early posts. Continue to keep up the very good operate. I just additional up your RSS feed to my MSN News Reader. Seeking forward to reading more from you later on!?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s