Adito notes

• create a webapp (my-adito)
• cd to it (cd /var/hda/web-apps/my-adito/
• chmod -R 777 .
• wget http://superb-east.dl.sourceforge.net/sourceforge/adito/adito-0.9.1-bin.tar.gz
• tar -xjf adito-0.9.1-bin.tar.gz
• mv adito-0.9.1/ server/
• cd into server
• cp conf/wrapper.conf.base conf/wrapper.conf
• copy a valid, pre-configured database set of files to the db/ dir
• chmod 777 install/platforms/linux/x86-64/wrapper
• ./install/platforms/linux/x86-64/wrapper /var/hda/web-apps/myadito/server/conf/wrapper.conf wrapper.pidfile=my.pid wrapper.daemonize=FALSE

---

Summary of Manual Install

• Concept: Adito requires Apache Ant to install and root access. The intent is to find a way to patch the source and do everything at the user level. In order to make this a one-click install, the patch would include predefined admin and links pertinent to the Amahi HDA.

• I did an actual install on a VirtualBox F10 32-bit VM with Amahi. As root, I did an install, activated the service, and logged in once to ensure everything worked (see http://wiki.amahi.org/index.php/adito). Once finished, stopped the service and compared the install version with the original source version. Files that were different are listed below:

server/conf: default.keystore.jks
server/conf/prefs/system/extensions: prefs.properties
server/conf/prefs/system/extensions/versions: prefs.properties
server/conf/prefs/system: prefs.properties
server/conf/repository/keystore: default.keystore.jks
server/conf/repository/PKI: aditoadmin.prv
server/conf/repository/PKI: aditoadmin.pub
server/conf: webserver.properties
server/conf: wrapper.conf
server/db: explorer_configuration.backup
server/db: explorer_configuration.data
server/db: explorer_configuration.log
server/db: explorer_configuration.properties
server/db: explorer_configuration.script
server/db: upgrade.log
server/db: versions.log
server/lib: tools.jar
server/logs: 2009_06_15.request.log
server/logs: adito.log
server/logs: wrapper.log
server/tmp: availableCipherSuites.txt
server/tmp: extensions (this is a directory of files)
server/tmp: org  (this is a directory of files)

• I then made a patch with the different files and started a clean VM. I followed the steps below to do the install without Apache Ant, but still using root access:

yum -y install java-1.6.0-openjdk-devel
cd /var/hda/web-apps/
mkdir myadito
cd myadito
wget http://superb-west.dl.sourceforge.net/sourceforge/adito/adito-0.9.1-bin.tar.gz 
tar -xf adito-0.9.1-bin.tar.gz
rm -f adito-0.9.1-bin.tar.gz
mv adito-0.9.1/ server/
cd server
wget adito-0.9.1-patch.zip (this is an archive of changed files between source and install)
wget adito-0.9.1-patch.zip
unzip adito-0.9.1-patch.zip
rm -f adito-0.9.1-patch.zip
chmod a+x /var/hda/web-apps/myadito/server/install/platforms/linux/adito
chmod a+x /var/hda/web-apps/myadito/server/install/platforms/linux/x86/wrapper
chmod a+x /var/hda/web-apps/myadito/server/install/platforms/linux/x86-64/wrapper
export WRAPPER_CONF="/var/hda/web-apps/myadito/server/conf/wrapper.conf"
/var/hda/web-apps/myadito/server/install/platforms/linux/adito start

Once it started, I used FF and went to https://localhost. The service only runs for about 10 sec, then shuts down, so have to be quick. Once I got the 'secure connection failed', I chose 'add exception.' I then did 'get certificate' and the 'confirm exception' button was greyed out. There was no certificate info available and I could not proceed. By this time, the service had also shut down.

I do not know why it shuts down, but it could be related to the certificate problem. There is guidance on the Adito wiki (http://adito.wiki.sourceforge.net/ssl_certificate_management) which provides some direction on manually creating a certificate.