Try OpenEdge Now
skip to main content
WebSpeed Essentials
Running and Deploying WebSpeed Applications : Distributed WebSpeed environments

Distributed WebSpeed environments

The pieces of the WebSpeed architecture do not have to reside on a single machine. However, there are dependencies that you must consider before installing your own WebSpeed environment. The way you choose to distribute your environment might affect how your application performs. You should consider this during the early stages of your design process, as well as the later stages when you are planning your deployment strategy.
The following sections show sample WebSpeed environments and briefly describe how they should be installed and managed. They concentrate on the WebSpeed components, but there are other considerations as well. For example, Securing your WebSpeed server machine discusses the addition of firewalls to a WebSpeed environment.
After you have installed your environment, you must consider the interdependencies when you write startup routines for your environment. Some components cannot start correctly unless they can communicate with some other component. These dependencies shape proper startup routines. The brief startup sequences in the following sections can help you avoid common errors that occur when components are started before everything they depend on has started.
Note: Some components can be configured to start automatically when other components start.
For example, before launching a WebSpeed application, you should make a data source available to the WebSpeed broker and agents for your application. When you shut down your application, the broker and agents should shut down before the databases. If agents lose their database connections prematurely, you might have to complete the shutdown manually.
In most cases, when a machine or component fails, you only have to restart that machine or component. If your data source in a complex distributed configuration fails, data integrity concerns might make it necessary to bring down other components before restarting your data source.
The examples of WebSpeed configurations in this section are meant to illustrate which components must reside on the same machine and how to establish links between the various WebSpeed components on different machines. You can adapt these examples to your needs, as described in the following sections.
* Single-machine configuration
* Development network with a central WebSpeed machine
* Development network with a dedicated Web server
* Multiple LAN development environment
* Deployment configuration with a dedicated Web server
* Development and deployment shared configuration