Zum Inhalt springen

Anwendungsvirtualisierung

aus Wikipedia, der freien Enzyklopädie
Dies ist eine alte Version dieser Seite, zuletzt bearbeitet am 22. Juni 2010 um 16:37 Uhr durch imported>Larsrein (→See also). Sie kann sich erheblich von der aktuellen Version unterscheiden.

Vorlage:Refimprove Application virtualization is an umbrella term that describes software technologies that improve portability, manageability and compatibility of applications by encapsulating them from the underlying operating system on which they are executed. A fully virtualized application is not installed in the traditional sense[1], although it is still executed as if it is. The application is fooled at runtime into believing that it is directly interfacing with the original operating system and all the resources managed by it, when in reality it is not. In this context, the term "virtualization" refers to the artifact being encapsulated (application), which is quite different to its meaning in hardware virtualization, where it refers to the artifact being abstracted (physical hardware).

Description

Limited application virtualization is used in modern operating systems such as Microsoft Windows and Linux. For example, IniFileMappings were introduced with Windows NT to virtualize (into the Registry) the legacy INI files of applications originally written for Windows 3.1.[2] Similarly, Windows Vista implements limited file and Registry virtualization so that legacy applications that try to save user data in a system location that was writeable in older versions of Windows, but is now only writeable by highly privileged system software, can work on the new Windows system without the obligation of the program having higher-level security privileges (which would carry security risks).[3]

Full application virtualization requires a virtualization layer.[4] Application virtualization layers replace part of the runtime environment normally provided by the operating system. The layer intercepts all file and Registry operations of virtualized applications and transparently redirects them to a virtualized location, often a single file.[5] The application never knows that it's accessing a virtual resource instead of a physical one. Since the application is now working with one file instead of many files and registry entries spread throughout the system, it becomes easy to run the application on a different computer and previously incompatible applications can be run side-by-side. Examples of this technology for the Windows platform are Ceedo, InstallFree, Citrix XenApp, Novell ZENworks Application Virtualization, Endeavors Technologies Application Jukebox, Microsoft Application Virtualization, Software Virtualization Solution, and VMware ThinApp.

Technology categories that fall under application virtualization include:

  • Application Streaming. Pieces of the application's code, data, and settings are delivered when they're first needed, instead of the entire application being delivered before startup. Running the packaged application may require the installation of a lightweight client application. Packages are usually delivered over a protocol such as HTTP, CIFS or RTSP.[6]
  • Desktop Virtualization/Virtual Desktop Infrastructure (VDI). The application is hosted in a VM or blade PC that also includes the operating system (OS). These solutions include a management infrastructure for automating the creation of virtual desktops, and providing for access control to target virtual desktop. VDI solutions can usually fill the gaps where application streaming falls short.

Benefits of application virtualization

  • Allows applications to run in environments that do not suit the native application (e.g. Wine allows Microsoft Windows applications to run on Linux).
  • May protect the operating system and other applications from poorly written or buggy code.
  • Uses fewer resources than a separate virtual machine.
  • Run applications that are not written correctly, for example applications that try to store user data in a read-only system-owned location.
  • Run incompatible applications side-by-side, at the same time[6] and with minimal regression testing against one another.[7]
  • Maintain a standard configuration in the underlying operating system across multiple computers in an organization, regardless of the applications being used, thereby keeping costs down.
  • Implement the security principle of least privilege by removing the requirement for end-users to have Administrator privileges in order to run poorly written applications.
  • Simplified operating system migrations.[6]
  • Accelerated application deployment, through on-demand application streaming.[6]
  • Improved security, by isolating applications from the operating system.[6]
  • Enterprises can easily track license usage. Application usage history can then be used to save on license costs.
  • Fast application provisioning to the desktop based upon user's roaming profile.
  • Allows applications to be copied to portable media and then imported to client computers without need of installing them.Referenzfehler: Ungültiger Parameter in <ref>.

Limitations of application virtualization

  • Not all software can be virtualized. Some examples include applications that require a device driver and 16-bit applications that need to run in shared memory space.[8]
  • Some types of software such as anti-virus packages and application that require heavy OS integration, such as Windowblinds or StyleXP are difficult to virtualize.
  • Only file and Registry-level compatibility issues between legacy applications and newer operating systems can be addressed by application virtualization. For example, applications that don't manage the heap correctly will not execute on Windows Vista as they still allocate memory in the same way, regardless of whether they are virtualized or not.[9] For this reason, specialist application compatibility fixes (shims) may still be needed, even if the application is virtualized.[10]

Vendor-specific implementations

See also

References

Vorlage:Reflist

  1. ↑ Introducing Microsoft SoftGrid Application Virtualization. Microsoft;
  2. ↑ WritePrivateProfileString Function. Microsoft, abgerufen am 18. Juni 2008.
  3. ↑ Mark Russinovich: Inside Windows Vista User Account Control. Microsoft, Juni 2007;.
  4. ↑ Amir Husain: How to build an Application Virtualization Framework. VDIworks, abgerufen am 1. Juli 2008.
  5. ↑ Coby Gurr: Facilitating Microsoft Windows Vista Migration Through Application Virtualization. (PDF) Dell, 28. Januar 2008, abgerufen am 19. Juni 2008.
  6. ↑ a b c d e Desktop Virtualization Comes of Age. (PDF) Credit Suisse, 26. November 2007, abgerufen am 3. März 2008.
  7. ↑ Overview Series: Windows Vista Application Compatibility. Microsoft, abgerufen am 19. Juni 2008.
  8. ↑ Peter Varhol: Application Virtualization Hits Its Stride. Redmondmag.com, September 2007, abgerufen am 19. Juni 2008.
  9. ↑ Adrian Marinescu: Windows Vista Heap Management Enhancements. (PDF) Microsoft, 14. Juli 2006, abgerufen am 19. Juni 2008.
  10. ↑ Chris Jackson: Can You Shim Applications Virtualized in SoftGrid? Microsoft, 1. Mai 2008, abgerufen am 24. Juni 2008.
Abgerufen von „https://de.wikipedia.org/w/index.php?title=Anwendungsvirtualisierung&oldid=134587722“