Installation Guide

Kapow Katalyst has one unified installer, which installs all the software, even though different parts of it will be run on servers and on client computers. The role (server, client, etc.) of a particular installation is decided during the steps that take place after basic installation of the software.

The following subsections describe:

Upgrading from Earlier Versions

In the interests of stability, different versions of Kapow Katalyst may be installed side by side on the same computer without interfering with each other (except that they must be configured to use different port numbers for Management Console if run simultaneously). This means that you can install a newer version and get acquainted with it while still doing your daily work with the older version.

This also means that important data like uploaded robots, execution schedules and so on will not be shared between different versions installed on the same computer. Thus at some point you will need to copy this data from the old Kapow Katalyst installation to the new one. (There is a similar but separate issue with Design Studio projects as discussed in Notes for Users of Earlier Versions.)

You copy this data from one version of Management Console to another by making a backup of the old installation and "restoring" it into the new one. This process is discussed here. Making a backup is done slightly differently in different versions of Kapow Katalyst, so check the online documentation for the relevant old version to learn how to create a backup. You will find the documentation here: 9.0 8.2 8.1 8.0 7.2 7.1 7.0

If you are running Management Console in a Tomcat web server (see below), be sure to make the backup before modifying your Tomcat configuration for the new version of Kapow Katalyst.

Management Console in Tomcat

The Management Console is a key part of Kapow Katalyst that by default is run as an embedded component inside the RoboServer application. However, it may also be installed as a regular web application on a standalone Tomcat web server. If you want to do that (or decide later to switch to doing that), you need to do a number of additional manual steps as described in the section on Management Console in Tomcat.

When running embedded in the RoboServer application Management Console will use an embedded derby database. At customer sites we have seen degraded performance when having more that 100 schedulers or 500 robots in the embedded Management Console. If you experience that we recommend deploying Management Console in Tomcat where you can choose another database.

If you are upgrading from a previous version of Kapow Katalyst where you have installed Management Console in a Tomcat web server, be sure to make a backup of it (see above) before you install the new version into Tomcat.