KonaKart uses a number of properties files for configuration and by default these have the following names and locations (assuming KonaKart was installed on Linux under /home):
KonaKart engine server properties file:
/home/konakart/webapps/konakart/classes/konakart.properties
KonaKart Storefront Application client properties file:
/home/konakart/webapps/konakart/classes/konakart_app.properties
KonaKart Storefront engine JAXWS (SOAP) client properties file:
/home/konakart/webapps/konakart/classes/konakart_jaxws_client.properties
KonaKartAdmin engine server properties file:
/home/konakart/webapps/konakartadmin/classes/konakartadmin.properties
KonaKartAdmin Admin App Client properties file:
/home/konakart/webapps/konakartadmin/classes/konakartadmin_gwt.properties
KonaKartAdmin Admin engine JAXWS (SOAP) client properties file:
/home/konakart/webapps/konakartadmin/classes/konakartadmin_jaxws_client.properties
KonaKart engine Velocity properties file:
/home/konakart/webapps/konakart/classes/konakart_velocity.properties
KonaKart Admin engine Velocity properties file:
/home/konakart/webapps/konakartadmin/classes/konakart_velocity.properties
Using the above default properties file names is fine for most installations but if multiple versions of each are required there are ways to configure KonaKart in order to use properties files with different names and locations.
Some of the properties file names and locations can be specified as part of "EngineConfig" objects (EngineConfig for the Application Engine and AdminEngineConfig for the Admin Engine) which are specified as parameters when you create the respective engines.
If still more flexibility is required it is possible to override the properties file names and locations in a customizable java class called PropertyFileNames.java . PropertyFileNames.java is provided in every download kit and can be found under /home/konakart/custom/utils/com/konakart/util. PropertyFileNames.java has a simple structure and allows you to override any properties file by modifying the getFileName() method. getFileName() takes two parameters:
propertyFileCode : an integer code that identifies the particular properties file (eg. PropertyFileNames.KONAKARTADMIN_SERVER_PROPERTIES_FILE and PropertyFileNames.KONAKART_SERVER_PROPERTIES_FILE are two examples)
def : the default value. By default this is returned for every properties file type.
Having modified the code in the getFileName() method it can be built using the standard custom build. The updated PropertyFileNames.class will be placed in the konakart_custom_utils.jar by the standard build as illustrated below:
C:\KonaKart\custom>.\bin\kkant compile_utils, make_jar_custom_utils Buildfile: build.xml compile_utils: [echo] Compile the customisable utils code [javac] Compiling 2 source files to C:\KonaKart\custom\utils\classes make_jar_custom_utils: [echo] Create the konakart_custom_utils.jar [jar] Building jar: C:\KonaKart\custom\jar\konakart_custom_utils.jar BUILD SUCCESSFUL Total time: 1 second
Once built successfully the new konakart_custom_utils.jar should be copied to the lib directories of the konakart and konakartadmin webapps as required.