Preparing the Package's Applications

Before you create the package, you need to make sure that the package's applications are ready. Refer to the following sections:

• Desktop Applications
• Thin-Client Applications
• Web Applications

Desktop Applications

OnDemand Services uses ZENworks for Desktops (ZfD) 3.2 to distribute desktop applications. Before you can add a desktop application to the package, you need to use ZfD to prepare the application for distribution. For information about using ZfD to distribute an application, see the ZfD 3.2 documentation on the Novell Documentation Web site.

As you prepare a desktop application that will be used with OnDemand Services, keep in mind the following requirements that are specific to OnDemand Services:

• When creating and configuring the Application object, make sure you use a UNC path (for example, \\server_hostname\vol1\snapshot\appname) in any locations where you are prompted for a path, and that you use the server's hostname in all locations where the server name is required.
• Do not use any of the following characters in the Application object's name:

  " (double quote)	+ (plus)
  = (equals)	\ (backslash)
  < (open angle bracket)	; (semicolon)
  > (close angle bracket)	/ (forwardslash)
  , (comma)	# (pound sign)

• Do not use the Application object's Association page to associate the application with users. OnDemand Services will create this association when a user purchases a package that includes the application.
• If you plan to use a pricing scheme that requires the application's usage to be tracked (see Establishing the Package 's Cost ), turn on the Enable OnDemand Services to Track Usage of This Application option. This option is located on the Application object's OnDemand tab.
• If the application's usage will be tracked (as discussed in the previous bulleted item) and the application's executable is a stub program that simply launches the real executable (for example, write.exe launches wordpad.exe), make sure that you've entered the real executable filename in the Application object's Monitor Module Name field (Run Options tab > Environment page). Otherwise, OnDemand Services will only track usage of the stub program, which will result in a very brief, inaccurate usage tracking record.

Thin-Client Applications

OnDemand Services uses Novell DeFrame^TM 2.01 to distribute thin-client (terminal server) applications. Before you can add a thin-client application to the package, you need to use DeFrame to prepare the application for distribution. For information, see the DeFrame 2.01 Installation and Administration Guide (deframe.pdf) on the root of the Novell ZENworks OnDemand Services 2 CD.

Web Applications

To include a Web application in a package, you need to 1) make sure the application is located on a Web server that users can access and 2) create a Commerce Item object to define the application in Novell eDirectory^TM.

You can also include Web content, such as document, video, or audio files, in addition to Web applications. The same process is required if you want to include Web content.

To create a Commerce Item object in eDirectory:

1. In ConsoleOne^®, right-click the container where you want to create the object > click New > click Object.

   You should create the Commerce Item object in the company container (as defined in the OnDemandService object) or one of its subcontainers. This ensures that OnDemand Services has sufficient rights to the object. If you create it outside of the company container or its subcontainers, you will need to make the OnDemand Administrator (ODSAdmin) object a trustee of the Commerce Item object. For details about the required trustee rights, see ODSAdmin Trustee Rights .

2. In the New Object list, select the commerceItem object, then click OK.

3. Provide the new item with a name.

   The name you supply will be used for the object's eDirectory name and for display in the OnDemand Services gadgets if you do not supply a Display Name later. Do not use any of the following characters in the name.

   " (double quote)	+ (plus)
   = (equals)	\ (backslash)
   < (open angle bracket)	; (semicolon)
   > (close angle bracket)	/ (forwardslash)
   , (comma)

4. Select the Define Additional Properties box, then click OK.

   
   

5. On the General tab, fill in the following properties:

   Display Name: Enter the name of the item as you want it displayed to users. If you don't enter a display name, the Commerce Item object's name is used.

   Launch Command: Click the Define Command button () to display the Launch Command dialog box. Enter the URL for the Web application or content, then click OK.

   Snapin Command: This field applies only if you are using Novell iChain^® to secure access to the Web application. If so, click the Define Command button () to display the Snapin Command dialog box. Browse for and select the iChain ACL rule that will provide access to the secured Web application, then click OK. For more information about iChain and iChain ACL rules, see Securing Web Applications With Novell iChain .

   Catalog Position: You can use this field to define a folder structure to display the item in the Launch Item gadget. The syntax uses forward slashes, as in the following example:

   /Software/Wordprocessors

   Description: Enter a description to be displayed to the user.

   Icon: If you want to change the display icon, click Modify. You can select an icon from an executable file or .ico file.

   Option: This field lets you specify a URL to a Web site that describes or promotes the item. Use the following syntax:

   <attribute name='brandingURL' value='<URL>'/>

   Replace <URL> with the appropriate URL. Make sure to include the protocol in the URL (for example, http://www.novell.com).

   Enable this Item for Use: Select this option to make the item available to users. If you deselect this option, the item will not be available, even if a user has already purchased the package.

6. Click OK to save the information.