Documentation for run.sh

I did get this working... Here is my run.sh

recommender directory is at ~/recommender...so its /home/xxx/recommender

Run.sh

# If you install the recommender module under 'sites/all/modules/recommeder' and 'sites/default/settings.php' is accessible, then you can run this script directly.
# Otherwise, please see README and make necessary configuration to make this script running correctly.

# config parameters whatever your drupal servers address is
export DRUPAL_HOME=192.168.0.90

ASYNC_COMMAND_HOME=~/recommender
RECOMMENDER_HOME=~/recommender
MAHOUT_HOME=~/recommender

# please make sure you have java and php installed.
command -v java >/dev/null || { echo "Cannot find java program. Please install Java first and make sure the executable is under PATH."; exit 1;}
command -v php >/dev/null || { echo "Cannot find php program. Please install PHP first and make sure the executable is under PATH."; exit 1;}

# set CLASSPATH
CLASSPATH=$RECOMMENDER_HOME/recommender.jar:$ASYNC_COMMAND_HOME/drupal-app.jar:$ASYNC_COMMAND_HOME/lib/*:$MAHOUT_HOME/*

# using the default config.properties file in the working directory, or fall back to use settings.php directly.
#java -cp $CLASSPATH org.drupal.project.recommender.RecommenderApp

# specify the location and filename of config.properties file. Default is the working directory
CONFIG_FILE=~/recommender/config.properties
java -cp $CLASSPATH org.drupal.project.recommender.RecommenderApp -c $CONFIG_FILE

config.properties

# This configuration file should follow the java .properties format. http://en.wikipedia.org/wiki/.properties

##### database configuration #####
# For a list of the database configuration parameters, please see http://commons.apache.org/dbcp/configuration.html

username=recommender
password=whatever

# could be mysql or postgresql
database_type=mysql
url=jdbc:mysql://192.168.0.90/whatever

##### Additional settings #####

drupal_version=7

# database prefix in Drupal
#db_prefix=

# mcrypt secret key. please specify if you use Encrypted Settings Field. Usually you can ignore it.
#mcrypt_secret_key=

# max database batch size for UPDATE/INSERT/DELETE. used in JDBC batchExecute()
#db_max_batch_size=5000

Thanks for the report. I'll try to make better documentation in the next version.
I'll consider this problem as "fixed", right? If the problem still persists, please re-open the issue again.

Automatically closed -- issue fixed for 2 weeks with no activity.