You can set up a Spoon Standalone server plug-in that allows users to receive applications that are created in Novell ZENworks Application Virtualization and streamed from the Web.
To build a model for streaming an application, you must first package and profile the application or product. This section includes the steps that make a product ready for streaming.
You need to package the application to prepare it for profiling.
Create a virtual application by using the templates available, or take a snapshot and capture the information.
While creating the application, select
> and ensure that the option is disabled.Build the application.
Learning the product for building application streams.
Click Packaging.
, select , and choose the virtual application to be profiled. This application is the one created inWhen you open the virtual application, its profiling begins.
Let the application run for a few of minutes to complete profiling and close the application. This step completes the profiling activity.If profiling is not complete, wait for a minute and select
to stop the profiling.Making the product ready for streaming.
After the profiling is complete, select
and create a model file for the virtual application.Create a new temporary location.
For streaming the application from the Web server, move the entire directory from the Client or temporary location to the Web server under the
folder. This directory contains one model.xm file and a number of *.xs files.Use the following steps to set up Spoon Standalone plug-in files on a Web server.
Extract StandaloneTemplate.zip to the root folder for the Spoon Web site.
In the root folder, edit scripts\spoon_config.js to specify the correct location on the Web server and the correct plug-in version. Do this by making sure that the Spoon_SiteRoot variable in this file refers to the root folder on the Web site where the Spoon files are found.
Example 1: If the files are copied to http://www.mysite.com/spoon/, edit the variable like this:
Spoon_SiteRoot=’/spoon/’;
Example 2: If the files are copied to http://www.mysite.com/products/streaming/, edit the variable like this:
Spoon_SiteRoot=’/products/streaming/’;
In the root folder, update the config\xvm.xml file and the config\spoonreg.xml file:
Find the <Configuration …/> element (located near the end of each file).
In this element, update the layer URL to point to the correct location.
Example: <Layer entry="True" type="Exe">http://www.mysite.com/layers/spoonreg/8-0-1271-4__0/spoonreg.exe</Layer>
In the root folder, modify launch.html by setting the Spoon_Config variable to the full URL path of the application configuration file to be used for launching the application.
Example: Spoon_Config = 'http://www.mysite.com/config/myappconfig.xml’;
For more information, see Creating an Application Configuration File by Using the Command Line Utility.
ZENworks Application Virtualization allows you to generate site license certificates, which can then be used to generate application configurations to be used with the Novell standalone streaming server.
Launch the ZENworks Application Virtualization console, then click
.In the
box, click .Enter the following details in the fields provided:
Organization Name: Provide a name for the organization.
Unit: Provide a name for the user per unit.
Allowed Portal Hosts: Provide the allowed port or ports of a server from which the application streams.
Click
to request the license certificate, then select to save it to a desired location.Making new applications available on the Spoon Standalone server requires adding the .svm or streaming files to the Web server and creating a configuration file that references the application.
After you use ZENworks Application Virtualization to package and profile the application you want to stream, create a folder on the Web server to host the files.
Example Path for a Streamed Application: http://site/site_root/layers/application_name/version__revision/xstream/model_revision/
A concrete example of a path for a streamed application might be
http://www.mysite.com/spoon/layers/firefox/3.5.0.8__0/xstream/0/
Example Path for a Non-Streamed Application: http://site/site_root/layers/application_name/version__revision/
A concrete example of a path for a non-streamed application might be
http://www.mysite.com/spoon/layers/firefox/3.5.0.8__0/
ZENworks Application Virtualization now allows you to generate site license certificates, which can then be used to generate application configurations for use with Novell’s standalone streaming server.
Launch the ZENworks Application Virtualization console, then click
.In the
box, click .Enter the following details in the fields provided:
Application Name: Provide a name for the application.
Application Version: Provide a version number for the application in the following format: Major.Minor.Build.Revision format, for example, 3.8.12.895.
Layer Revision: Provide the current revision of the application build.
Type: Select either SVM or XM (streaming).
Layer URL: Include the path to the location where the application is hosted. The file will be of the .svm or .xm format, as defined by the type check box).
Xvm Config URL: Path to the location of the virtual machine configuration.
SpoonReg Config Url: Path to the location of the SpoonReg configuration.
Certificate Path:
Path to the requested application license certificate that was saved during generation of the application license certificate. Click to search for this location.
Click
to request the application configuration.Each application delivered by using the Spoon Standalone requires a unique .xml configuration file. Each configuration file is linked to a private key. An application configuration file is copied to the Web server and referenced on the Web page where the application is launched. The Spoon Standalone plug-in uses the configuration file to validate the application and determine where to locate the files to stream and launch the application.
Use the LicenseUtil-Novell.exe command line tool (extracted from StandaloneTemplate.zip) to create application configuration files.
IMPORTANT:The LicenseUtil-Novell.exe command line tool requires Microsoft .NET Framework 3.5 for correct operation.
When you create a configuration file, the first parameter must be CreateAppConfig. For other command line parameters, refer to the following list:
/pc: The path to the private key (ZAV80-NOV-xxxxxx.xml) file on your Web server.
/an: The name of the application (limited to ASCII characters).
/av: Application version information (application_version;layer_revision;model_revision_if_applicable).
Streamed Application Example: 1.0.0.0;0;0
Non-Streamed Application Example: 1.0.0.0;0
/au: The URL to the model file for a streamed application or to the .svm file for a non-streamed application.
Streamed Application Example: http://www.mysite.com/layers/myapp/1.0.0.0__0/xstream/0/model.xm
Non-Streamed Application Example: http://www.mysite.com/layers/myapp/1.0.0.0__0/myapp.svm
/vm: The version information for xvm.exe version;revision, such as 8.1.1398.1;0
To locate the version number, from the extracted StandaloneTemplate.zip folder, go to layers, select either xreg or xvm folder. Copy the directory name 8-1-1398-1__0 and replace it in the command line as 8.1.1398.1;0
/xvm: The URL to the .xvm configuration file.
/xreg: The URL to the .xreg configuration file.
NOTE:The spoonreg version and revision information is assumed to be identical to the xvm version and revision.
/o: The output file.
The following is an example of the command line syntax that was used to create a GroupWise application configuration file.
C:\inetpub\wwwroot>LicenseUtil-Novell.exe CreateAppConfig /pc c:\bh\Zav8-Internal-Spoon Certs\ZAV80-NOV-0000#.xml /an groupwise /av 8.0.1.0;0;0 /au http://164.99.186.184/spoon/layers/groupwise/8-0-1-0__0/xtream/0/model.xm /xvm http://164.99.186.184/config/xvm.xml /spoonreg http://164.99.186.184/spoon/config/spoonreg.xml /vm 8.0.1236.1;0 /o groupwise.xml
After you generate the configuration file, save it in a convenient location on the Web server, for example, http://site/site_root/configs/.
This section includes the following information:
(Conditional) On the Windows desktop, click
> > , select , then click .Repeat this step to remove all previous installations (versions) of the Spoon Sandbox Manager.
NOTE:Although this step is unnecessary for end-users, it helps you to ensure that the plug-in installer is correctly referenced.
Use a Web browser to navigate to plugin-check.html. For example,
http://www.mysite.com/spoon/plugin-check.html
Install the plug-in.
From a text editor, open launch.html and edit the Spoon_Config variable to reference one of the application configuration files available on the Web server.
Use a Web browser to navigate to plugin-check.html.
The page then redirects to launch.html. The application buffers and then launches.
NOTE:The application configuration file is cached by the plug-in for up to 15 minutes. If the application configuration is changed, it is best to restart the Spoon plug-in (select
) before retesting.The DebugView tool from Microsoft generates the logging information output from the Spoon plug-in. Use the following steps to obtain, configure, and use the tool.
Download the DebugView tool from the Microsoft Web site.
Run the debug tool (dbgview.exe) to immediately start capturing the debug output.
In HKEY_CURRENT_USER\Software\Code Systems\Spoon of the Windows registry, create the value and add Debug as a new String value.
On the Windows desktop, select
to restart the Spoon plug-in.Navigate to launch.html.
Inspect the DebugView output for possible errors in the application configuration file.