How to isolate mutexes, events and semaphores (MutexIsolation)

Save to PDF

Applies to: AppAcceleratorV

12/08/2019 Cliff Hobbs   ID: 267104

Overview

In order for some desktop applications to run securely and safely on a server operating system, they require systems resources to be isolated so they do not attempt to access the same resources which may need to be controlled by different mutexes, semaphores, and the events generated. 

By default, the Cloudhouse Redirection Engine (AAV) will not isolate any mutexes, semaphores or events; isolation will only be enabled if the <MutexIsolation>, <EventIsolation> or <SemaphoreIsolation> isolation tags are specified. For each tag, the name referenced within it is redirected to a process specific name. 

Video Example: Google Earth

Only a single instance of Google Earth can run on Citrix Virtual Apps (XenApp) or RDS, watch a video to see this compatibility Feature in action for mutex isolation.

<AAV>
  <MutexIsolation>
    <MutexName>Google Earth Google Mountain View</MutexName>
  <MutexIsolation> 

Step-by-step process

  1. Open AppAcceleratorV.clc
  2. Open Redirections.xml and create a tag for the type of system object you would like to isolate.
  3. Create the tags required for <MutexIsolation>, <EventIsolation> or <SemaphoreIsolation>
    <MutexIsolation>
      <MutexName>FirstMutexName</MutexName>
      <MutexName>AnotherMutexName</MutexName>
    </MutexIsolation>
     
    <EventIsolation>
      <EventName>FirstEventName</EventName>
      <EventName>AnotherEventName</EventName>
    </EventIsolation>
     
    <SemaphoreIsolation>
      <SemaphoreName>FirstSemaphoreName</SemaphoreName>
      <SemaphoreName>AnotherSemaphoreName</SemaphoreName>
    </SemaphoreIsolation>
Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support