WebSpeed
Developer’s Guide
An Overview of WebSpeed
The WebSpeed development and deployment environment consists of four major software components:
- The WebSpeed Workshop, which includes the following:
- AppBuilder, a graphical tool that contains wizards, templates, compilers, and editors for building Web Objects. The AppBuilder is also a launching point for various database administration tools (the Data Dictionary, for example).
- WebTools, a set of browser-based utilities.
- WebSpeed Development Server, actually a WebSpeed Transaction Server that responds to requests, executes WebSpeed applications (also known as Web objects), and delivers HTML pages to the Web Server.
- A Web Browser, the client software where the request for WebSpeed services originates. You use a browser to test and run your WebSpeed applications. You also use a browser to run WebTools.
- A Web Server, the software that passes requests between a browser and the WebSpeed components. The Web Server receives requests for WebSpeed services and it passes the request to a the WebSpeed Development Server. When the request has been processed by WebSpeed, the Web server returns an HTML page back to the browser.
- A Data Source, a Progress database server or any of a wide variety of other database servers. You can also use a SmartDataObject as a data source. See the Progress AppBuilder Developer’s Guide for information on creating SmartDataObjects.
NOTE: Only the first item, WebSpeed Workshop, is included in the WebSpeed product. However, depending on your licensing option, you might also have a Progress data source as well.For more information about WebSpeed components and their distribution in a network environment, see WebSpeed Architecture." Also see the WebSpeed Installation and Configuration Guide for more information on configuring WebSpeed and on system requirements.
Figure 1–1 shows the relationship between the components in the WebSpeed development environment.
Figure 1–1: Components of the WebSpeed Development Environment
![]()
Basically, you use WebSpeed AppBuilder connected to a data source to create Web objects. A Web object may, for example, perform a query on the data source. When you test or run Web objects, the AppBuilder spawns a browser. The broken line in the diagram indicates that there is no sustained connection between the browser and the AppBuilder. The browser passes the request to the Web Server and the Web Server sends the request to the WebSpeed Development Server. The WebSpeed Development Server, which is also connected to the data source, executes the Web object. The Web object formats its results as an HTML page. The WebSpeed Development Server passes the HTML page back to the browser through the Web Server.
You can start the WebTools utilities directly from a browser by supplying a URL. Or, you can start WebTools from the AppBuilder tools menu. In the later case, the AppBuilder merely spawns a browser. The browser then generates a request to the Web Server, which passes it to the WebSpeed Development Server for execution. The Development Server generates the Web page that is returned to the browser through the Web server.
All the components of the WebSpeed Development Environment can reside on a single machine, or on multiple machines in a network environment. However, there are some restrictions on a network deployment of WebSpeed. For example, the WebSpeed Messenger, a component of the WebSpeed Development Server, must reside on the same machine as the Web Server. For more information about requirements for running WebSpeed, see the WebSpeed Installation and Configuration Guide .
For more information about WebSpeed AppBuilder and WebTools, see Overview of WebSpeed Tools."
For more information about the WebSpeed architecture, see WebSpeed Architecture."
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |