This wonderful little tool written by Richard Aldridge uses ’sed’ to group together all the files under a particular folder of a certain type (in the example this is files whose name contains the string ‘local’ but you could easily change this to look for other groups of files such as ‘.log’ or ‘.html’ files) and then adds all their sizes up to give a total number of kb the files amount too.

find . -name '*local*' -ls | awk 'BEGIN {$count=0} /./ {$count += $7} END {print $count}'

How to clear the LiveSite Runtime Cache

You can go to the following URL on your runtime server to clear the JCS cache:

http://runtimeservername/iw/admin/JCS.jsp

You should see a screen similar to the below, where you can click on “Clear all regions” link or the “Remove All” links on the right hand side of the table.

Other things to try and help troubleshoot caching issues are:

1. On runtime server you may want to manually remove all the cache files. To do this you need to change directory to the
“LiveSite Run Time.ear/iw-runtime.war/WEB-INF/livesite.cache” folder and remove all files such as component.data, component.key, page.data and page.key.

2. Don’t forget to look at the component cache settings too, as well as your own browser cache settings. It may help to delete all local files from the browser cache
including session, path and domain cookies. Use Firefox’s “Firebug” and “Web Developer” plugins if you are not familiar with how to do this in your browser.

3. Check from another user desktop to see if they are experiencing similar issues to your own.
This can help eliminate the client side from any cache related troubleshooting you are doing.

4. Re-start the LiveSite Runtime Application server

Thanks to WCM Rant for this tip on LiveSite Controllers, we had not added an External and it was not working. Once the “dummy” External was added this worked!

Check out the post here

If you see the below in the “servletd_out.log” then you need to run a Make Toolkit with the “Clobber” parameter to clear out the Content Centre application and then you need to run a standard “Make Toolkit” as follows:

Change Directory using:
“cd /iw-home/local/config/lib/content_center/customer_src”

issue the command “/iw-home/bin/make_toolkit.ipl -target clobber”

Wait for this to complete and then issue the command /usr/iw-home/bin/make_toolkit.ipl

 
     [exec] BUILD FAILED
     [exec] /usr/iw-home/install/livesite/post-install-webapp-livesite.xml:191: 
     Could not create task or type of type: serverxmlmunger.
     [exec] Ant could not find the task or a class this task relies upon

The below example runs and simply prints the file names of files inside the c:\temp folder, you will need to add the behaviour you require on the “print” line:

Command line call:

perl.exe c:\find.pl c:\temp

Script

use strict;
use File::Find;
 
my ($area) = @ARGV;
my(@files, $file);
 
find(\&wanted, $area);
		foreach $file(@files){
			if (-f $file){
				print "File: $file\n";
			}
		}
sub wanted {
	push @files, $File::Find::name;
	return @files;	
}

Result

File: c:\temp/find.txt
File: c:\temp/find2.txt
File: c:\temp/find3.txt
File: c:\temp/find4.txt
File: c:\temp/regfind.exe

If you get the following error message when viewing a page in the LiveSite Runtime environment:

“Error 500: Filter [runtime.filter.OpenSessionsInView]: could not be initialized”

Please check the pagetype-config.xml file as this may have an error in it. This is usually located in the following folder:

…/WEB-INF/conf/livesite_customer

In case you have lost your working version of this file you can find one here.

TeamSite 6.7.1 has some nice new URL Commands that give quite a
detailed view of various elements in the tool:

The master list of these can be found by placing the following in the
browser address bar, replacing ‘servername‘ with the name of your TeamSite server.

The Master List

URL to use:
http://servername/iw-cc/command/iw.base.show_command_descriptors

This command shows the below and very long list..

I have picked out a few useful examples below from the above master list:

Show Performance

URL to use:
http://servername/iw-cc/command/iw.base.show_performance

Returns the below results:

JSP Snoop

URL to use:

http://servername/iw-cc/command/iw.show_snoop

This command returns useful environment information just like ‘show_env.cgi’ does:

Show Loggers

URL to use:

http://servername/iw-cc/command/iw.base.loggers

Returns the below type results to the browser

The above allows you visual easy control of the log4j level settings on all the objects
in TeamSite. Remember to always check this is in ‘default’ setting when running the
server under Production so as to not add unnecessary overhead to the system.

There are lots of other commands, use the master list mentioned first in this article
to play around and find the others you like.

The below are some further useful ones:

http://servername/iw-cc/command/iw.admin.teamsite.iwserver_stats

http://servername/iw-cc/command/iw.admin.teamsite.jvm_memory

http://servername/iw-cc/command/iw.base.caches

http://servername/iw-cc/command/iw.ping

Enjoy!

This is a list of questions to ask a new project that is required to be delivered on an existing Interwoven platform.

The idea with asking these questions is to get an immediate feel for size, benefits and risks of the project and then to help set the clients expectations on timescales, budgets and quality of the deliverable.

- What date do you need to deliver the project?

- Who is the end customer for the project?

- Who will sign off the project for the business?

- Who will assist with testing?

- Who will assist with the requirements document?

- Is there more than one business unit involved?

- Is this a new website?

- Is a change needed to the CMS Service Level?

- Is there any 3rd Party Integration?

- Is there any integration with backend systems?

- Can we have a content freeze?

- Are Web Site analytics required?

- Are page Redirects required?

- Are there any additional CMS Support requirements?

- Is there a requirement for multi-language support?

- Do we need to create or update branches?

- Do we need to create or update workareas?

- Do we need to create or update deployments?

- Do we need to create or update data capture forms?

- Do we need to create or update presentation templates?

- Do we need to create or update components?

- Do we need to create or update workflows?

- Do we need to create or update menu items?

- Do we need to create or update users or groups on the servers?

- Will content need to be regenerated?

- Will content need to be migrated?

- Do we need to create or update a cron job?

- Is this a global code change or specific to a project?

- What other technical teams are involved?

- What is the availability of the other technical teams for the dates?

- What dates will we need to raise Change Requests on?

- Which team will own the project once it is in Production?

If your LiveSite page layout is missing you will see the following error on the runtime website:

Error 500: Filter [runtime.filter.DispatchFilter]: filter is unavailable.

To fix this copy your page layout file to the following folder:

…WEB-INF/classes/com/interwoven/xsl/runtime/

To make things a little less disruptive on development servers I recommend using a simple “compile” script for running any Java code.

This is good to do to check that all compiles ok before running a “build.sh” (which takes down the TeamSite UI for a minute or so
and so disrupts any other work being done on the server).

The “just_compile.sh” file should be placed in /usr/iw-home/local/config/lib/content_center/livesite_customer_src.
You need to pass in the full path to your Java file like this (on one line though!):

./just_compile.sh
"/usr/iw-home/local/config/lib/content_center/livesite_customer_src
/src/com/littleforest/examples/Hello.java"

You may need to edit the below “just_compile.sh” to add in new jars that your Java class needs to include.
Also note the $1 at the end which is the name of the Java class you want to compile.

/usr/iw-home/tools/java/bin/javac -cp
/usr/iw-home/httpd/webapps/content_center/WEB-INF/lib/livesite-runtime.jar:
/usr/iw-home/httpd/webapps/content_center/WEB-INF/lib/dom4j-1.6.1.jar:
/usr/iw-home/httpd/webapps/content_center/WEB-INF/lib/customer.jar $1