Changes between Version 29 and Version 30 of orca-introduction

Show
Ignore:
Timestamp:
04/23/11 12:20:23 (8 years ago)
Author:
ibaldin (IP: 70.10.231.201)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • orca-introduction

    v29 v30  
    7171Configuring ORCA requires creating a container.properties file which defines the basic properties of the entire container and an XML file which contains the configuration for the actors that will run inside this container. The container.properties file is read at webapp startup (either when the webapp is deployed into Tomcat engine, or when the Tomcat engine is restarted) and therefore can be modified at any time without affecting other parts of ORCA. The actor configuration XML file must be included into the [http://en.wikipedia.org/wiki/WAR_file_format_(Sun) webapp WAR file] and therefore any time this file is changed, the ORCA war file must be repackaged and the webapp must be redeployed to take effect. 
    7272 
     73The actor configuration XML file defines the actors in a given container (their types, properties and plugins used by them; for authority actors it defines what resources are available to this actor and how to control them via handlers). It also defines how actors in this container communicate between each other and actors in other containers (i.e. ''actor topology'') 
     74 
     75A 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 unnecessary. 
     76 
    7377== Further reading == 
    7478