The Talon Manual

Versions Compared

Old Version 82

changes.mady.by.user Unknown User (colin)

Saved on

compared with

New Version 83

changes.mady.by.user Unknown User (colin)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Minor formatting changes

...

  • <systemDetails>: Defines system metadata that is used by tools and emitted by an XVM in heartbeats. 
  • <env>: Defines environment variables that can be used for substitution of values in the document and are exposed to the application and talon runtimes.
  • <busProviders>: Defines custom message bus provider implementations.
  • <buses>: Defines the message buses that are used for applications to communicate with one another.
  • <apps>: Defines and configures the applications that make up the system. 
  • <xvms>: Defines the XVMXVMs (Talon lightweight containers) that host one or more applications. 
  • <profiles>: Defines profiles that can be dynamically activated to localize the configuration for different operating environments.

...

  1. Apply DDL Profiles: Activated DDL <profiles> elements are merged into the main DDL XML. 
    DDL profiles provide a means of making a single DDL configuration document more portable to different environments, by the structure of configuration to be augmented and overridden.
  2. Apply DDL Templates: Apply <app>, <bus>, <xvm> templates. 
    Templates provide a means of reducing duplicate configuration across the above element types/. Template values may be supplied by profiles activated in step 1 above. 
  3. Apply DDL SDDL Substitutions and Overrides: ${varName::defaultValue} substitutions.
    Substitution values come from values in the environment or <env> elements in the DDL document itself. Substitution values can come from profiles or templates applied in steps 1 and/or 2 above. 

...