Dynamic Suite Composition (DSC) is new for App-V version 4.5. It allows linking of applications that have dependencies while not requiring that they be sequenced in the same virtual application package.
To use DSC, you must take some important steps. For the purpose of these instructions, a primary application is the sequenced application that will have a plug-in installed. The secondary application, or plug-in, is an application that relies on or integrates with the primary application.
To use DSC to link two packages
1. Sequence the primary application on a clean sequencing computer following sequencing best practices.
See the section Stream Applications.
2. Sequence secondary applications, making sure the primary application has been installed on the sequencing computer first.
This step ensures that the sequencer has all the application programming interfaces and libraries needed for the secondary application to install various integrations with the primary application. Using Microsoft Office as an example, Microsoft Office has been installed on the sequencing computer before sequencing the secondary application. It is installed natively, meaning that it has not been virtualized.
3. After sequencing both applications, perform one of the following tasks:
· If streaming the application, publish them to a distribution point and complete the remaining steps on the App-V Streaming Server or Management Server.
· If using Stand-alone mode, package applications as MSI files, then complete the remaining steps on the sequencing computer before generating the MSI file.
4. Edit the OSD file for the secondary application. Copy the tag containing the <CODEBASE> tag to the clipboard.
5. Open the primary application’s OSD file.
6. After the </VIRTUALENV> tag, add a <DEPENDENCIES></DEPENDENCIES> container, and then paste the <CODEBASE> tag from the clipboard into it.
7. Remove from the <CODEBASE> tag all but the following parameters:
· HREF, which is the property that defines the URI for the package
· GUID, which is the package ID
· SYSGUARDFILE, which is the property that determines the relative path to the OSGUARD.cp file
· MANDATORY, which is a Boolean field that you must add manually and that determines whether the secondary package is required for the primary package to run. (A package is optional by default.)
The XML file should look like this:
<CODEBASE HREF="RTSP://appvserver:554/PLUG-IN.001/PLUG-IN.001.sft" GUID="B8BCA34F-25C2-4CC2-9623-CA366C801E89" SYSGUARDFILE=" PLUG-IN.001\osguard.cp" MANDATORY="YES"/>
8. Verify that the primary application is properly interfacing with the secondary application.