Archive for November, 2010

The following example details in javascript how to validate an email address for the web using a regular expression.

            function validateEmailAddress(emailAddress){
                var emailRegex = /^(\w|\-|\_|\.|\'|\#|\$|\*|\/|\^|\!|\%|\&|\=|\||\~|\{|\})+\@((\w|\-|\_)+\.)+[a-zA-Z]{2,}$/;

            prompt("",validateEmailAddress("")); /* valid */
            prompt("email",validateEmailAddress("email")); /* according to the specification, this is valid for the local domain, but we don't have a local domain when we're on the interweb */

the same regular expression can be used to validate email addresses in perl or php

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