Added by Dennis Reedy, last edited by Dennis Reedy on Feb 27, 2009  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

The core service configuration is found in RIO_HOME/config. All Rio configuration is done with Groovy.

Transient (recommended) Configurations

Filename
Description
start-cybernode.groovy
Starts a Cybernode using the cybernode.groovy file
start-monitor.groovy Starts a Provision Monitor, a Lookup service using (respectively) monitor.groovy and reggie.groovy files
start-all.groovy Starts a Cybernode, Provision Monitor, a Lookup service using (respectively) cybernode.groovy, monitor.groovy and reggie.groovy files
cybernode.groovy The configuration for a Cybernode.
monitor.groovy The configuration for a Provision Monitor.
reggie.groovy The configuration for a lookup service.

Persistent Configurations

There are also configurations for starting persistent services. Persistent services are used if you want to store the state of a Cybernode or a Provision Monitor. A persistent Cybernode stores it's service statements (records of all services it has created). A persistent Provision Monitor retains the state of deployed OperationalStrings, including any changes made to those deployed opstrings.

Filename
Description
start-persistent-cybernode.groovy
Starts a persistent Cybernode using the cybernode.groovy and the persistent_cybernode.groovy files.
start-persistent-monitor.groovy Starts a persistent Provision Monitor, a persistent Lookup service using (respectively) monitor.groovy, persistent_monitor.groovy and reggie.groovy, persistent_reggie.groovy files. 
start-persistent-all.groovy Starts a persistent Cybernode, persistent Provision Monitor, a persistent Lookup service using (respectively)
persistent_cybernode.groovy The configuration for a Cybernode. The persistent_cybernode.groovy file extends the CybernodeConfig class in the cybernode.groovy file, overriding properties required for persistence.
persistent_monitor.groovy The configuration for a Provision Monitor. The persistent_monitor.groovy file extends the MonitorConfig class in the monitor.groovy file, overriding properties required for persistence.
persistent_reggie.groovy The configuration for a persistent lookup service. The persistent_reggie.groovy file extends the ReggieConfig class in the reggie.groovy file, overriding properties required for persistence.

Activation Configurations

These configurations are used to start the core services under the control of RMI Activation.

Filename
Description
start-activatable-cybernode.groovy
Starts a persistent activatable Cybernode using the cybernode.groovy and the persistent_cybernode.groovy files.
start-activatable-monitor.groovy Starts a persistent activatable Provision Monitor, a persistent activatable Lookup service using (respectively) monitor.groovy, persistent_monitor.groovy and reggie.groovy, persistent_reggie.groovy files.