WebSpeed
Installation and
Configuration Guide
DataServer and WebSpeed Architecture
You have the option of having a local or a remote DataServer. A local DataServer runs on the same machine as the WebSpeed Agents, that is, on the machine where you install the WebSpeed Transaction Server. A remote DataServer runs on a different machine from the WebSpeed Agents, which could also be the machine where your data source resides. This is not a requirement, however.
Figure 10–1 shows a DataServer that is local to the WebSpeed Transaction Server. The database also resides on this machine.
Figure 10–1: The Local DataServer
![]()
Figure 10–2 shows one possible configuration for the remote DataServer where a WebSpeed Agent accesses a remote DataServer. Here, the database and the DataServer are running on the same machine. The schema holder is local to the WebSpeed Transaction Server to increase performance.
Figure 10–2: Remote DataServer
![]()
The figures show a schema holder on the same machine where your Agents run. A local read-only schema holder gives you better performance. However, you might decide that you want your schema holder on a separate machine to make better use of processing resources.
Note that none of the configuration diagrams include a Web server. The Web server plays no role after passing the initial Web request for data to the WebSpeed Messenger. Much like a typical Progress client, the WebSpeed Agent interacts with the DataServer, which in turn passes queries and data requests to the database management system.
You can integrate DataServers for ODBC and ORACLE into the Progress Explorer administrative framework, which allows you to have a single administrative system and take advantage of the NameServer’s load balancing. Alternately, the WebSpeed Agents can access DataServers that cannot be managed by the AdminServer, such as the Progress/400 DataServer.
There are variations on these configurations that allow you to combine Windows NT and UNIX platforms or to distribute the components using vendor networking (for example, ORACLE’s SQL*Net). The DataServer architecture that allows you to access DB2/400 data is more complex as it is integrated into the native OS/400 architecture. See your Progress DataServer Guide for more information. The DataServer Guides present configuration information in traditional client/server terms; when reading this material for implementing WebSpeed, substitute WebSpeed Agent for Client.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |