Problem

You are trying to setup Derby database for use with the Interwoven Event SubSystem.

You have followed the installation instructions manual

You get the following error in the eventsubd.log when starting the Event Subsytem:
“Cannot create PoolableConnectionFactory”.

Potential Solution

Check where the testdb database file has been created as the default in the Interwoven instructions creates the db file in your current working directory. Derby looks for the database by default in it derby/bin

Other possible problems:

1. Check the database exists by connecting to it and doing a “show tables” as per the Interwoven instructions
2. Check the driver exists and is in the correct location (/usr/iw-home/eventsubsystem/lib/derbyclient.jar – is “374965″ in size for TS 6.7.1)

3. Check your configuration in “/usr/iw-home/eventsubsystem/conf/jmsconfignew.xml”

Should be as follows:

<DatabaseConfiguration>
<RdbmsDatabaseConfiguration
driver=”org.apache.derby.jdbc.ClientDriver”
url=”jdbc:derby://localhost:1527/testdb”
user=”usr”
maxActive=”10″
maxIdle=”5″
minIdleTime=”1800″
evictionInterval=”3600″ />
</DatabaseConfiguration>
ERROR

EVENTSUBD_HOME is set to /usr/iw-home/eventsubsystem
OpenJMS 0.7.6.1
The OpenJMS Group. (C) 1999-2004. All rights reserved.
http://openjms.sourceforge.net
org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory, cause:

java.sql.SQLException: The connection was refused because the database testdb was not found.
at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection
(DriverConnectionFactory.java:82)
Caused by: org.apache.derby.client.am.DisconnectException: The connection was refused because the database testdb was not found.

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

Setting Environment path variables allows a user to input on command line a Interwoven command line tool rather than also entering the path and the name of the command line tool

e.g. The TeamSite reset command is iwreset.  Without the environmental path variable set, the command on command prompt would be required to be inputted as;

C:/iw-home/bin/iwreset.exe

With the Environmental path variable set, the command on command prompt would be inputted as;

iwreset (This could be from any location on the command line)

Setting Environment Variables

1. Right Click ‘My Computer’.  You will see the properties option in the context menu.  Select this option
2. A properties window will appear.  Select the ‘Advanced Tab’
3. Now select the button ‘Environment Variables’
4. A new window will appear displaying information regarding Environment Variables.  Scroll down to the option path under system variables.  Highlight this option by selecting it
5. Select the edit option for the variable path
   
6. A new window will appear.  This is the area where you add all the Interwoven Command Line Tools paths e.g C:/iw-home/bin.  For each path you add, you need to add a semicolon (;) at the end.  Thereafter you can enter the next path.Depending on the Interwoven Software, there are many Interwoven Command line tools which are in various paths. Entering them all here will save an abundance of time when using the command line for important commands
7. Select ok, close all windows and reboot the server

You can now enter commands such as iwreset without paths on the command line

From my experience there are a few things to bear in mind when installing Interwoven Software.  These include

1. Always install your software as administrator or full root (for solaris/Linux).  In respects to root access it must be full root not any sppof such as sudo. At the lease su root would be acceptable.  There have been installs where I have seen the installer not correctly installing, after which issues later arise.  Another reason to install as full root or administrator is that Interwoven will only support the software if they are installed by these users.
2. Always read the release notes, and ensure you fulfill the pre-requisites.
3. When selecting the install path, don’t leave any spaces.  I like to install as below;
   C:/Interwoven/TeamSite or C:/Interwoven/MediaBin
4. Keep a record of your actions whilst the install take place; will come in handy to document and to analyse any potential issues arising at a later date
5. Follow up your installation by executing any actions that are required after the install

If you have TeamSite or Search installed on seperate servers, you are required to make configuration changes on both servers, so that they communicate with each other.

On the TeamSite Server:

Browse to iw-home/cssdk/cssdk.cfg. Edit the following entries (near the bottom of the file) according to your Search Server

search.server.host: <Search Server Hostname>
search.server.port: 6720

On the TeamSite Search Server:

Browse to search-home/etc/search.properties. Edit the following entries according to your TeamSite Server

iw.teamsite.server.host=<TeamSite Server Hostname>
java.naming.provider.url=tcp://< TeamSite Server Hostname>:3035/

iw.index.agent.idxdir=C:/iw-index
iw.search.agent.idxdir=C:/iw-index

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 your experiencing trouble with OpenDeploy starting up and are seeing ‘ERROR: LicenseException: Bad host name’ errors in the OpenDeployNG/od.log file, this post will help resolve the issue.

To get your domain name and host name, on the Command Line type:

<Your OpenDeploy Home Directory>\OpenDeployNG\jre\bin>java -cp <Your OpenDeploy Home Directory>\opendeployng\lib\odng.jar com.interwoven.license.LicInfo -f <ODlic.log> -p OD

Use the output of this command to help generate the OpenDeploy license key

Now do the following:

On Windows check the following registry keys (Click Start, run, and type regedit)

\\HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DhcpDomain
\\HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Domain

Make sure they match exactly, same string and case.  If dhcpDomain does not exit, create it (String value)

The key \\HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Domain holds the Primary DNS Domain, and is set as follows:

1. Right click My Computer and select properties
2. Select the ‘Computer Name’ tab
3. Click on the “More” button and populate the “Primary DNS Suffix”
4. A system reboot is required after the change.

Also the key \\HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\hostname holds the system hostname,  should be tied to the correct ip address, and defined in winnt\system32\drivers\etc\hosts.

To verify the hostname and IP “seen” by OD, you can review the odbase.log for the line “Network Address available on localhost” for the correct host or IP which should match the OD.lic file

On a Unix box, verify that the primary domain in /etc/resolv.conf matches the domain in /etc/hosts and the domain returned by nslookup on the server.