Table of Contents
Advertisement
9.15 E
NABLING SHARED OBJECT ISOLATION
ZENworks Application Virtualization provides the ability to isolate shared objects in memory.
Certain applications will refer to objects in memory by a specific name, which can cause runtime
errors if a named object in a virtual application's memory collides with other objects of the same
name in the memory of a natively installed version of the application on the same device. Shared
object isolation creates unique names for memory objects at runtime, in order to allow a virtual
application and a natively installed version of the same application to run side by side without
conflict.
Currently, shared object isolation can only be enabled by manually editing the XAPPL file for a
virtual application.
In the following scenario, OBJECT 1 and OBJECT 2 are named objects used by a virtual
application that conflict with identically-named objects used by a natively installed application.
Common named objects include mutexes and named pipes.
To enable shared object isolation for OBJECT 1 and OBJECT 2 in a virtual application:
•
Open the XAPPL file of the virtual application you are working with in a text editor
•
Replace the <NamedObjectIsolation ../> element with the example below:
<NamedObjectIsolation enabled="False">
<Exception regex="[OBJECT 1]" />
<Exception regex="[OBJECT 2]" />
</NamedObjectIsolation>
•
Reload the XAPPL file in ZENworks Application Virtualization and build the
application
The resulting virtual application will have shared object isolation enabled. Note that multiple
objects in memory can be isolated simultaneously.
92
Novell ZENworks Application Virtualization
Advertisement
Table of Contents
