Konakart

Once you have java (at least java 8) installed and a database (either pre-loaded with all the necessary tables etc or ready to be loaded), you are ready to install KonaKart itself. To do this, download an installation kit, compatible with your chosen platform, and follow the installation instructions below for your platform : Note that if the GUI or silent installers do not work on your platform you should download the zip version of KonaKart and follow the manual installation instructions. Installing KonaKart on Windows Run the set-up program that executes a graphical installation wizard - see Graphical Installation Wizard below. (You can use the "Silent Mode" installation if you prefer, but the graphical version is probably easier if you're installing for the first time). Installing KonaKart on Unix/Linux Create a terminal session on your machine and enter the following: (You may prefer to use commands to do the same thing from your X-desktop if you have one installed). $# (replace 2.2.6.0 with the version you have downloaded)$ chmod +x KonaKart-2.2.6.0-Linux-Install $ ./KonaKart-2.2.6.0-Linux-Install If you have a graphical environment on your Linux/Unix machine you will be able to run the GUI. In which case see the Graphical Installation Wizard below (identical steps to the Windows installation). If you don't have a graphical environment you will see this warning message: $ ./KonaKart-2.1.0.0-Linux-InstallThis program must be run in a graphical environmentor in silent, unattended mode (with the -S option).Silent Mode Installations When running in "silent" (-S) (or "unattended") mode you are able to specify configuration parameters on the command line, for example: $ ./KonaKart-9.2.0.0-Linux-Install -S \ -DDatabaseType mysql \ -DDatabaseDriver com.mysql.jdbc.Driver \ -DDatabaseUrl jdbc:mysql://localhost:3306/mykkdb \ -DDatabaseUsername kkdbusr \ -DDatabasePassword ikk8271 \ -DLoadDB 1 \ -DJavaJRE "/usr/lib/jvm/java-8-openjdk-amd64/" Ensure that $HOME is defined before running the silent installer. Silent Mode Parameters The following parameters can be added to the command line, as in the example above, to specify default values for KonaKart at installation time: Parameter Default Value Explanation DatabaseType mysql mysql, postgresql, db2net, oracle, mssql DatabaseUrl jdbc:mysql://localhost:3306/dbname?zeroDateTimeBehavior=convertToNull&useSSL=false (on one line) for MySql 5.7 and 8.0 use jdbc:mysql://localhost:3306/dbname?useUnicode=true&characterEncoding=utf-8&useSSL=false (on one line) Database URL DatabaseUsername root Database User's Username DatabasePassword Database User's Password DatabaseDriver com.mysql.jdbc.Driver for MySql 5.7 and 8.0 use com.mysql.cj.jdbc.Driver Database Driver mssqlDBO dbo Database Owner (only used by MS SQL Server) InstallationDir Windows: C:\KonaKart *nix (as root): /usr/local *nix (as user): ~/konakart Installation Directory LoadDB 0 1=Load DB 0=Do not Load DB JavaJRE The Java runtime location PortNumber 8780 KonaKart Port Number HTTPSPortNumber 8783 KonaKart HTTPS Port Number SMTPServer ENTER_YOUR_SMTP_SERVER_HERE SMTP Server SMTPPort 25 SMTP Server Port SMTPSecure false SMTP Server requires authentication? SMTPStartTLS false Enable STARTTLS for SMTP email SMTPUser user@yourdomain.com SMTP Server Username SMTPPassword SMTP Server password sqlEncoding utf-8 Encoding for files addToClasspath Custom classpath entry Note: the value specified for addToClasspath will be added to the installer's classpath (after a classpath separator suitable for the platform) so that it is made available when the installer executes java utilities during the installation process. This can be very handy for

For the first time but this is probably not what you want to do if you already have a KonaKart database with a product catalog loaded for your store. If you do not check the 'Create the tables..' box then click next you would jump to the final page of the wizard. Alternatively, if you do check the 'Create the tables...' box then click next, you will be presented with a screen that shows the loading of the database initialisation script in a scolling window which will look like this: In the above example the script ran successfully (see last comment "SQL executed successfully" in the scrollable text area). If the script does not run successfully you will see the error message in this window. After clicking next you reach the following screen: Finally you are congratulated on a successful installation on the final screen of the wizard: Finally you have the option to create a desktop icon (which is defined to start the KonaKart server and launch the GUI) and launch the application immediately after the installation has completed. The "Launch KonaKart" option executes a startup of the KonaKart server and then launches the default browser to show the KonaKart UI, and the KonaKart Administration Application.

Skip to content We recognize that you want your on line store to be unique and stand out from the crowd, so KonaKart has been designed to be easy to customize to suit your particular business.Customizing the Store AppearanceCustomizing the appearance of the store is simple because all of the user interface source code is provided. We expect that you will want to customize the look of your store so KonaKart has been designed with this in mind. You can add your own logo and styles or completely change the look and feel of the store to make it look exactly the way you want. Since the store communicates with the KonaKart eCommerce engines through a stable set of APIs, your customizations continue to work as new versions of KonaKart are released.By way of example, here are three live customer sites that illustrate how much freedom you have to customise the look and feel of the storefront:Customizing the Store FunctionalityThere are a variety of techniques for customizing the behavior of the KonaKart engine functionality. Examples of the kinds of things you are able to do are:Add new payment and shipping modules. Many examples of these modules are included “out of the box” but KonaKart allows you to plug in new modules as you please, if, for example, you wish to interface to your own preferred payment gateway systemExecute your own code when certain events happen (e.g. when an order is made, you can execute your own code to send the order to another system). These “hooks” are designed to help you integrate your KonaKart store with other systems you might have such as your ERP or Warehousing systems.Enable Single Sign On by overriding KonaKart’s login checks. This allows a user to log in to many of your systems at once by just specifying one password – which leads to a much better user experience for your customers.Use customers defined in another system. Many companies will already have customers defined in an existing system. KonaKart can be customized to interface to this external data source instead of using customer information directly

Typing errors and will only allow you to proceed in the wizard when it validates the location successfully. Click on next to get to: This is where you define the port number that KonaKart will run on. Actually, KonaKart uses Apache Tomcat, so this is the port number that Tomcat is configured to run on. Whilst it is certainly possible to choose another port, it's advisable to accept the default which is 8780. KonaKart will not start up if another application is using the port you select, so make sure the port you select here is not currently being used. Clicking next moves you on to: This is your final chance to check your settings before copying the files into position. Clicking next will start the process of copying the KonaKart files into position as can be seen on the next screen: After about a minute or so the file copying will have completed and you are presented with this screen to choose the Database Type that you wish to use: Choose your preferred database type. You must set up the database yourself - this is not done as part of the installation (see database creation). Click next to continue to : It is very likely that you will have to modify values on this screen. You have to define the database connection parameters to KonaKart for the database that you created earlier (see database creation) KonaKart currently supports MySQL, PostgreSQL, Oracle, DB2 and MS SQL Server and includes all the JDBC driver jars required to access these. Note that you must append "?zeroDateTimeBehavior=convertToNull&useSSL=false" to your Database URL if you're using MySQL. Typically, for MySQL, you will need to change "dbname" in the default URL for the name of your own database schema. A good example for such a name might be "store1" or "konakart" but you are free to choose whatever name you like. After clicking next, the installer will check the database connection and report the results on the next screen as follows. For an unsuccessful connection you will see something like this: At this point you can go back and modify the database connection parameters and then click next to try the database connection test again. If successful you will see a screen like this: If the database connection fails, you can choose to click on next and finish the installation without executing the database initialisation. Normally, for a fresh install, you are advised to correct your database connection parameters so that you see a successful database connection message, then proceed to the database initialisation screen which looks like this: Note that the default is that the database initialisation is NOT executed. To execute it you must click on the checkbox and click next to reach the next step. Be warned that the database initialisation script will drop and re-create all the KonaKart tables and populate them with a default set of starting data. This default starting position is ideal for users who are setting up KonaKart

March 12, 2025, 04:43:01 pm Mobile Main Menu Home Search Sign Up KonaKart Community Forum ► Installation / Configuration ► Installation of KonaKart ► KKWebServiceEng?wsdl doesn't work in KonaKart 6.0.0 (works fine in 5.5.0.x) Started by PiotrN, February 08, 2012, 02:10:11 pm Previous topic - Next topic Print Go Down Pages1 User actions PiotrN Jr. Member Posts: 22 Location: Poland Logged KKWebServiceEng?wsdl doesn't work in KonaKart 6.0.0 (works fine in 5.5.0.x) February 08, 2012, 02:10:11 pm Howdy,I was trying to get access to KK 6 SOAP WS, but when I access this URL: localhost:8780/konakart/services/KKWebServiceEng?wsdl an exception is thrown and the following logs are produced in catalina.out: QuoteFeb 8, 2012 3:06:00 PM org.apache.coyote.AbstractProtocol startINFO: Starting ProtocolHandler ["http-bio-8780"]Feb 8, 2012 3:06:00 PM org.apache.coyote.AbstractProtocol startINFO: Starting ProtocolHandler ["http-nio-8783"]Feb 8, 2012 3:06:00 PM org.apache.coyote.AbstractProtocol startINFO: Starting ProtocolHandler ["ajp-bio-8789"]Feb 8, 2012 3:06:00 PM org.apache.catalina.startup.Catalina startINFO: Server startup in 6090 ms08-Feb 15:06:04 FATAL (InternalException.java::88) Exception:java.lang.Exception: Couldn't find a matching Java operation for WSDD operation "getConfigurationValue" (1 args) at org.apache.axis.InternalException.(InternalException.java:71) at org.apache.axis.description.JavaServiceDesc.loadServiceDescByIntrospection(JavaServiceDesc.java:902) at org.apache.axis.providers.java.JavaProvider.initServiceDesc(JavaProvider.java:477) at org.apache.axis.handlers.soap.SOAPService.getInitializedServiceDesc(SOAPService.java:286) at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:500) at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274) at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260) at org.apache.axis.deployment.wsdd.WSDDDeployment.getService(WSDDDeployment.java:427) at org.apache.axis.configuration.FileProvider.getService(FileProvider.java:231) at org.apache.axis.AxisEngine.getService(AxisEngine.java:311) at org.apache.axis.MessageContext.setTargetService(MessageContext.java:756) at org.apache.axis.handlers.http.URLMapper.invoke(URLMapper.java:50) at org.apache.axis.handlers.http.URLMapper.generateWSDL(URLMapper.java:58) at org.apache.axis.strategies.WSDLGenStrategy.visit(WSDLGenStrategy.java:33) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.generateWSDL(SimpleChain.java:104) at org.apache.axis.server.AxisServer.generateWSDL(AxisServer.java:446) at org.apache.axis.transport.http.QSWSDLHandler.invoke(QSWSDLHandler.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.axis.transport.http.AxisServlet.processQuery(AxisServlet.java:1226) at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:249) at javax.servlet.http.HttpServlet.service(HttpServlet.java:621) at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:964) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)When I run the KK 5.5.0 it works smoothly and the WSDL is properly generated. Any idea what might be the problem?Thanks in advance! ryan Administrator Hero Member Posts: 277 Logged Re: KKWebServiceEng?wsdl doesn't work in KonaKart 6.0.0 (works fine in 5.5.0.x) February 09, 2012, 08:02:38 am #1 Looks like you haven't enabled the SOAP web services . PiotrN Jr. Member Posts: 22 Location: Poland Logged Re: KKWebServiceEng?wsdl doesn't work in KonaKart 6.0.0 (works fine in 5.5.0.x) February 09, 2012, 08:26:18 am #2 Feel so damn awkward right now...Thanks Ryan and sorry for such stupid question ;-) User actions Print Go Up Pages1 KonaKart Community

KonaKart is completely multi-lingual both at the database level and at the UI level. Translating the KonaKart Application The data within the database such as product descriptions and category names etc. may exist in different languages. The database contains a languages table that contains information about each of the supported languages. When a new product is added to the database through the administration tool, it is possible to enter a description in multiple languages. Languages in the database have an attribute (specifically a column called display_only that indicates whether the language is only used for display purposes and not for product descriptions (and other KonaKart objects that have different variants for each data type). By default when you install KonaKart every language that is defined in the database has this display_only attribute set to 0 (false) which means that all KonaKart objects that require a variant for each language must have a value defined for each language. If you wish to introduce a language for use with the Admin App but not be required to add KonaKart object definitions for the language you can check the Display Only checkbox for the language (this can be found on the Languages Panel of the Admin App). You will have to provide a message catalog file for the new language and name the file in the appropriate fashion for the chosen locale. With KonaKart you can either store the application messages in message catalog files on disk or in the database. The default is to use message catalog files but from the v5.2.0.0 release it became possible to use the database to store these messages. Some users prefer to manage the messages in the database whereas others prefer files. The choice is yours! A configuration parameter called "USE_DB_FOR_MESSAGES" is used by the system to determine whether the messages are stored in the database or in files. You can set this value in the Admin Application under Configuration >> Admin App Configuration. The label used in English for this field is "Use D/B For Messages" and it can have a value of "true" or "false". When the messages (the storefront Application messages, the Admin Application messages and the Admin Application Help messages) are stored in the database you should use the Messages panel of the Admin Application to maintain the messages. Note that when editing the messages using the Messages Panel of the Admin Application you can click on the "Switch Editor" icon (to the right of the "Locale" field) to switch between the Rich Text Editor and the Plain Text Editor. This is sometimes useful to gain greater control over the HTML that is saved (the HTML that is created by the Rich Text Editor can be slightly different depending on which browser you use). When the messages are stored in message catalog files, there is a message catalog for each language. These can be found in the webapps/konakart/WEB-INF/classes directory of the application server. The default message catalog is called Messages.properties and is