Emulation as a Service - Demo Page
Where is the old bwFLA demo? The bwFLA project ended 2013 and the demo was ageing. We'll
replace the old demo pages with new demo instances, starting with the result of the EMiL project.
Note: Old passwords will remain valid on all new demo pages.
Who (or what) is EMiL? - EMiL (Emulation of Multimedia-objects in Libraries) was a two-year project (2014-2016) funded by the DFG. This demo page shows the results of this project. EMiL consists of two user interfaces, one aiming at end-users (source code / Live Demo) and one to be used by library staff (source code / Live Demo). Both UIs are just functional examples and made to demonstrate the use and integration options of the EMiL RESTful API.
EMiL User UI
This UI demonstrates a typical user workflow, starting from a catalog view to select
a digital object to be rendered.
To try EMiL, go to the EMiL-UI Demo-Page. The demo page is password protected. The old bwFLA passwords will still work. You may ask for an account by mailing to email@example.com
The EMiL Demo provides a simple catalog example, simulating a web-based library catalog. The catalog is acting as a starting point for users to access digital objects.
By choosing an object (left-click on the object or through the context menu), the EMiL access workflow is started. The catalog system passes the object ID to the EMiL EaaS framework using a HTTP request. The object is characterized on-the-fly, if no manually assigned emulation environments are found. The characterization process, if successful, provides a (list of) suitable emulation environment(s) for the object.
Emulation Access Landing Page
The result of the characterization process is a list of suitable rendering environments. The emulation access landing-page suggests a specific environment. If there are more suitable environments available (e.g. Windows/Mac hybrid CDs) the user is able to choose from a list of alternatives.
Object RenderingBy default, objects are rendered within the browser using HTML5 techniques. While the session is active, the user is able to use the object interactively as well as to control the emulation system (e.g. create a screenshot, change media if an object consists of multiple media and stop or restart a session).
Emil Administration User UI
This UI demonstrates typical curational tasks, such as maintaining an emulation environment.
To try EMiL, go to the EMiL-Admin UI Demo-Page. The demo page is password protected. The old bwFLA passwords will still work. You may ask for an account by mailing to firstname.lastname@example.org
Maintain Automated Evironment Assignment
If the automated characterization process fails or produces insufficient results, the environment assignment can be adapted manually. To access an object's suggested environment list, use the context menu and choose edit (from the EMiL user UI). You will be redirected to the EMiL admin UI.
Additional environments can be added to the suggested environments list and/or the ordering can be changed.
All environments can be tested with the chosen object (click on the "test" button). Within the "test context", it is possible to create so-called "object environments", environments tailored for a specific object, e.g. with pre-installed software or automatic start of an application.
Object environments can be exported, e.g. to run as stand-alone boot-to-emulator instances.
Emulation Environments Overview
- Environments can be configured, e.g. network configuration, screen resolution and color depth, etc. An environment "configuration" will not create a new environment.
- Create a new environment by installing a software package to an existing environment.
- Export an environment to the Cloud or USB appliance.
Manage SoftwareWithin EMiL, software is treated as a regular digital object with additional metadata. In particular, EMiL needs to know the software's rendering capabilities (to improve environment assignment) and to enforce (optional) licensing restrictions.
Create New Base Environment
Base environments are basic operating system installations for a given (emulated) hardware platform. This workflow allows to choose a supported hardware platform and an installation medium to create a new base environment.
Alternatively, an existing disk image file can be imported and assigned to an emulated machine definition.