Design Patterns for and Automation of Federation State Control
conference paper
The suitability of or choice for a particular design pattern for federation execution state control depends on several factors, such as the degree in which legacy applications can support particular patterns and the complexity of the federation. For small federations that involve only a handful of federates that execute at one location, it may be sufficient to use manual control of the applications and document all necessary procedures in a Federation Agreements document, whereas a complex federation executing on a wide area network can find many benefits in using automated execution state control.
Standardisation of design patterns for federation execution state control will promote re-use of federates in different federation configurations. And formalisation of these design patterns using available standards will enable a certain degree of automation of execution state control, independent of the federation.
This paper describes the functions of Federation Management, in particular execution state control, and provides an overview of a number of commonly found execution state control patterns. It introduces the W3C State Chart XML (SCXML) as state machine notation and demonstrates its use in the automation of federation execution state control using available open source software from the Apache Commons project.
Standardisation of design patterns for federation execution state control will promote re-use of federates in different federation configurations. And formalisation of these design patterns using available standards will enable a certain degree of automation of execution state control, independent of the federation.
This paper describes the functions of Federation Management, in particular execution state control, and provides an overview of a number of commonly found execution state control patterns. It introduces the W3C State Chart XML (SCXML) as state machine notation and demonstrates its use in the automation of federation execution state control using available open source software from the Apache Commons project.
TNO Identifier
28533
Publisher
Simulation Interoperability Standards Organization's (SISO)
Article nr.
09S-SIW-009
Source title
2009 Spring Simulation Interoperability Workshop (SIW), March 22-27, 2009, San Diego, CA, USA