Explicitly Defining the UsageServer's Address

If you have user workstations or DeFrame servers that are not in the same subnet as the UsageServer's OSAgent, the OSAgent will not receive the UsageClient's broadcast. This will result the usage-based application failing to launch because the usage session could not be opened. To resolve this problem, you need to explicitly provide the UsageClient with the OSAgent's address.

The UsageClient receives the OSAgent's address from the Launch Item gadget for usage-based desktop (ZENworks for Desktops) applications or from the DeFrame server's Windows registry for thin-client (DeFrame) applications. The following sections provide instructions for explicitly defining the UsageServer's OSAgent's address in the Launch Item gadget and a DeFrame server's registry. If you have both usage-based desktop applications and usage-based thin-client applications, you will need to complete the tasks in both sections.


Adding the UsageServer's Address to the Launch Item Gadget

With desktop (ZENworks for Desktops) applications, you use the Launch Item gadget's UsageServer setting to explicitly define the IP address or host name of the UsageServer you want the UsageClient to connect to. When the Launch Item gadget launches a usage-based desktop application, it passes the IP address or host name is passed to the UsageClient on the user's workstation. The UsageClient then connects directly to the UsageServer's OSAgent.

The Launch Item gadget's UsageServer setting is used for directing only usage-based desktop applications to a specific UsageServer. If you also have usage-based thin-client (DeFrame) applications, see Adding the UsageServer 's Address to a DeFrame Server 's Registry .

To add the UsageServer's address to the Launch Item gadget:

  1. Log in to Novell Portal Services (NPS) as a portal administrator.

  2. Click Administer the Portal.

  3. Click Pages.

  4. Select the page that contains the Launch Item gadget, then click Edit.

    The gadget list includes all the gadgets that are included on the page. The Launch Item gadget should be in this list. However, it will be listed by its display name (for example, Launch Applications), not its gadget name (OD_LaunchItmeGadget).

  5. In the list of gadgets, select the gadget, then click Edit.

  6. In the UsageServer field, enter the IP address or DNS host name of the network server where the UsageServer process is installed.

  7. Click Continue, click Save, then click OK.

  8. Restart the Tomcat servlet engine.


Adding the UsageServer's Address to a DeFrame Server's Registry

With thin-client (DeFrame) applications, the UsageClient on the DeFrame server, not the UsageClient on the user's workstation, is used to track usage. The DeFrame server's UsageClient does not receive the IP address from the Launch Item gadget. Instead, if you want to explicitly define the UsageServer's address, you need to add the IP address or hostname to the DeFrame server's Windows registry.

The UsageServer address in the DeFrame server's registry is used for directing only usage-based thin-client applications to a specific UsageServer. If you also have usage-based desktop (ZENworks for Desktops) applications, see Adding the UsageServer 's Address to the Launch Item Gadget .

To add the UsageServer's address to the DeFrame server's registry:

  1. At the DeFrame server, use regedit.exe to open the registry.

  2. Add the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Novell\on-demand\Objects

  3. Add a String value to the Objects key, using the following information:

    Value Name: -ORBagentaddr

    Value Date: Enter the IP address or DNS host name of the network server where the UsageServer process is installed.

  4. Save the registry changes.