Aeolus: How to get started

From Pmgwiki

Revision as of 22:28, 30 September 2011

Directions for checking out and running code

1. Prerequisites
   • MySql database
     • Install the rpms or packages (mysql, mysql-server, mysql-devel (may not need all these))
     • Start the server (/etc/rc.d/init.d/mysqld start)
     • chkconfig on for the server (to restart on reboot)
     • set passwords appropriately (probably need -p in the second one)
   • Postgres database
     • Install the rpms or packages (postgresql, postgresql-server, postgresql-jdbc)
     • service postgresql initdb (or run initdb somehow else)
     • chkconfig postgresql on
     • (the following is adapted from aeolus/auditing/graphdb/SQLEventStore.java)
     • sudo -u postgres createuser --superuser YOUR_UNIX_USERNAME
     • createdb AeolusAuthority
     • edit pg_hba.conf and change 127.0.0.1 entry to "trust" (fedora)
     • restart postgres server /etc/rc.d/init.d/postgresql restart
   • java 1.6
   • ant
2. Check out code
   • svn co svn+ssh://<Your-Name-Here>@lirone.csail.mit.edu/space/svnroot/aeolus aeolus
     
   • alternatively use eclipse to check out the sources from the repo
3. Build code
   • use eclipse to browse to build.xml
   • right click on build.xml and then choose Ant Build from the menu
     
   • Alternatively run "ant" in the aeolus directory (uses build.xml)
4. Create environment
   • Create databases (once)
     • AUTHORITY SERVER (per authority/server/AuthorityManager.java)
       • CREATE DATABASE AeolusAuthority;
       • CONNECT AeolusAuthority;
       • GRANT ALL ON * TO 'aeolus'@'localhost' IDENTIFIED BY 'PFlate762!';
     • AUDITING (per auditing/MySQLPersistentLogging.java)
       • CREATE DATABASE AeolusLogging;
       • CONNECT AeolusLogging;
       • GRANT ALL ON * TO 'aeolusLogger'@'localhost' IDENTIFIED BY 'PFlate762!';
   • Start authority server and audit server
     • cd ~/workspace/aeolus/dist
       ./aeolus-server.jar &
5. Run code
   • java -cp ~/workspace/aeolus/aeolus/dist/aeolus-rt.jar:~/workspace/aeolus/aeolus/../lib/bcel-5.2.jar edu.mit.csail.aeolus.runtime.RuntimeLoader ~/workspace/aeolus/aeolus/dist/aeolus-apps.jar edu.mit.csail.aeolus.apps.testapps.HelloWorld
     
   • Note: aeolus-apps.jar contains all the classes in apps (or at least approximately)
   • Note: need to add aeolus-apps.jar to the class path if using shared state
   • Alternatively, cd to the dist directory and type
     java -cp aeolus-rt.jar:../lib/bcel-5.2.jar edu.mit.csail.aeolus.runtime.RuntimeLoader /home/user-name/workspace/aeolus/dist/aeolus-apps.jar edu.mit.csail.aeolus.apps.testapps.HelloWorld
     
   • Note: the Aeolus class loader (RuntimeLoader in above command) always needs a full, absolute pathname
   • For performance measurements bypass the aeolus class loader
     java -jar aeolus-rt.jar aeolus-rt.jar edu.mit.csail.aeolus.apps.testapps.RuntimeBenchmark
   • For completeness, here are the other two commands to collect performance numbers:
     • RPC: java -Xmx3G -cp aeolus-rt.jar:aeolus-apps.jar;../lib/bcel-5.2.jar edu.mit.csail.aeolus.runtime.RuntimeLoader ~/aeolus/dist/aeolus-apps.jar edu.mit.csail.aeolus.testing.MyApplication
     • Monster: java -Xmx3G -cp aeolus-rt.jar:../lib/bcel-5.2.jar edu.mit.csail.aeolus.runtime.RuntimeLoader ~/aeolus/dist/aeolus-apps.jar edu.mit.csail.aeolus.apps.bnewmonster.MonsterServer