As part of this series I have been reviewing and creating Amazon Machine Images (AMI) of some of the open source data mining, business intelligence software out there.
Apart from some earlier issues with getting java installed it has been straight-forward.
Please check this articles for the background
http://blog.vmdatamine.com/2007/07/bizgres-greenplum-on-ec2.html
https://wiki.dbadojo.com/howto-install-bizgres-on-centos
http://blog.vmdatamine.com/2007/07/running-bizgres-demo.html
To run the Bizgres Clickstream demo you will need to download this tarball and use the Clickstream User Guide.
My only issue was the environment variables I had a Postgresql database specified and it caused the demo to fail during the test of the database. Under the hood it was using a similar test suite (IVP) as outlined in the article on the demo.
After that everything was good. I had to open up the 8080 port on EC2 for the security group the instance was running to be able to view the Jasper reports.
I will write another article about my thoughts after running through the demo and clickstream demo.
I have included some screen shots as well (edited to remove my Firefox bar)
Have Fun
Paul
Here is the .bash_profile and bizgres_path.sh I setup
[bgadmin@domU-12-31-35-00-1C-C1 bizgresClickStream]$ cat ~/.bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
unset USERNAME
# For Bizgres
# This is the installed location of the Bizgres binaries. For example:
BIZHOME=/usr/local/bizgres
export BIZHOME
# Bizgres is installed with a Java Development Kit (JDK) installation that is compatible with Bizgres.
JAVA_HOME=/usr/local/jdk1.5.0_12/
export JAVA_HOME
# The LD_LIBRARY_PATH environment variable should point to the location of the PostgreSQL library files.
# For Solaris, this also points to the GNU compiler and readline library files as well.
LD_LIBRARY_PATH=$BIZHOME/pgsql/lib:$BIZHOME/lib
export LD_LIBRARY_PATH
# The default port number of the Bizgres/PostgreSQL database server.
#PGPORT=5432
#export PGPORT
# The location of the PostgreSQL manual pages.
MANPATH=$BIZHOME/doc:$MANPATH
export MANPATH
# The name of the default Bizgres/PostgreSQL database to use.
#PGDATABASE=bizdb
#export PGDATABASE
PGPATH=$BIZHOME
export PGPATH
# The host name of the Bizgres/PostgreSQL database server that clients use to connect to the database.
#PGHOST=`hostname`
#export PGHOST
#PGUSER=bgadmin
#export PGUSER
# Your PATH environment variable should point to the location of your JDK bin directory (listed first),
# the location of the Bizgres Loader bin directory,
# and the location of the Bizgres database engine (PostgreSQL) bin directory.
PATH=$JAVA_HOME/bin:$BIZHOME/pgsql/bin:$BIZHOME/client/loader/bin:$PATH
#PATH=$PATH:$HOME/bin
export PATH
unset USERNAME
The bizgres_path.sh file
[bgadmin@domU-12-31-35-00-1C-C1 bizgresClickStream]$ cat /usr/local/bizgres/bizgres_path.sh
BIZHOME=/usr/local/bizgres
PATH=$BIZHOME/pgsql/bin:$BIZHOME/client/loader/bin:$PATH
LD_LIBRARY_PATH=$BIZHOME/lib
MANPATH=$BIZHOME/doc:$MANPATH
PGPATH=$BIZHOME
export BIZHOME
export PATH
export LD_LIBRARY_PATH
export MANPATH
export PGPATH
The screen dump of running make under the bizgresClickstream directory
[bgadmin@domU-12-31-35-00-1C-C1 bizgresClickStream]$ make
Tomcat package is complete, good.
bizgresClickStream package is complete, good.
Found sed, good.
Found gtar, good.
Found JDK version 1.5, good.
Port 8080 appears to be free, good.
Tomcat appears not to be running, good.
Port 5432 appears to be free, good.
Port 10000 appears to be free, good.
Bizgres is installed at /usr/local/bizgres, good.
Testing Bizgres installation...
Bizgres test passes, good
Installing Tomcat...
Using CATALINA_BASE: /usr/local/bizgres/demo/solutions/bizgresClickStream/tomcat
Using CATALINA_HOME: /usr/local/bizgres/demo/solutions/bizgresClickStream/tomcat
Using CATALINA_TMPDIR: /usr/local/bizgres/demo/solutions/bizgresClickStream/tomcat/temp
Using JRE_HOME: /usr/local/jdk1.5.0_12/
Waiting 5 secs for WAR deployment
Uncompressing database dump files...
done.
CREATE DATABASE
Starting...
nohup: appending output to `nohup.out'
Started.
KETL startup succeeded.
Bizgres clickstream installation complete. Please read the documentation for next steps.
Starting KETL and running the job to generate the reports
[bgadmin@domU-12-31-35-00-1C-C1 bizgresClickStream]$ cd bin
[bgadmin@domU-12-31-35-00-1C-C1 bin]$ source clicksenv.sh
[bgadmin@domU-12-31-35-00-1C-C1 bin]$ ketl_ctl
KETL Console - Version 0.9 beta release
->connect localhost
Connected to domU-12-31-35-00-1C-C1.z-2.compute-1.internal
->job RUN_REPORTS execute 1 multi ignoredependencies
RUN_REPORTS
Job submitted to server for direct execution.
->status jobs
Executing
---------
Failed
------
Just Failed
-----------
Ready To Run
------------
->quit
[bgadmin@domU-12-31-35-00-1C-C1 bin]$ ls $WEBAPP/jasper
CumulativeEntryPages.jasper DailyGeographicActivity.jrxml ReferrersByWeek.jrxml
CumulativeEntryPages.jrxml DailySiteActivity.jasper SearchEngineReferrersByWeek.jasper
CumulativeExitPages.jasper DailySiteActivity.jrxml SearchEngineReferrersByWeek.jrxml
CumulativeExitPages.jrxml DailyTopReferrers.jasper WeeklyEntryPages.jasper
CumulativeGeographicActivity.jasper DailyTopReferrers.jrxml WeeklyEntryPages.jrxml
CumulativeGeographicActivity.jrxml DailyTopSearchEngineReferrers.jasper WeeklyExitPages.jasper
CumulativeSiteActivity.jasper DailyTopSearchEngineReferrers.jrxml WeeklyExitPages.jrxml
CumulativeSiteActivity.jrxml DailyTrafficActivity.jasper WeeklyGeographicActivity.jasper
CumulativeTopReferrers.jasper DailyTrafficActivity.jrxml WeeklyGeographicActivity.jrxml
CumulativeTopReferrers.jrxml Daily_10_2004_11_18.html WeeklySiteActivity.jasper
CumulativeTrafficActivity.jasper Daily_13_2004_11_18.html WeeklySiteActivity.jrxml
CumulativeTrafficActivity.jrxml Daily_16_2004_11_18.html WeeklyTopReferrers.jasper
Cumulative_12.pdf Daily_19_2004_11_18.html WeeklyTopReferrers.jrxml
Cumulative_15.pdf Daily_1_2004_11_18.html WeeklyTopSearchEngineReferrers.jasper
Cumulative_18.pdf Daily_4_2004_11_18.html WeeklyTopSearchEngineReferrers.jrxml
Cumulative_21.pdf Daily_7_2004_11_18.html WeeklyTrafficActivity.jasper
Cumulative_3.pdf EntryPagesForWeek.jasper WeeklyTrafficActivity.jrxml
Cumulative_6.pdf EntryPagesForWeek.jrxml Weekly_11_2004_11_15.html
Cumulative_9.pdf ExitPagesForWeek.jasper Weekly_14_2004_11_15.html
DailyEntryPages.jasper ExitPagesForWeek.jrxml Weekly_17_2004_11_15.html
DailyEntryPages.jrxml GeographicByWeek.jasper Weekly_20_2004_11_15.html
DailyExitPages.jasper GeographicByWeek.jrxml Weekly_2_2004_11_15.html
DailyExitPages.jrxml README.txt Weekly_5_2004_11_15.html
DailyGeographicActivity.jasper ReferrersByWeek.jasper Weekly_8_2004_11_15.html
Make sure port 8080 is open
After I was finished, shutdown KETL and check the status
[bgadmin@domU-12-31-35-00-1C-C1 bin]$ ketl_ctl
KETL Console - Version 0.9 beta release
->connect localhost
Connected to domU-12-31-35-00-1C-C1.z-2.compute-1.internal
->shutdown
...
->status
KETL Cluster Status
Registered Servers: 2
Alive Servers : 0
Pending Jobs
Server : domU-12-31-35-00-1C-C1.z-2.compute-1.internal
Status : Shutdown
Start Time: 2007-07-20 08:01:06.234
Last Ping : 2007-07-20 08:16:59.446735
Executors (Stats)
SQL: (Total: 2)
KETL: (Total: 2)
XMLSESSIONIZER: (Total: 1)
OSJOB: (Total: 2)
No comments:
Post a Comment