Package org.lsst.ccs.startup

Codes in this package are mostly mains for applications linked to subsystem startup.

See: Description

Class Summary

Class	Description
BootUtils	A collection of static utilities linked to boot operations.
BootUtils.LocalBootObject	Very important class: when an instance is created you can have : a descriptive Node the names of subsystem, configuration, tag the corresponding Effective Node a Subsystem ready to run (but not started)
CCSBuilder	for future uses: does nothing special right now build methods may be modified to insert some elements
LocalDescriptionToConfigurationText	Utility to create locally the configuration properties file.
LocalMergeToBinary	creates a new Binary description file by merging a description file and a configuration properties file
LocalTextToBinary	Utility code to locally transform a description text file to a binary one.
MainDescriptiveNode	A DescriptiveNode containing the name of the subsystem.
NodeLookup
NodeModularSubsystem	the top modular subsystem that deals with configuration proxy and lookup service
SubsystemBoot
SubsystemBootFromBus	Starts a subsystem by requiring data from the network.
SubsystemBootFromStream	Boots a subsystem from a local resource.

Package org.lsst.ccs.startup Description

Codes in this package are mostly mains for applications linked to subsystem startup.

• SubsystemBootFromStream enables to start locally a subsystem from a resource file that describes a subsystem (and possibly a subsystem modified by configuration data.
  Possible file formats are :
  • XML/spring : this format will later be no longer supported
  • a ".ser" file containing a Serialized ComponentNode object. This object is used to describe and starts a subsystem. The file may have been generated by compiled java code, a groovy script, or a merge between a previous description file and a configuration file.
  • a Groovy script (A specific DSL in a ".groovy" or ".groo" file)
• SubsystemBootFromBus enables to start a subsystem when a Configuration service is available on the network. It can request data for a specific subsystem or just start and wait for a command when a link is established between the local MacAddress and a Configuration.
• LocalTextToBinary generates a local ".ser" resource from a groovy text file (xml is not supported)
• LocalDescriptionToConfigurationText generates a ".properties" template file to be edited to configure a subsystem
• LocalMergeToBinary combines a local description and a local configuration into a local ".ser" file to be executed.