Product Documentation

To set up inter-isolation communication

Dec 17, 2015

During the profiling process, set up inter-isolation communication for applications profiled independently that should interact as though they are integrated with other profiled applications.

The order in which profiles are listed determines the precedence of isolation rules and operations for the applications in the inter-isolation communication profile. The rules that exist for each profile are merged into a single list of rules, with the rules of highest priority taking precedence.

Important: Refer to the system requirements for user devices if you plan to deliver profiles with inter-isolation communication.
  1. On the Set up Inter-Isolation Communication page of the profiling wizard, click Browse to locate the directory (not the files themselves) where your existing profiles are stored. To be linked, the profiles must all be located in the same directory.

    Make sure that each of the profiles you link has a target for the operating system of the profiling workstation.

  2. In the Browse for Profiles box, click Browse to locate the directory where your existing profile directories are saved. For example, if you saved “Adobe.profile” in the following location:
    navigate to the Profiles directory (the grandparent of the profile file).

    To be added, all the profile directories must be located in a single directory, such as “Profiles” in the example.

  3. Click the check box of the individual profiles to link in this profile.
  4. When you highlight a profile, use the Move Up and Move Down buttons to set the order of priority.

    For example, if you create a linked profile for Microsoft Office 2007 and Adobe Reader (any version), make sure that Office 2007 is the top-level application in the profile, which ensures that the Office isolation rules take priority over those of Adobe Reader. This priority is required for Office applications to launch correctly.

  5. For new profiles, continue in the wizard to the Set Operating System and Language page:
    • To link existing profiles only (the profiles you selected on the previous page) but not create any new applications or targets, called an associated profile, check the top check box (not selected by default). When you click Next, the wizard skips the installation pages and goes directly to the final step, signing the profile with a digital signature.
    • To create an additional target or application in this profile, called a dependent profile, make sure the top check box is not selected and continue using the wizard to create the new target or install the application in the profile. Use this option if the new target or application is to be dependent on the profiles you selected on the previous page.
  6. On the lower part of the page, carefully review the lists of operating systems and languages.
    Important: Each profile must contain a similar set of targets as all the other profiles in the linked profile, including a target that matches the profiling workstation. Note the superset of operating systems, service packs, and languages contained in all the linked profiles, and then check to make sure that each linked profile contains a target for all the operating systems, service packs, and languages in the superset. User devices must have a target in each of the linked profiles or they cannot launch any applications in any of the linked profiles.
    • Available. This profile property is available in the common range of target configurations.
    • Not Available. This profile property is missing in one or more target configurations.

Continue the installation using the profiling wizard, as normal. After you save the profile enabled with inter-isolation communication, publish the applications using the Citrix AppCenter in XenApp.

To view or modify the contents of the inter-isolation communication profile, from the navigation panel, select the profile; from the Edit menu, select Profile Properties; and from the navigation pane, select Linked Profiles.

Linked profiles are stored within the .profile file by name rather than by the path. At application launch, the profiler service searches the INSTALLROOT locations of the linked profiles.

When the user device runs a profile enabled for inter-isolation communication, the user-level settings that are stored on that user device by an application in one of the individual profiles are ignored, and the user-level settings of the application start fresh as if the application is being launched for the first time. To change this behavior, write a pre-launch script to migrate settings from specific applications whenever the linked profile is executed on the user device.