A suite of products with multiple components in it can be virtualized as a single application and launched via the “command line” using triggers or appropriate components can be opened by opening the application window. A few examples for this kind of application are MSOffice, OpenOffice, Safari browser, etc. If these types of applications need to be posted in a streaming site, then how can we organize them? How is the application profiled or configuration files created? The following document answers all these queries.
The following section illustrates how this can be achieved using ZAV 9, for example OpenOffice 3.2.1 version is considered. Follow the step-by-step procedures below:
Steps to follow for achieving this with ZAV 8.x or 9 version
- Create the virtual application and enable multiple startup scripts for sub-applications.
- Generally the virtual application opens the quickstart executable which provides all the sub-options to open further applications
- Open the multiple startup files link and select one of the sub-applications as the startup file such as scalc or sbase and rebuild the application.
Fig 1: Selection of appropriate application for start up.
- Such an application is profiled and created model with appropriate Icons. The steps of creating a virtual application, profiling and modeling need to be done with all components, such as sbase, soffice, swriter. For example create the virtual application with a startup selected as sbase, create the profile for that component and later model that application.
- Create a separate config file for each of the applications with which the profiles/models were created for each of the components.
- Post these on the Spoon standalone web server and configure links for accessing these.
Steps to follow for achieving this with ZAV 9 version
- Create the virtual application and enable multiple startup scripts for sub-applications. Either you can keep the default sub-application as startup application or you can remove it.
- Create the profile and also model for the whole application.
- During the creation of config file select the startup file accordingly, in the startup options dropdown list.
Fig 2: Start up files selection in the App Configuration page.
- Similar manner create multiple config files with different startup options.
- Post these on the spoon standalone web server and configure them appropriately.
Note: The benefits of the second approach is we have to build the application only once and create config files multiple times. Whereas in first approach with each component the virtual application need to be rebuilt with specific startup application option.
For creation of profile, model and application config file use the following documentation link (6.2.1 section)