Installing KonaKart on IBM's WebSphere Application Server

Verified on WebSphere 6.1 on Windows

Refer to the general notes for installing KonaKart on all Application Servers .

Usage Limitation: Reports with embedded charts produced using EMF 2.2 cannot be run in the default WebSphere 6.1 installation due to a conflict between versions of EMF (WebSphere 6.1 uses 2.1 whereas KonaKart/BIRT use EMF 2.2). If reports with embedded charts are important to you, you can either write new, compatible, reports using EMF 2.1 or modify the class-loading mode of the KonaKart application to parent last (as described in various reports on the subject on the Internet).

Note that the default download kit of KonaKart contains code compiled with a java 1.8 target therefore it will not work on WebSphere 6.0 which uses a 1.4 JRE.

Installation

Use the deployment method of choice. Loading using an EAR is probably the simplest by navigating to Enterprise Applications in the Administrative Console, "Install" application, browse to your EAR file, then proceed through the wizard accepting all the defaults.

Configuration

  1. If you are not using a Sun JRE for WebSphere, you will need to add two jars jsse.jar and jce.jar from your Sun JRE to support some SSL and mail functionality of KonaKart. Either package these in the WARs of konakart.war and konakartadmin.war, or place them in the lib directories of these applications once deployed.

  2. Set the port numbers (9080) for the reporting configuration variables as required (set these using the KonaKart Admin App under the Configuration > Reports section)

  3. Set the HTTP (9080) and HTTPS (9443) port numbers as required (set these using the KonaKart Admin App under the Configuration > HTTP/HTTPS section)

  4. Set the memory parameters to suit your environment. Use the WebSpehere Administrative Console to set the JVM parameters. Navigate to Server > Server Infrastructure > Java & Process Management > Process Defn then your values for Maximum Heap Size (eg. 1024) and Initial Heap Size (eg. 512). (You may need require different settings to suit your own environment).