Deployment Checklist

The following table contains a deployment checklist. You can print it by clicking the print icon on the toolbar.

Check

Item

Description / Notes

 

Download and install a supported version of Apache Tomcat Server

 

Download and install Java 7 (JDK 1.7.0_45 or later)

Management Console will not initialize correctly if Apache Tomcat is started using any version of Java other than Java 7.

 

Insure that the JAVA_HOME variable is pointed to the Java 7 installation.

 

Start up the Apache Tomcat and confirm that the Apache Tomcat server will come on-line before attempting to deploy the Management Console application.

  • You can use the catalina run command from the \bin directory to start the server.

  • Going to http://localhost:8080 in the browser should display the default Apache Tomcat start up page.

 

From a Kapow 9.3.x installation, locate the ManagementConsole.war file that will be deployed under the Apache Tomcat \webapps directory

Expect errors on the initial start up of the application at this point, because the server has not been configured yet. We are simply unpacking the .war file so that we can easily gain access to the files we will need to edit to complete the installation and configuration process.

 

Turn the Apache Tomcat server off.

 

Create a new database to be used by the Enterprise Management Console to hold its configuration.

  • Choose one of the support platforms

  • The on-line help contains the CREATE and DROP SQL Scripts needed to create all of the required DB tables. Note that these scripts only need to be used if the user account that the application will use to connect to the DB does not have CREATE privileges on the schema.

  • Choose an appropriate collation as suggested in the on-line help.

 

Create the DB user account to be used by the application to connect to the database via JDBC.

 

Create the Tomcat Context file: ManagementConsole.xml

  • Validation query to be specified is DB platform specific. The on-line help has all accepted values for all supported databases.

  • Do not forget to update the Username, Password, and DatabaseName parameters in the JDBC URL string with the correct values for your database.

 

Prior to starting up the application, notice that the Management Console database (the one specified in the ManagementConsole.xml) does not have any tables related to the Management Console process at this time.

  • When the application is started the needed DB tables will be automatically created if they are not present assuming that the DBUser account has CREATE privileges to the schema.

  • If the user does NOT have CREATE privileges, the CREATE SQL scripts can be downloaded from the help.kapowsoftware.com website.

 

Do not forget to deploy the necessary JDBC .jar file under the Apache Tomcat installation directory.

  • Deploying to <APACHE_TOMCAT_INSTALL_DIR>\lib makes it available to ALL apps running under Tomcat.

  • Deploying to <APACHE_TOMCAT_INSTALL_DIR>\webapps\ManagementConsole\WEB-INF\lib makes the JDBC .jar file only accessible to the Management Console application itself.

 

Restart the Apache Tomcat Server

Confirm the Tomcat main home page loads: http://localhost:8080

 

Try to login to the Enterprise Management Console as user - admin, password - admin

http://localhost:8080/ManagementConsole

 

Enter the Kapow Software License Keys

Deployment Checklist