Preparing the Deployment Scenario

The deployment scenario for the SunWeb 4.0 deployment is a combination of the following:

• The logical architecture, which identifies the Java ES components and other software needed to provide the services described in Detailed Service Requirements.

• The quality of service requirements, which specify the performance required from the Java ES components and other software named in the logical architecture.

Preparing the Logical Architecture

The Java ES components needed to provide the services listed in Detailed Service Requirements are diagrammed in the following figure. This set of components is prepared by examining the list of services required in the SunWeb 4.0 deployment and determining which Java ES component will be used to provide the services.

Figure 3–1 SunWeb Deployment Logical Architecture

Notice that the logical architecture includes Java ES components, represented as boxes with solid outlines, and non-Java ES software, represented as boxes with dashed outlines. Non-Java ES software is used as follows:

• The Portal Content Delivery API is installed as part of the SunWeb deployment, and supports interaction between the SunWeb deployment and the content management system (CMS).

• The CMS is already running on the main corporate network. The SunWeb components are configured to interact with the CMS. The CMS appears in the logical architecture's data tier, but the CMS is more a service used by the SunWeb components than a part of the actual SunWeb deployment.

• The logical architecture also includes existing corporate applications and web sites. These existing applications and web sites, including the corporate messaging and calendar services also running already on the main corporate network. These applications and web sites are represented in the logical architecture's business services tier, but they play a role similar to the CMS. The corporate applications and web sites are more accurately regarded as services used by the SunWeb components than as part of the actual SunWeb deployment.

• The logical architectures shows SafeWord, which is already running on the main corporate network. Access Manager is configured to interact with SafeWord in order to authenticate login requests from remote users. (Access Manager ships with a module for this purpose.) SafeWord, too, is more accurately regarded as a service used by the SunWeb components than as a part of the SunWeb deployment.

Reviewing the Quality of Service Requirements

The logical architecture identifies the Java ES components that provide the services named in the requirements, but does not tell you how you should install the components on your network. In a typical production deployment you satisfy quality of service requirements such as response time, service availability, and service reliability by installing and configuring multiple instances of the components and distributing the components among several computers. For example, you could provide failover capability for your portal service by configuring multiple instances of Portal Server on multiple computers behind a load balancer.

To review the quality of service requirements for the SunWeb deployment, see the following sections in Chapter 2:

• Availability Requirements

• Performance Requirements

• Scalability Requirements

• Security Requirements