Try OpenEdge Now
skip to main content
WebClient Applications
Deploying an Application : Defining applications in WebClient Application Assembler : General tab

General tab

The General tab, shown here, provides basic information about the application, including startup information:
*Click Locator to open the Configuration File Locator Definition dialog. With this dialog, you specify the Internet server for the application configuration file and you define the server's authentication options:
*Click Versions to open the Versions dialog. With this dialog, you specify which versions of your application are acceptable to run:
*Click Change to open the 32-bit User Upgrade dialog box. With this dialog box, you define the action that WebClient should take when an end-user on a 64-bit Windows machine has an older 32-bit version of the application installed.
Note: Change is enabled only when both the 32-bit and 64-bit Platform check boxes are selected.
*Each time the end user starts the WebClient application, the WebClient Initializer checks the Web server that is hosting the application configuration file (application-name.prowcapp) to determine if an application update is available. If the Web server is not available, the WebClient application terminates. To allow the WebClient application to continue execution, even if it is not able to contact the hosting Web server, select Allow execution to continue when unable to refresh prowcapp file.
This option can be useful in areas where network connectivity is poor or sporadic. The downside is that if there is a new version of the application available and the server hosting the application configuration file is down unexpectedly, then clients will attempt to continue running with the old version, even if the old version is now incompatible. Application vendors need to consider this and manage it within the application.