Hi Devs, Before we proceed with the release we need to come-up with a structure for airavata distribution. Currently we have a distribution for ws-messenger because ws-messenger can be used separately without having any Xbaya, GFac functionality. There is a possibility that some users use ws-messenger as their messaging system for their system, so I believe when we release its reasonable to release ws-messenger distribution too. Currently ws-messenger distribution is pretty straight forward and users have to unzip the archive and start the axis2server.sh and can run the samples and try it out.
I think we need to provide similar distribution for complete airavata stack. My idea is to create distribution with the following functionality. 1. Airavata distribution will be a zip file which is having embedded axis2 container in it. 2. When user extract it and start airavata startup script it will deploy all the ws-messenger services and gfac services and start the jackrabbit instance too (embedded version of jackrabbit). 3. Then users can start the XBaya separately from another script and create a workflow in Xbaya and invoke the workflow. 4. Other than this setup we need to provide all the artifacts in a separate location with proper instructions of how to deploy all the services on tomcat with mysql server for ws-messenger and how to start Jackrabbit in server mode and consume the repository. 6. All the samples should work out of the box when user start the airavata-startup script and simply run ant run in all the samples (Every sample has to have a Readme.txt which explain what sample is demonstrating and how to run it). Note : Samples will not work if user try to run it by checking out the source code (directory locations might get change when creating the distribution). Please provide your ideas about airavata distribution. Regards Lahiru -- System Analyst Programmer PTI Lab Indiana University
