When installing the Tibco Workspace Browser 11.1 I experienced some unexpected problems. Before installing this tibco product I had to install Apache Tomcat. I ended up with Tomcat 6.0.20. Then I installed the tibco iProcess Workspace Browser and requested the URL from the Tomcat server in my browser.

The first error was that Tibco browser page could not connect to the iProcess Action Processor. After some restarting the tomcat application server failed to display pages. The error message was a LifecycleException indicating that something was wrong with the user database resouerce. This is a configuration file configuring the username and the password of the Tomcat administrator user.

It turned out to be an entirely different problem. I uninstalled the Tibco iProcess Workspace Browser, Tomcat and then reinstalled the latest Tomcat version: 6.0.24. The tomcat installation executable warned me to use a 64 bit java version for my 64 bit windows operating system (e.g. Windows 7 or Windows XP). So I did that. Then my web page still could not connect to the Tibco Action Processor running in Tomcat. This problem went away after I uninstalled the Tibco product, rebooted and installed it again. The rebooting was a recommendation that showed up at the beginning of the installation.

The next error was that the Action Processor could not load the file icuuc36.dll. This file was shipped with the Apache 32/64 bit installer file but this library seemed to be a 32-bit library. It was compatible with my 64-bit java version. So I started to read the manual of the Tibco iProcess Workspace Browser. It turned out that only the Action Processor should run within the Tomcat webserver. The iProcess workspace client can also run from a local disk, provided that the url to the Action Processor is correct. So I installed the Action Processor as a Tomcat web container on the same 32 bit machine as the iProcess server. Within the iProcess workspace browser I corrected the url to the Action Processor in the file JSXAPPS/ipc/config.xml.

Unfortunately my Firfefox 3.5.x browser could still not connect to the Action Processor. Only Firefox 3.0.x is supported and not Firefox 3.5.8, which is now the oldest Firefox available for download. The unsupported Google Chrome browser could not connect to the Action Processor either. But Internet Explorer 7 and 8 were able to open the page connect to iProcess and log on to iProcess. Later I found out that I should use IE7 when developing with iProcess Workspace 11.1 Components. This package is not compatible with the latest GI version (3.9), only with GI 3.6.2, which does not support IE8.