Deployment

kui is deployed as a web application in your application server or servlet container. Just drop the kui.war file where your other web applications are deployed, start your container and you're good to go. See the Configuration section below for configuration options.

Configuration

The only configuration option in kui is to specify a username and password which are as system properties by kui at startup; the parameter names are kui.username and kui.password. Many application servers allow you to set system properties in your server configuration or in some cases they can be specified via your startup command.

Here is a simple example using the Resin application server:

java -Dkui.username=username -Dkui.password=password -jar lib/resin.jar console

Logging

kui uses slf4j for logging and is packaged with the JDK14 implementation. This can be changed as needed by expanding the kui.war file and replacing the slf4j-jdk14.jar file with the slf4j implementation of your choice.

Requirements

kui requires Java 5 or higher and a supported container.

Supported Containers

kui has been tested with the following application servers and containers:

kui is known to have issues with the following application servers and containers:

• GlassFish 2.1.1
• Receive error java.lang.ClassNotFoundException: com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder when starting Glassfish. Still researching...
• JBoss Application Server 5.1.0.GA
• JBossAS 5.1.0.GA appears to use multiple MBeanServers which kui does not support. Will likely be supported in a future version.
• JOnAS 5.1.1
• Exceptions at startup related to the Spring framework. Still researching...

Supported Browsers

kui has been tested with the following web browsers: