Try OpenEdge Now
skip to main content
WebClient Applications
Deploying an Application : WebClient application updates

WebClient application updates

When you make changes to your application, you simply generate a new version of the application with the WebClient Application Assembler. This creates a new configuration file and any necessary component files and component update files, placing them in a new version subdirectory.
On the end user's machine, WebClient Initializer compares the installed version of the application with the acceptable version in the application configuration file and then prompts the end user as follows:
*If the installed version is acceptable but older than the current version, the Initializer gives the user an opportunity to update to the current (preferred) version or run with the existing version.
*If the installed version is not acceptable, the Initializer gives the user an opportunity to update to the preferred version.
If you use:
*IntelliStream, and the end user chooses to update, WebClient Initializer starts WebClient to perform the IntelliStream update and run the application.
Depending on how you implemented your security, the end user might be prompted for authentication information and verification to download the modified files. For more information, see Designing Security and the Application components.
Note: A major benefit of IntelliStream is that only the individual modified files are downloaded during an update. The WebClient Application Assembler determines what files are modified according to an algorithm. To optimize this process, Progress Software Corporation strongly recommends you use the Generate MD-5 option when you compile your r-code. For more information, see the Determining if a resource was modified.
*An external installer to update the application, you can re-use the Web page and logic for initially installing your application, or you can provide a separate application-specific Web page and logic.
For any case where the user chooses to update the application to the preferred version, the Initializer opens a Web browser on the user's system using the application update URL specified in the application configuration file, and then exits. At this point, the user can continue with the update over the Web.
* Updating procedure libraries
* Suppressing the WebClient Application Update dialog