Changes between Version 44 and Version 45 of orca-introduction

Show
Ignore:
Timestamp:
05/09/11 15:09:36 (8 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • orca-introduction

    v44 v45  
    8181The container.properties file is stored outside the webapp and is read at webapp startup (either when the webapp is deployed into a running Tomcat engine, or when the Tomcat engine is restarted) and therefore can be modified at any time without affecting other parts of ORCA.  
    8282 
    83 A [source:orca/trunk/webapp/actor_configs/config.xml default actor configuration XML file] is included with the binary distribution of the webbapp and the source code. This file starts a single-container emulation of three basic ORCA actors - an authority, a broker and a service manager. Emulation refers to the fact that ORCA does not operate on real substrate and only goes through the motions of managing reservations. An alternative configuration XML file can be created and placed outside of ORCA, in which case the default file will be ignored. Also, if you are rebuilding ORCA from source, you can package it with your own version of the actor configuration XML file. 
     83A [source:orca/trunk/webapp/actor_configs/config.xml default actor configuration XML file] is included with the binary distribution of the webbapp and the source code. This file starts a single-container emulation of three basic ORCA actors - an authority, a broker and a service manager. Emulation refers to the fact that ORCA does not operate on real substrate and only goes through the motions of managing reservations. An alternative configuration XML file can be created and placed outside of ORCA, in which case the default file will be ignored. Also, if you are rebuilding ORCA from source, you can package it with your own version of the actor configuration XML file into the WAR file.  
    8484 
    8585A relatively new feature of ORCA is an [http://geni.renci.org:11080/registry/actors.jsp ORCA actor registry] - a separate component that is run as a service for all ORCA users. If desired actors in any container can register with this registry and thus automatically become visible to all other publicly available actors. This feature allows for a much simpler configuration process, especially the actor topology part. In many cases using the ORCA Actor Registry makes the actor topology definition in the actor configuration XML file unnecessary.