Version 4 (modified by ibaldin, 6 years ago)



Setting up $ORCA_CONTROLLER_HOME generally follows the same philosophy as $ORCA_HOME. The difference is that the controller is not an ORCA actor, but rather a remote policy that connects to the SM actor (only to the SM actor!). Therefore, the controller must be configured to connect to an SM actor.

Note that the file has been replaced with The structure of the file is largely the same as before with a few additional properties related to running the controller as a standalone application.


$ export ORCA_CONTROLLER_HOME=/opt/orca-controller

Create a default configuration

It is easiest to check out the sample configuration from SVN and then customize it:



  • orca.manage.url points to the URL of the Jetty container running the SM with which this controller associates
  • orca.manage.[user, password] are the login and password of the admin user on the SM configured in
  • is the GUID of the SM actor to which this controller connects (defined in $ORCA_HOME/config/config.xml)
  • logging properties should be left unmodified
  • the controller now requires two .jks files:
    • geni-trusted.jks truststore which contains the trust roots for this controller to authenticate users - this affects which users are allowed to connect
    • xmlrpc.jks keystore which contains the private key and certificate of the controller when it acts as SSL server - this should be generated for each new installation