Now that we have Hello.Java created as a class.  Please refer to the blog
Creating a “Hello World” LiveSite Java External

I will demonstrate below how the class would be utilised in a LiveSite component.

- Create a component (name the component what ever you would like it to be)
- Select the component as XML/XSL format
- In Content XML, add the the following code;  

- Save the component, and Preview the Component
- You will see the Hello.Java class discussed in the blog
Creating a “Hello World” LiveSite Java External in your LiveSite component.

Java classes created in TeamSite & LiveSite reference many other Java files.  These files are located in a different directory of TeamSite, so are referred to as external files to the location where Java classes.

The problem with compiling a Java class comes when the Java file to be compiled looks for these reference files, but can’t find them as they are located externally to where a Java compile takes place.  This is not documented.

Solution:

1. Make sure the Java file you create is in the location;
iw-home/local/config/lib/content_center/livesite_customer_src/src

Files created should be placed into these location corresponding to the file type

iw-home/local/config/lib/content_center/livesite_customer_src/etc/conf for config files
iw-home/local/config/lib/content_center/livesite_customer_src/etc/web for jsp files

2. you need to copy the external jar files which you may require for your own Java file located in;
iw-home/httpd/webapps/content_center/WEB-INF/lib
to
iw-home/local/config/lib/content_center/livesite_customer_src/lib

There are many Jar files which have many java classes which might be referenced in your own Java file.  Typical Jar files which are recommended to copy to the location above are;
- dom4j-1.6.1.jar
- livesite.jar
- livesite_customer.jar
- livesite-runtime.jar

3. Once  you have copied these files over, in command line, navigate to
iw-home/local/config/lib/content_center/livesite_customer_src

4. Run the command iw-home/bin/make_toolkit.ipl

This should now build your Java file successfully to the Java class you require for your LiveSite external component

TeamSite Version: 6.7.1
Operating System: Windows Server 2003

I recently experienced a major issue with the TeamSite server, where by it was not displaying the TeamSite url on the browser.  I was getting a Apache error.

I scrolled through the TeamSite logs to find an error which was causing TeamSite not load correctly.  This can be seen below;

ERROR com.interwoven.livesite.iw.impl.CSBackingStoreService (com.interwoven.livesite.iw.impl.CSBackingStoreService:254) – Error while creating/updating branch: /iwadmin/main/livesite
com.interwoven.cssdk.common.CSException: (Insufficient space to complete operation)

This was found in iw-home/local/logs/ccsdk.log

Solution:

As you can see in the error there is insufficient space detected on the TeamSite Server.  To overcome this problem there are 2 options you have to get TeamSite back up and running

Option 1 – Add more memory to the server, and re-size the partition where TeamSite is installed.  This can be done with a partitioning tool software.  There are quite a few commercialware applications that can achieve the re-size of a partition.

Option 2 – Get a freeware application tool such as ccleaner to remove all unnecessary files on the server.  Also identify applications which are unnecessary and uninstall.  Once this is complete you will have save some space.  In conjunction with this you should also edit the file iw-home/etc/iw.cfg

and change the following line from;

disklowpercent=10

to

disklowpercent=5

Now on the command line do a iwreset – a to restart TeamSite.  TeamSite should now come back up and running and above the 5% threshold of disk space left rahter then the default 10%.  This should buy some time and allow your TeamSite server to run again.

TeamSite Version: 6.7.1
Operating System: Windows Server 2003

I was recently having a problem where when I ran a make_toolkit.ipl in the customer_src directory in TeamSite my web page url of TeamSite would not appear.  I notice I had some directories missing

Solution:

To overcome I had to reinstall webapps.

On Command Line,

cd iw-home/install
install_webapps -l -f

- Once this is finished, run a iwreset -a

This reinstall TeamSite Webapps, and it thereafter my TeamSite url appeared on the browser

When copying over components from one environment to another, you loose the extended attribute which recognises the component as a Interwoven LiveSite component.  Below is how you would set the extended attribute, so that LiveSite recognises the component.

On command line or in a script you would need to execute the following;

iw-home/bin/iwextattr -s TeamSite/LiveSite/Type=component “hostname/iwadmin/main/livesite/component/WORKAREA/shared/component1”

or

cd iw-home/bin/
iwextattr -s TeamSite/LiveSite/Type=component “hostname/iwadmin/main/livesite/component/WORKAREA/shared/component1”

Note:

- For Solaris or Linux, if you get to iw-home/bin,  you would place ./ in front of iwextattr
- iw-home = TeamSite Install Directory
- hostname = Server/Host name
- /iwadmin/main/livesite/component/WORKAREA/shared/component1 = Example of a component stored in the shared workarea under components branch

A problem with TeamSite 6.7.1 on Solaris or Linux servers are when creating a new workarea, group permissions fail to propagate down; meaning permissions don;t filter down.

Any additional folders or files created or imported with the “File Import” menu action will take on the logged-on user’’s primary group; not the workarea group.

Solution:

To overcome this potential problem, configure the workarea permissions such that the group you specified is automatically propagated down to newly created folders and files; therfore inheriting the workarea group permissions only. This approach works applies to both ordinary Unix groups and TeamSite groups.

After creating a new workarea, enable the “set-group-ID” permission on the workarea by running the following command on cmd (execute the command as the user root);

“chmod g+s”

e.g.

chmod g+s /default/main/branch1/WORKAREA/test_workarea

Once the command execute, you can verify the command has been successfully executed by running the command;

“ls -ld”

e.g.

ls -ld /default/main/branch1/WORKAREA/test_workarea

You should find a “s” in the group permissions, such as:  drwxrwsr-x

Platform: Linux
TeamSite Version: 6.7.1

I was recently involved in a project where I was getting a constant error message appearing in my iwtrace.log (iw-home/local/logs).

The error casued TeamSite not to start correctly.  I was looking up reasons and solutions for the error, and found the below;

Cause:

TeamSite is reading over a 1000+ users and groups. Once a investigation was done on where this came from, it became apparent that the users and groups were for a requirement for a previous project.  Each time the server rebooted, the server would synchronise with the main server, so the configuration of 1000+ users and groups would continue to exist.

Solution:

- Remove group and users’ db on the server, along with reference to the users and group db in the file nscd, located in the /etc directory in the parent directory.
- Also the removal of Server synchronization with users and groups from the main server.

Making these changes helped to resolve the issue, with error message not appearing again

I was recently involved in a project where I was getting a constant error message appearing in my iwtrace.log (iw-home/local/logs).

I was looking up reasons and solutions for the error, and found the below;

Cause:

The error is caused by an attempt to run TeamSite on an NTLM domain. TeamSite no longer supports NTLM domains: you must run TeamSite on a Windows 2000 or later (Active Directory) domain.

Solution:

Add your TeamSite server to a Windows 2000 or later (Active Directory) domain then the error messages should go away.

Also, it is recommended to add the line set domain_list=<DomainName>
under the [iwserver] section of iw.cfg,
located in iw-home/etc.

<DomainName> is the list of domains not including the local machine name the local machine name. If domain_list is incorrect, then you will see a variety of error messages in the iwtrace.log (mostly referencing ADSI problems) and possibly even a server crash.

When doing an upgrade of any Interwoven Software package, it is always handy to know what version you are upgrading from.  This will allow you to plan your upgrade path according to the current version installed.  Finding the exact TeamSite version can be quite tricky.  Below is a way to get the latest TeamSite version

1. Navigate on command line (cmd) to iw-home/bin
2. Run the command iwversion.  If you are running this command on a Linux/Solaris box you would input this as ./iwversion

You will now get the output of the current TeamSite version installed on the server