Version 6 (modified by ibaldin, 8 years ago)




ORCA Config files and directory structure


Once you decide which host ORCA container will run on, you can begin configuring ORCA on it. All of ORCA-specific configuration is contained under $ORCA_HOME directory (typically /opt/orca), which must be declared in Tomcat start/stop scripts.

Set $ORCA_HOME. Change ownership of this directory to the user on whose behalf the euca site authority is going to run. 'geni-orca' is the user and 'nonrenci' is the group in this example. The user and group are presumed to exist.

$ export ORCA_HOME=/opt/orca 
$ mkdir -p $ORCA_HOME 
$ chown -R geni-orca:nonrenci .

Create config/ and runtime/ directories for storing container configuration, actor configuration and Axis2 credentials:

$ cd $ORCA_HOME; mkdir runtime config 

Populate directories


An example of '' for a container can be found here. Download it and name it $ORCA_HOME/config/ Modify this file to tailor to your installation:

  • Change 'protocols.soapaxis2.url' to point to this host and proper port (usually 11080)
  • Generate and change 'container.guid'. You can use 'uuidgen' program that ships with many Linux distros and Mac OS X.
  • Optionally, if you want to make the actors in the container talk to the RENCI Actor Registry, follow instructions for configuring with registry.
    • From Camano 3.0+, this is the recommended way to interconnect actors within and between containers.


This file contains the definitions of ORCA actors placed in this container. The contents is heavily dependent on your deployment type. Please refer to top-level documentation for more information.


Generate guids and keys for each actor you wish to place in this container and copy the contents of $ORCA_SRC/tools/cmdline/runtime to $ORCA_HOME/runtime: