Evalaze is an application virtualisation solution created by Dögel GmbH. The company was founded in 2005 as Dögel IT Management. Since then it has specialised in web development as well as the sale and support of innovative software solutions. Up to 2007, Dögel GmbH’s distribution network extended across the countries Germany, Austria and Switzerland. Since 2008, the company has had global success, reaching far beyond the German-speaking territories. The company has been involved in application virtualisation since the launch of Thinstall 2007 (now ThinApp by VMware) in Germany by Dögel IT Management. Thanks to the experience gained there, Dögel IT Management advanced to become the leading provider of application virtualisation in Germany, developing a high level of expertise in all areas from sales through to support. An increasing number of competitive products were tested and installed at customer sites. Over time it became clear that customers required not only fully functioning products, but also a technical support service to guide them. In mid-2008, the company decided to develop its own solution. The concept envisaged the development of an application virtualisation tool that would satisfy customers’ requirements. A technical support service would also be offered given that such a service was not yet available to corporate clients. In December 2010 the company released the first version called 0.9. A year on, version 2.0 will support even more applications while also offering a variety of new features.
- What is Application Virtualization?
- Which Problems has Evalaze solved?
- Which System Requirements Evalaze need?
- Why can I not activate Evalaze?
- Why can I not start the Evalaze-Builder?
- What is an Entry Point?
- What is a Sandbox?
- What is a Snapshot?
- What does isolation mean?
- How does file association works?
- What is a Splash Screen?
- What do you mean with capture?
- What is Logging?
- How can integrate Evalaze in our company?
- When Is Application Virtualization Feasible?
Virtualisation enables the use of system-independent applications. A virtualised application can be run locally from your hard drive or from different physical media (CD, USB, etc.). During the virtualisation process an application is consolidated into a single .exe file. All the required .dll (library) files and registry entries are contained within the file.
Evalaze offers the opportunity to make applications both portable and platform independent. Furthermore, following the creation of a virtualised application your operating system no longer needs to stay loaded with unnecessary data. Examples of cases that can be solved with Evalaze include:
Applications that, due to the introduction of a new operating system, are no longer functional can be run again thanks to Evalaze (32-bit applications on 64-bit systems).
Watch a example
Virtualised applications can be copied on to a memory stick and executed from there (e.g. analytical tools for administrators).
Applications can be designed in such a way so as to revert to their original state upon completion.
Companies that wish to distribute applications as simply as possible can make use of the existing software distribution system or post on a network share.
Different versions of a browser can be used, for example, browser A version 1 for the intranet and browser A version 2 for the Internet.
Example: different runtimes at the same time
With Evalaze virtualization technology there are essentially two types of systems. When creating a virtualized application, one refers to what is called the capture process and capture system. The capture process involves scanning the system before the application's installation, followed by a further scan once the installation and configuration of the application has been completed. This is the process for the creation of a virtual application.
Recommendations for the Capture System:
- Windows XP as a physical or virtual machine; We recommend a newly set-up operating system on a virtual machine
- Microsoft .NET Framework version 2.0 or higher
- The requirements for the system and hardware are that they must be at least equivalent to the virtualized application being created. Evalaze requires at least 256 MB of RAM memory
- 15MB hard disk space and at least four times the space taken up by the application to be virtualized.
The second type of system is called the target system. This system is called the operating environment in which the virtualized application will run.
Recommendations for the Target System:
- System and hardware requirements are at least equal to those of the virtualized application
- Windows XP or later; Windows Server 2003 or later
Recommendations for the Virtualization of Applications:
Install Windows followed by .NET Framework 2.0 on a virtual machine. Do not perform any additional installations as these could affect the virtualization process. Copy Evalaze onto the system and launch it to adjust any settings as necessary. Then quit Evalaze and you will obtain a snapshot of the entire virtual machine in a clean state. After the virtualization of an application has been carried out, you can reopen the snapshot and use it to reset the virtual machine back to a clean condition.
For the activation of Evalaze you need a internet connection. The licence-key will be checked with our licence server. Make a snapshot of the capture system after the activation (if you use virtual machine), so you do not need repeat the whole process. For the case if you use a Proxy-Server, please shut him down for the period of activation.
When the below message is displayed on your screen, is the main reason the missing of .net Framework. Evalaze needs at least .net Framework 2.0. Download Microsoft .NET Framework 2.0 Redistributable (x86)
During the virtualisation process the application must be linked with the boot file. At the post-scan stage, Evalaze records all added executable files and displays them as possible entry points.
A sandbox is the area within which the virtualised application caches all required information and individual settings. This path must be set during the virtualisation process. Evalaze also offers the option of automatically deleting the sandbox when the application is terminated. That the sandbox also stores your individual settings and profiles during use should also be noted. If the sandbox is deleted, then the application is reset to its original state. This would mean a virtualised browser losing all pre-recorded settings such as favourites, opening page, etc.
In the information technology sector there are many definitions for the term “snap-shot”. At Evalaze we understand it in the classic sense of the term. The first snapshot is taken at the pre-scan stage (first system scan). Another is done at the post-scan stage. Evalaze compares the two snapshots and the changes (deltas) are recorded. Based on these deltas the Evalaze engine recognises that a change (i.e. installation) was performed on the system.
Virtualised applications can, depending on the degree of isolation, be sealed off from the operating system. With Evalaze, files and registry entries (directory, file, registry key and registry value) can be configured individually. There are three degrees of isolation: Merge, Write Copy and Full Merge.
Merge: Objects on the host that are marked with the Merge isolation mode can be directly accessed by virtualised applications. Objects that already exist on the host can be modified directly from the virtual environment. In this instance Evalaze passes on the changes to the host. However, if a user starts the run time of an object with the virtualised application, Evalaze stores it on the host. The merge mode is particularly suitable for directories, wherein users store their own data.
Write Copy: Objects existing on the host that are marked with Write Copy can be read by the virtualised application. However, write accesses are redirected to the sandbox. Evalaze creates a duplicate of the file in the sandbox and works with the copy. In general, Evalaze isolates objects in this mode.
Full: Objects in this mode are completely sealed off from the virtual ones. An application does not have access to these objects on the real system. If the host system contains a folder with the same name within its directory tree at the corresponding place, the files contained therein will not be available for the virtualised application. Only files in the appropriate directory of the virtual environment can be used. This mode is ideal for hiding applications installed on the host from the virtualised application. This ensures, for example, that a virtualised application cannot access the local settings of another installed application.
Watch the video:
File associations and links can be configured during the virtualization process. This gives the charm of the virtualized application of a fixed locally installed application.
Watch the video for more informations:
The splash screen is a graphical component that appears when the virtualised application is launched, similar to a welcome screen. The splash screen contains information about the application being launched, including version number and the application engine. In the ‘Commercial’ editions the splash screen can either be customised with a logo and additional text or be switched off completely.
When creating a virtualised application there is a 'capture process' and consequently a 'capture system' as well. This process involves scanning the system before the application’s installation, then scanning after the installation and configuration of the application being virtualised. The changes (deltas) are recognised by Evalaze's virtualisation engine. The capture, including the memory path, is defined during the virtualisation process and then saved. This enables you to retrospectively make changes to the project and, by extension, to the application as well. This means that there is no need to re-run all the settings and that new versions of Evalaze (with increased functionality) can be used to virtualise your application. So make sure to store the capture carefully!
Evalaze offers the option of monitoring events and processes during virtualisation. This file is called a log and its creation is known as logging. The log will serve both your developers and ours as a tool for error and process analysis. It should be noted that the log setting choices in the free edition are limited to either “off” or “normal”. It is only with the extended editions that there is the option of increasing the level of detail. The log can be saved through the graphical interface.
In order for your company to purchase Evalaze you simply have to contact us. We will be only too happy to put together a quote for your business, or you can simply use our shopping system. As soon as you have bought a license, you can use Evalaze and the virtualised applications to the level you have purchased, allowing free reign for your creativity.
That depends on the needs of the end user. Some people use Evalaze because of its uncomplicated deployment via USB or network drives. Others want to use an operating system-independent solution, so that their system will not become burdened or slowed down with useless data. Evalaze works when you need to set up applications quickly without having to carry out complicated installation routines.