Messages

sounds to me that there is some kind of problem connecting to your database from the installer.   You could try to investigate what's wrong by writing a tiny jdbc program to see if you can get any clues as to why java cannot connect to your mysql db (and create tables) using those credentials.

you should not have to run that script manually - the silent installer should do that.

we install hundreds of times per day using the silent installer to 5 different databases - including mysql.

I can't say... the fact that it tells you the DB connection test failed should give you a clue.

Is it blocked by a firewall perhaps?  Does the user have sufficient privileges?

Have you tried writing a tiny JDBC program to see if a java program can connect to the DB in that environment using those credentials?

I didn't say the GUI installer.... although that is easier if you can use it....  the silent mode command line installer sets up the properties files in the same way as the GUI installer.    Refer to the User Guide for details.

I'm just warning against using the zip installations unless you really have no choice.

if you use the installer you wouldn't get any of these problems since at installation time the DB connection is tested and all the necessary properties are automatically set in all properties files.

have you checked the properties files in the other webapps?  konakartadmin.properties for example.

I've never actually tried it but you should be able to use an external ActiveMQ (just fill out the attributes of the MqOptionsIf object appropriately).

Another option is to configure a topology whereby you have a KonaKart ActiveMQ that links to your other queue.   In some ways this could be beneficial in that it is more likely that messages from KonaKart can be successfully posted to a queue that KonaKart initialises than one controlled elsewhere.    You have to consider what happens if KonaKart (or your custom code) posts to the external queue when it isn't available.   (The same is true for posting to the KonaKart queue but it is probably a lot less likely to be unavailable if KonaKart is up and running).

There are no plans to move any features from the Enterprise version to the Community Edition.

The Community Edition provides enough to get a complete store up and running but the Enterprise Edition has far more features:

http://www.konakart.com/product/community-or-enterprise

It's important that the Enterprise customers get significantly more for their money.

As I said, have you looked in the logs for problems?

What's in your localhost log?

It's usually a file like this:

logs/localhost.2014-02-26.log




If you use kkant we know we will be using a compatible KonaKart ANT, if you just use ant it will use whatever version of ANT you have set up in your environment which may not be compatible.

I don't actually know why you want to run the Admin App in Eclipse.
Normally people are more interested in customising the storefront in Eclipse.

You need to check your tomcat start-up.

Have you looked in the logs for problems?

Could you please help how to have tomcat have access to the Internet?

That's something you have to resolve in your own network infrastructure.  I can't help you with that.


It's best not to ask so many questions in one post.  It becomes unmanageable very quickly.  I suggest you focus on one step at a time and get that right before moving on.


Your points 4 and 5 sound correct.

The problem is you don't say what went wrong so no-one can help you.

You don't make it easy for anyone to help you since you don't explain exactly what you did or exactly what went wrong.. eg. what exceptions you saw in your logs etc.

Taking point 2, you said that you couldn't access http://localhost:8780/konakart ?   What did you see in your tomcat log?  What was the error in your browser?

Does your tomcat have access to the Internet?  It needs it.


When making EARs you need to ensure you add the appropriate options to your ANT build commands.  For example, for JBoss, you should use:

In your /custom directory:

Code Select Expand

./bin/kkant make_ear -Djboss=true

Check the examples and the user guide for best practices.

You should never create a KKWSAdminIfService

Only create the engine proxies like KKAdmin (POJO) KKWSAdmin (SOAP) etc.

Focus on programming against the two main interfaces :  KKAdminIf for the Admin engine and KKEngIf for the storefront server engine.

KKWSAdmin is a proxy that implements the KKAdminIf and uses SOAP for the communication.   It handles all the details of the SOAP communication for you... hence you just have to focus on the KKAdminIf interfaces to use it.    The beauty is that you can switch to a different implementation of the proxy extremely easily (even at runtime)...  without changing any of your code, to change from SOAP to POJO, to RMI etc...


This is the recommended higher-level version (in this case for the KKEngIf but the technique is the same for KKAdminIf engine proxies):

Code Select Expand


EngineConfigIf engConfig = new EngineConfig();
engConfig.setMode(EngineConfig.MODE_SINGLE_STORE);
           
KKEngIf engine = new KKWSEng(engConfig);

// make some example calls

CountryIf[] countries = engine.getAllCountries();
System.out.println("There are " + countries.length + " countries");

ManufacturerIf[] manufacturers = engine.getAllManufacturers();
System.out.println("There are " + manufacturers.length + " manufacturers");

CurrencyIf curr = engine.getDefaultCurrency();
System.out.println("The default currency is: " + curr.getCode());

You have to modify the OrderIntegrationMgr to actually post messages to the queue:

            // Post the order to the order message queue for processing by some other system
            // postOrderToQueue(order);

You'll find it's commented out by default as not everyone will want this.

You cna find the source for this here:
"*\KonaKart\custom\appn\src\com\konakart\bl\OrderIntegrationMgr.java"

What is the exception that it refers to in your tomcat log?

You should probably set some logging in Liferay to see why your portlets aren't being deployed successfully.

One thing I would try first is to eliminate AXIS from the portlets by adding -DnoAXIS=true

You should be OK on those versions.   I agree it can be frustrating as the error reporting from Liferay when portlets don't deploy correctly isn't at all helpful.

Invariably the problems are to do with incompatible jars.  However, it's not always easy to figure out which are incompatible with each version and app server type.

Don't instantiate KKWSAdminIfService()

That's not the recommended way to work with the KonaKart SOAP engine.

You should instead instantiate KKWSAdmin by providing an AdminEngineConfig object in the constructor.

Once you've got your engine stub you would simply call the methods on the KKAdminIf interface (that KKWSAdmin implements).

This is the way to work with all of the KonaKart engines (KKEngIf and KKAdminIf).

The idea is that you could instantiate different implementations of KKAdminIf to use SOAP, JSON (KKEngIf only), RMI or POJO just by changing which engine is instantiated.  The engine could be specified in a property and you could use this to instantiate the engine stub by name, to make the change at runtime a configuration option.