It is often useful to setup a “Multi-Select Datum” in a LiveSite component, but how do you write the Java external to receive this array of parameters?

The following code snippet from Raj Shekhawat shows you how:

//LiveSite returns Multiple select values in the form of ArrayList object
//Searchproperties is my parameter name
 ArrayList selectedProperties= (ArrayList) context.getParameters().get("SearchProperties"); 
 
String selectedValues = "";
Iterator propertiesIterator = selectedProperties.iterator();
 while (propertiesIterator.hasNext()) {
             selectedValues += propertiesIterator.next();
}

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

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.

I wrote a post recently regarding how to install LiveSite 3.0.2 with OpenDeploy 6.1.1

and TeamSite 6.7.1 SP1 http://www.littleforest.co.uk/articles/livesite302-installation/

This post expands on the post written above where by you get OpenDeploy 6.0.2 to work

with LiveSite 3.0.2 and TeamSite 6.7.1 SP1.

As long as you follow the process stated in the post above you can then go ahead and install;

1. OpenDeploy 6.2.0 Base/Receiver
2. OpenDeploy 6.2.0 Admin
3. OpenDeploy 6.2.0 Patch

If you have TeamSite 6.7.1 SP1 and wish to have LiveSite. You will need to install LiveSite 3.0.2

There are certain pre-reqs that need to be followed before doing the installation

1. OpenDeploy must be installed on the server. This at present (25th July 08) can only be
   OpenDeploy 6.1.1 with the latest patch. NOTE: It will not work with OpenDeploy (OD) 6.2.
   The installation will not be able to detect OpenDeploy should you install OD 6.2,
   and will display an error
2. You need to have a minimum of 2gb space whilst installing, else you will experience
   errors near the end of the installation, with LiveSite unable to write to TeamSite
3. Make sure you have enough virtual memory. Again errors will appear similar to point 2
4. You need to have a DBMS installed that will be integrated with LiveSite. If you don’t
   then you will have to cut short your installation. Create a LiveSite runtime, and
   LiveSite Development database. You can name it what ever you wish
   (you will need this for the installation)
5. You will need create a user ‘DomainName\livesite-od’ in Windows or on a UNIX box
   just ‘livesite-od’. This user needs to have od-admin access; which can be done via the OD interface
6. You will need to configure OpenDeploy Web services as described in the location
   
   <od-home directory>/websvc/README_OD_WEB_SERVICE
   Ignore the 1st step of the ‘README_OD_WEB_SERVICE’ file as this step is done by the LiveSite Installer
7. Configure odbase.xml. You will find odbase.xml in <od-home directory>/etc
   You need to apply (uncomment) the following <databaseDeployment> and
   <webServices> sections and enter the appropriate host name:<databaseDeployment>
   <standalone enabled=”yes”/>
   <das enabled=”yes”/>
   </databaseDeployment>

   <webServices enabled=”yes”>
   <httpTransport port=”port_number” host=”hostname”>
   </httpTransport>
   </webServices>
   

Once you have all this in place you can begin the installation, and the install should run smoothly

After Installation, you will need to complete a few post installation steps.
This can be found in the LiveSite Installation guides created by Interwoven from page 38 onwards

Now LiveSite, TeamSite & OpenDeploy should be up and running

If you wish to change the user of ‘livesite-od’ after installation you can do so by going to

C:\Interwoven\TeamSite\local\config\lib\content_center\livesite_customer_src\
etc\conf\livesite_customer\opendeploy.properties

Here you will be able view and change the user account information

For LiveSite 3.0 upwards, if you wish to make any configuration changes to the database details you would need to go to:

<iw-home location>\local\config\lib\content_center\
livesite_customer_src\etc\conf\livesite_customer\database.properties

Here you can configure the databse schema information for your runtime server as well as the local development server

The following (simple) scripts may be of use.

You can use them to query the status, and update the general purpose XSL files (e.g. myTemplate.xsl)

This is handy as the files have to be copied to 3 locations. Instead :-

1) Copy the file into your home dir on the UNIX box using FileZilla.

2) Then run the scripts (from your home dir) as per below to check timestamps,
or update the files (note that there is no backup taken)

Rgds,

Richard.

> more ls-templates.sh

#!/usr/bin/sh

echo $1

ls -las /usr/iw-home/local/config/lib/content_center/livesite_customer_src
/etc/conf/classes/com/interwoven/xsl/$1

ls -las /usr/iw-home/httpd/webapps/iw-preview/WEB-INF/classes/com
/interwoven/xsl/$1

ls -las /usr/iw-home/httpd/webapps/content_center/WEB-INF/classes/com
/interwoven/xsl/$1

_________________________________________________

> more update-templates.sh

#!/usr/bin/sh

echo $1

cp $1 /usr/iw-home/local/config/lib/content_center/livesite_customer_src/etc/conf
/classes/com/interwoven/xsl/

cp $1 /usr/iw-home/httpd/webapps/iw-preview/WEB-INF/classes/com
/interwoven/xsl/

cp $1 /usr/iw-home/httpd/webapps/content_center/WEB-INF/classes/com
/interwoven/xsl/

_________________________________________________

> ./update-templates.sh myTemplate.xsl

myTemplate.xsl

> ./ls-templates.sh myTemplate.xsl

myTemplate.xsl

18 -rw-r–r– 1 root root 8459 Jul 23 13:52 /usr/iw-home/local/config/lib/content_center
/livesite_customer_src/etc/conf/classes/com/interwoven/xsl/myTemplate.xsl

18 -rw-rw-rw- 1 root root 8459 Jul 23 13:52 /usr/iw-home/httpd/webapps/iw-preview
/WEB-INF/classes/com/interwoven/xsl/myTemplate.xsl

18 -rw-r–r– 1 root root 8459 Jul 23 13:52 /usr/iw-home/httpd/webapps/content_center
/WEB-INF/classes/com/interwoven/xsl/myTemplate.xsl