Deploying into Tomcat

We will now detail how to install the Management Console on a stand alone J2SE web container. For this guide we have chosen Tomcat, the distribution has been tested on Tomcat 5.5, 6.0 and 7.0. Your J2SE web container must be using the Java 7 runtime or later. For example, you can visit the Oracle Java SE Downloads site and download the latest Java 7 release.

Configuring ManagementConsole.war

The Management Console application comes in the form of a Web Application Archive (a WAR file) named ManagementConsole.war and is located inside the /WebApps folder in the Kapow Katalyst installation folder.

The version of ManagementConsole.war that ships with Kapow Katalyst is configured to run embedded inside RoboServer, before you can deploy it as a standalone application on Tomcat it must be reconfigured to fit your environment.

A WAR-file is compressed using zip, in order to access the configuration files you will have to explode (unpack) it. Once the configuration files are updated you re-zip and deploy ManagementConsole.war to you Tomcat server.

The table below contains a list of the configuration files relative to the root of the un-zipped ManagementConsole.war

File

Configures

Notes

WEB-INF/Configuration.xml

Clustering, password encryption, REST-Plugin

If you copy the version of the file from 8.1, it will automatically be upgraded once you start the Management Console

WEB-INF/login.xml

Administrators and users, this is where you integrate with LDAP

WEB-INF/classes/log4j.properties

application logging

Configuration files


Spring configuration files

Configuration.xml and login.xml are all Spring configuration files (www.springsource.org) and share the same general syntax which we will outline here.

Spring is configured through a series of beans, each bean has a number of properties which configures a piece of code inside the application. The general syntax is:

    <bean id="id" class="SomeClass">
        <property name="myName" value="myValue"/>
    </bean>

part

Configures

id="id"

The id of the bean is an internal handle, that the application use to refer to the bean. It is also referred to as the beans name

class="SomeClass"

The class identifies the code component which the bean configures.

<property name="myName" value="myValue"/>

Defines a property with the name myName and the value myValue. This configures a property on the code component defined by the class attribute

Part


In Kapow Katalyst versions prior to 9.3, user access credentials were defined manually in the login.xml file. Starting from version 9.3, user management is performed using the Users & Groups tab under the Admin tab in the Management Console. In the enterprise version of Kapow Katalyst, user management is enabled by default. See the Users Tab topic for more details. User population from previous installations can be performed using the Kapow backup functionality. For LDAP integration you still need to edit the login.xml file.

Troubleshooting

If you have any problems during the installation, you should check the Tomcat log in the /logs folder in your Tomcat installation. During the configuration process it is often easier to run Tomcat from the command line, as it will then print error messages directly in the command line window.