What is Dynamic Suite Composition and how to implement it ?
In earlier versions of App-V, if you wanted virtual applications to talk to one another we usually include them in the same package. In version 4.5 it is now possible to allow two virtual applications to talk to one another by making one dependent upon another. If you had a plug-in that was used by ten different applications in the past you would have had to package the plug-in with every suite and if you needed to update it all ten packages would need to be updated. Now with DSC you sequence the plug-in separately and only need to update it once. The major benefit of this is it allows you to update packages separately.
Let’s discuss the example of Microsoft Office and Snagit (a plug-in for office).
The sequence of events are:
- Sequence Microsoft Office, create a package, then save it.
- Go back to a clean sequencer and create your Snagit package. However before you start monitoring make sure you install Office.
- With Notepad.exe open the OSD file for the Snagit package and copy the line that begins with codebase and copy the following bits
- MANDATORY – this you will type yourself. If MANDATORY=”TRUE” then the plugin will be required to run the main application so access must be given to it to allow the main application to run.
<CODEBASE HREF=”RTSPS://%SFT_SOFTGRIDSERVER%:322/<Sft File Name> ” GUID=”<GUID>” SYSGUARDFILE=”<snagit 8.3 folder>\osguard.cp” MANDATORY=”TRUE”/>
- Next open the OSD file for each of your Office apps that you want to use Snagit. Above the line that says </VIRTUALENV> type the following
- Paste the code from #3 above
- So in the end what you typed would look something like this:
<CODEBASE HREF=”RTSPS://%SFT_SOFTGRIDSERVER%:322//<Sft File Name> ” GUID=”<GUID>” SYSGUARDFILE=”<snagit 8.3 folder>\osguard.cp” MANDATORY=”TRUE”/>