This final design for the integration framework has changed slightly from the initial version presented in PERICLES deliverable D6.1 . We describe the changes and the reasons for them in the early chapters of this report.
The integration framework is built from standard encapsulation technologies – Docker containers and RESTful web services – and controlled by a standard workflow environment – jBPM controlled by the Jenkins continuous integration system. On this execution layer, arbitrary workflows representing digital preservation activities can be deployed, run and evaluated. Standard tools – mediainfo, bagit, fido and so on – can be encapsulated and deployed, as can new preservation tools developed within the project.
Two new subsystems have been designed to couple the workflow execution layer to the abstract models developed through the research activities of the project: the Process Compiler (PC) and the Entity Registry-Model Repository (ERMR). The ERMR also provides the key link to the Linked Resource Model Service, an external semantic reasoning service under development by partner XEROX Research. These two subsystems provide the means to couple powerful semantic reasoning and policy-driven models to a “live” digital preservation system.
The API designs and technology choices for the test bed are now settled and implementation of the underlying (standard) test bed infrastructure is complete. The APIs and communication patterns are based on RESTful web services and JSON payloads and are described in detail in Section 5 and in the appendices.
Implementation of the new ERMR and PC subsystems is well underway. The focus for the integrated test bed over the final stages of the project will be on demonstrating the full end-to-end power of the model-driven preservation approach through the implementation of key application scenarios using models, tools and components drawn from across the PERICLES project. Examples of such
scenarios are given in the appendices.
|Type||Deliverable 6.4 of PERICLES EU project|
|Media of output|
|Number of pages||80|
|Publication status||Published - 6 Nov 2015|