The OpenEdge WebClient enables you to build and distribute updates for web-based OpenEdge applications.

By using the WebClient, you can take a Web-enabled OpenEdge application, deploy and configure its back-end components as desired, package its front-end components, and host the packages on a server you can package updates to the application front end and place them on a server as well. The end user, typically using a Web browser, can request to run the application. In response, WebClient downloads the initial front-end package, installs and runs the application, downloads update packages, and installs the updates—all with a high degree of transparency.

WebClient vs. standard ABL client

There are several factors that you should consider to determine if the WebClient is right for you. First compare the WebClient to a standard ABL client.

Feature WebClient Standard ABL client
Execution Contains no compiler; runs as a reduced-size executable. Compiles source and runs as a complete ABL client executable.
Data access Supports temp-table access, but does not support direct access to the OpenEdge database or DataServers; relies on a connected application server to provide indirect access to all databases and DataServers. Supports direct access to all data objects, as well as indirect access to databases and DataServers using a connected application server.
Customization Cannot be customized using OEBuild. Can be customized using OEBuild.
UI Supports only the graphical user interface (GUI) and batch modes in Windows. Supports all ABL user-interface modes.
Launch method Is typically launched by accessing a Web page or a shortcut that runs the WebClient Initializer, which performs certain housekeeping tasks and automatically executes WebClient on the end user's behalf. The ABL procedures that the application comprises do not have to be installed on the end user's machine prior to run time. Is typically launched by executing a script or shortcut you provide that executes the ABL client on the end user's behalf. The ABL procedures that the application comprises must be installed on the end user's machine prior to run time.

WebClient

WebClient is specifically designed for:

  • Application service providers (ASPs) renting out applications over an extranet.
  • Corporate information technology (IT) departments deploying applications internally over a corporate intranet.

ASP

As an ASP, you rent applications to end users, who install and run the applications over the Web or an extranet. Your end users might perform tasks like the following:
  • Identifying the application — End users identify the application on your Web site as a likely business solution through a Web search.
  • Evaluating the application — End users sample the application through a live demonstration, installed and executed directly on their systems over the Web. You make this option available by providing the application in a demo mode, complete with online documentation and sample data.
  • Subscribing to the application — You allow end users access to a measured level of application functionality based on a price-driven subscription agreement. You maintain and administer the application's back end (its servers, databases, and so on).
  • Downloading, installing, and launching the application — Your Web site grants end users access to the application, including the purchased level of functionality controlled by a version-based license. This allows them to download and install the application directly from a server, complete with all supporting OpenEdge components. End users then run the application, which access the business logic on your back-end server.

IT department

As an IT department, you install and run your application entirely over a corporate intranet. You or your end users might perform tasks similar to the following:
  • Identifying the application — You search the Web to identify an application to deploy via WebClient.
  • Evaluating the application — Your end users sample the application through a live demonstration, installed and executed directly on their systems over the Internet.
  • Purchasing the application — You buy the application.
  • Deploying the application — You deploy the application on a local machine.
  • Downloading, installing, and launching the application — Your end users access the local machine to download, install, run, and update the application, as in the ASP model.

WebClient files and software

The following files and software support your WebClient application deployment:

  • WebClient executable ( prowc.exe ) — The WebClient main executable, responsible for running the application on the user's machine.
  • WebClient Initializer ( prowcini.exe ) — The program responsible for coordinating the installation and execution of a WebClient application. The Initializer is installed with WebClient.
  • WebClient Application Assembler ( prowcappmgr.exe ) — A utility used to define the application to WebClient and to package the front end of the application for downloading.
  • WebClient Deployment Packager (contained within prowcappmgr.exe ) — A utility used to modify the deployment configuration for an application.
  • WebClient Application Manager ( prowcam.exe ) — A utility for customizing and troubleshooting your WebClient applications on the end user's machine. It is typically used when the end user talks with your technical support staff.
  • Application Configuration ( .prowcapp ) file — The configuration file created by the WebClient Application Assembler and downloaded to the end user's machine at the initial download and each time the end user starts the application. This file provides WebClient with all the information it needs to know about the application.
  • WebClient project ( .wcp ) file — The file that contains the WebClient application install definition for the latest version of an application.
Note: In Windows Explorer, if you double-click on a project file, the WebClient Application Assembler starts and opens that project definition.
  • Microsoft Cabinet ( .cab ) files — Files into which the procedure files, image files, etc., that make up the front end of the application are placed to prepare them for downloading to the end user's machine.
  • Microsoft Authenticode™ Technology — The software that creates and validates digital signatures.
  • Test-certificate generator ( maketestcert.bat ) — A batch file that simplifies creating test public-key certificates used for testing digitally signed applications.
  • WebClient application — The application to be deployed through WebClient.

WebClient versus WebClient applications

The WebClient itself is separate from the applications that you deploy with it. When used alone, WebClient refers to the WebClient executable and the rest of the infrastructure on which a deployed application runs. WebClient application refers to the deployed application itself.