Streaming Virtual Applications
31
n
ov
do
cx (e
n)
16
Ap
ril 20
10
Example 1:
If the files are copied to
http://www.mysite.com/spoon/
, you would edit the
variable like this:
Spoon_SiteRoot=’/spoon/’;
Example 2:
If the files are copied to
http://www.mysite.com/products/streaming/
, you
would edit the variable like this:
Spoon_SiteRoot=’/products/streaming/’;
3
In the root folder, update the
config\xvm.xml
file and the
config\xreg.xm
l file.
3a
Find the
<Configuration …/>
element (located near the end of each file).
3b
In this element, update the layer URL to point to the correct location.
Example:
<Layer entry="True" type="Exe">http://www.mysite.com/layers/
xreg/8-0-1271-4__0/xreg.exe</Layer>
4
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” on page 33
.
6.2.2 Configuring the Web Server
To finish configuring the Web server for the Spoon Standalone server plug-in, add the following
special file types to the Web server’s MIME type list.
.
svm
(application/octet-stream)
.xs
(application/octet-stream)
.xm
(application/octet-stream)
.xlayer
(application/octet-stream)
6.2.3 License Certificates
Each Spoon Standalone server deployment uses a public certificate or “key” and a private certificate
or “key” to validate that the applications are running in a licensed environment. You use the private
key to generate application configuration files (see
“Creating an Application Configuration File” on
page 33
), and you install the public key on the end-user devices to access the applications delivered
from the Spoon Standalone server. The public key validates the private key and it also validates that
the applications to be streamed are secure.
Do not confuse the public and private license certificates. The public key file is of the construction
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx
, which is an auto-generated alphanumeric ID with no file
extension. The private key is named
ZAV80-NOV-
xxxxxx
.xml
.
IMPORTANT:
Do not rename the public key.
You can download these keys in a single
.zip
file at the
Novell Customer Center Web site (http://
www.novell.com/customercenter/)
using your Novell customer account. To license the product,
download either the evaluation public and private license keys (included in
zav8-nov-eval.zip
)
or the public and private license keys that you purchased from Novell (included in
zav8-nov-
