Each time the end user starts the application, WebClient on the end user's machine compares the local version of the application to the latest version on the application deployer's Web site. If the versions differ, WebClient on the end user's machine updates the local version to match the latest version. This is done through the Configuration File Locator.

The config file locator

When the application deployer uses the Application Assembler, the Application Assembler writes the application definition to a configuration file. The end user downloads the file as part of the initial download, and each time the end user starts the application.

As part of defining the application, the application deployer defines the server from which the end user downloads the application configuration file. WebClient uses this description, called the configuration file locator, to access the application configuration file on the configuration file server. For more information, see Host your WebClient Deployment.
Note: To allow the WebClient to continue execution even if the configuration file server is not available, select Allow execution to continue when unable to refresh prowcapp file under the General tab of the Web Application Assembler. See Defining applications in WebClient Application Assembler for more information.

Acceptable-to-run versions

When a new version of the application is defined, a previous version that still runs acceptably can be defined as acceptable to run. For example, an acceptable-to-run version might contain a cosmetic bug that the most recent version fixes.

When the end user starts the application, the end user's WebClient instance downloads the latest application configuration file and checks if any updates are needed. At that point, WebClient might discover that the end user's version is defined (in the application configuration file) as acceptable to run. When this occurs, the end user is offered the option of downloading the newer version. If the end user so requests, WebClient downloads and applies the updates. For more information on acceptable-to-run versions, see Deploy a WebClient Application

Server sharing

WebClient and the application can share a single server. An application server that contains application components downloaded by the WebClient might also contain business logic accessed by the same application. When the WebClient and the application access the same server, they can share a connection. For more information on server sharing, see the Managing application server connections.

Single sign-on

Progress recommends that each server the application accesses be protected with a user ID and password. To simplify access to servers, multiple servers might be protected by the same user ID and password. Facilitating single sign-on for the end user eliminates the need for them to enter their logon information multiple times. If SSO is enabled, the WebClient caches the end user authentication information and grants the application access to this cache.

If the end user desires, WebClient can maintain the authentication cache across end user sessions. This is called persistent caching. The you can disable persistent caching if necessary, and the end user can clear the persistent cache. For more information, see the Implementing single sign-on.