The Architecture Information Repository (AIR) is the facility within the Architected Futures™ framework that provides the
data store for the architecture knowledgebase. It is where the awareness of the architecture is stored. The representation and storage format for the knowledgebase has undergone multiple transformations over time as the concept of the framework has evolved. EATSv5 is a 2020 version implemented in Java using an Eclipse RCP e4 framework as a virtual machine environment to obscure the application from the technology of the host environment. The EATS core retains its network nature, and incorporates web capabilities via integration with Jetty as a peer process on the Eclipse Bus. Eclipse P2 will be employed for ITIL management process.
The EATSv5 Knowledge Repository is a dynamic body of knowledge, not a single place or database. Interactions take place against a single system, the KR, through a consistent set of UX widgets and tools using a device interface, but processing, even when entirely accomplished locally on that device, is always accomplished using an asynchronous message-based protocols, as background processing over whatever network of machines and devices happens to be required for resolution. The Eclipse ecosystem defines an architected technology host container for the EATS Architected Space. Eclipse can be run on almost any Java machine, from a RasPi to a mainframe computer. It runs on robots on Mars. EATSv5 runs on Eclipse as a client-server network, or as a stand alone installation. It requires enablement as a Java application. The Architected Space for EATSv5 is defined by configuration. Architected Elements communicate by message passing using a standardized Document Object Model (DOM).
EATSv5 RCP Life Cycle Model
EATS Infrastructure Life Cycle discusses the EATSv4 LIFE CYCLE model and previous generations of the code. It also lays out issues related to Eclipse and Cloud migration of the infrastructure, including difficulties which inhibited v4.7 progress. Previously versions of EATS were based on ownership of the Inversion of Control driver mechanism using a hard, top down, continuous monitoring of control, management paradigm. The paradigm and the methods evolved from a desire to be concerned simultaneously with maximize productivity while minimizing resource utilization, and being responsible for both dynamics. We are past the point where Moore’s Law based in the normal range of Physics and Chemistry is supplying free hardware as a cyber architecture resource. The physics of concern is now network latency, efficiency and effectiveness of delivery to task requirements. EATSv5 is implemented as an inverted mental model for the development of an automation and the security system1Relates to the true owner of two-sided glass of the UX. This implements the shift to the reactive operational model discussed in the Eclipse transition discussion on the AF.net website.
The diagram below is taken from e4 – Fundamental Overview on the Eclipse 4 Application Platform. It shows the e4 Application Platform as a functional block model. The Application Model hosts MPart and MHandler parts, which are bound by the injection and Inversion of Control (IoC) mechanisms to the generated, human-user interaction (UX) framework. This maps the surface of the human-cyber interaction space. Key presses and mouse clicks trigger MHandler triggered algorithms. The algorithms reflect results through effects seen in MPart behaviors.
When executed using the e4 Application Model runtime, the e4 Application Model runs the environment and instantiates and activates application classes in response to events within the model. The e4 Model is executed as an OSGi Equinox application. The awareness of operating context and framework at the functional service level is keyed through two API classes and their associated methods, in addition to the event driven DI, annotation tagged, callback interface. MPart specification elements are implemented by association with application defined classes. Events trigger methods within the class based on assignment through Java annotation specifications.
Activator provides the platform interface to the operating system for any Eclipse Plug-in. Activator is the Bundle Activator for the Bundle that defines the operating context for EATSv5 execution. EATSv5 is constructed as an Eclipse Plug-in. Eclipse provides a standard framework for an OSGi Bundle Activator. The activator has 2 primary functions:
- Provide the technical context for operation
- Provide start() and stop() operations to inform the application when the machine is in a stable state and capable of operation, and when to cease operations during times when the environment is unstable due to start-up, shut down, or hardware or software changes in progress.
The EATSv5 Activator is constructed via extension of the open source Eclipse Plugin standard activator.
E4LifeCycle is specific to the Eclipse e4 Application Model and the associated application life cycle of any application build and executed under the e4 execution framework. It is an event driven IoC framework that provides the mechanism for monitoring and supervision of e4 Application Model UX events and behaviors. The four key events which provide the core of the interface are: