When WebClient is installed, it creates registry entries based on the input from the user and the type of installation.

Administrator instances use the following registry key:
HKEY_LOCAL_MACHINE\Software\PSC\WebClient
Note: If you are installing an administrator instance of a 32-bit application on 64-bit Windows, maintain keys in the 32-bit subnode of the registry. If you use a 32-bit process to maintain the registry, it is transparent. If you use a 64-bit process to maintain the registry, the 32-bit subnode is:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\PSC\WebClient
Personal instances use the following registry key:
HKEY_CURRENT_USER\Software\PSC\WebClient

These registry key values specify path settings for accessing WebClient functionality, and user-supplied options for running WebClient. You must be aware of these registry entries when you write your application installation. The path settings include two values that you can use to set up application shortcuts and a default setting for your application installation directory. For information on programmatically checking the installation type, see the Checking application registry access.

The following table lists the registry key value names as they appear in the registry and provides a description of the information that appears under Data in the registry.

Table 1. Registry entries made by WebClient
Registry key value name Data
ProwciniPath The complete path, including filename, of the WebClient Initializer executable.
ProwcamPath The complete path, including filename, of the WebClient Application Manager executable.
ApplicationsPath Default path on the end user's machine that you can use as a root directory to install your WebClient application. The WebClient installation allows the end user to specify this location.

Using this registry value in your application installer eliminates the need to prompt the users for information about where they want the application installed.

As a result, this creates a more silent application installation. However, you do not want to use this registry value if there might not be enough space on a drive to install the application.
You can provide a shortcut for the user to launch the application directly from Windows after the application is initially installed. This shortcut executes the WebClient Initializer, passing an application configuration file reference to it. You must invoke the application this way to take advantage of the automatic update capabilities of WebClient. When you set up the shortcut in the installer, use the following command syntax to execute WebClient Initializer:
ProwciniPath{ "<VendorName>/<ApplicationName>" -s }
ProwciniPath

The complete path, including filename, to the WebClient Initializer executable. This pathname is stored by the WebClient installer as the ProwciniPath registry key value.

<VendorName>/<ApplicationName>

A unique identifier for an application. The values for VendorName and ApplicationName match the values you specify in the General tab of the WebClient Application Assembler when you define your application. WebClient Initializer uses these values to indirectly locate the application configuration file.

CAUTION: When you change the location of your application configuration file, the user's shortcut no longer works. Tell your users to start the application from the application Web page to automatically update the location of the application configuration file. After updating the location, the shortcut works again.
The WebClient installer also installs a shortcut for running the WebClient Application Manager. You can create a separate shortcut that runs the WebClient Application Manager with your application highlighted. To set up this application-dedicated shortcut, use the following command syntax:
ProwcamPath "<VendorName>/<ApplicationName>"
ProwcamPath

The complete path, including filename, to the WebClient Application Manager executable. This pathname is stored by the WebClient installer as the ProwcamPath registry key value.

<VendorName>/<ApplicationName>

A unique identifier for an application. The values for VendorName and ApplicationName match the values you specify in the General tab of the WebClient Application Assembler when you define your application. WebClient Application Manager uses these values to access information about the WebClient Application.