Building ORCA 4.x from source

This assumes your environment satisfies the software prerequisites. Note that unlike the previous versions of ORCA, ORCA 4.x does not require a separately configured Tomcat container to run. Instead it uses an embedded Jetty container.

  1. export ORCA_SRC=/where/you/want/orca/source/code/to/be
  2. Retrieve the source tree in its entirety (specific tagged release or trunk)
    $ svn co https://geni-orca.renci.org/svn/orca/tags/<substitute release name>/ $ORCA_SRC
    

or for trunk

 svn co https://geni-orca.renci.org/svn/orca/trunk/ $ORCA_SRC
  1. Build the source
    $ mvn clean install -DskipTests=true
    
  2. Build the ORCA core. ORCA is built in two ways - as an application that can be started on the command line and as a daemon. For testing the application is built under $ORCA_SRC/server/orca/[bin|repo] and can be executed from there assuming you set $ORCA_HOME=$ORCA_SRC/server/orca. Daemon is built under target/generated-resources/appassembler/jsw/orcad. You can move the constructed tar files from target/ (orca.tgz, orca-startup.tgz and orcad.tgz) to a new host. NOTE: you only need one orca.tgz or orcad.tgz, but you always need orca-startup.tgz.
    $ cd server
    $ mvn clean package
    $ ant package
    
  3. Build the XMLRPC controller. Similar to ORCA code, the resulting executables are provided as a command line application and a daemon. The command line application is built under $ORCA_SRC/controller/xmlrpc/xmlrpc/[bin|repo] and can be executed from there for testing. Daemon is built under target/generated-resources/appassembler/jsw/xmlrpcd. You can move the constructed tar files from target/ (xmlrpc.tgz and xmlrpcd.tgz) to a new host. NOTE: you only need one xmlrpc.tgz or xmlrpcd.tgz.
    $ cd $ORCA_SRC
    $ cd controllers/xmlrpc
    $ mvn clean package
    $ ant package