When a company develops its own applications, it can have networks that are used for development, testing, and deployment simultaneously.
The following figure shows the products installed in a shared development and deployment network.
Note: The WebSpeed Broker and the WebSpeed Agents it controls are collectively referred to as the WebSpeed Transaction Server in this figure.
Figure 14. Development and deployment shared configuration
In this configuration, the dedicated Web server machine, Neptune, has two Web servers installed. One Web server handles the development workload, and the other handles the deployment workload. This allows the developers to experiment with the environment without bringing down the deployment side. Each of the Web servers requires its own WebSpeed Messenger, but only the development Web server needs the WebSpeed WebTools.
On the development side, the Messenger routes requests to the NameServer on Triton. Triton's NameServer only has the WebSpeed Transaction Servers on Proteus registered, so it looks there for a Transaction Server to handle the request. Proteus has the WebSpeed Enterprise Transaction Server and either the OpenEdge Enterprise RDBMS or a non-Progress data source installed on it.
On the deployment side, that Messenger routes requests to the NameServer on Galatea. Galatea has the WebSpeed Enterprise Transaction Server installed. The deployment side uses a dedicated machine, Nereid, to hold its data source (that is, the OpenEdge Enterprise RDBMS or a non-Progress data source).
