Sun Java Enterprise System 2005Q4 Technical Overview

Logical Architecture for Example Scenario

A logical architecture for delivering the portal, communication, and identity services identified in Table 2–4 using Java ES components is shown in the following figure. The architecture treats logically distinct configurations of Messaging Server as separate components because of the distinct services they each provide.

Figure 2–7 Logical Architecture for Enterprise Communications Scenario

Diagram showing logical architecture for the example enterprise
communications scenario.

The components are placed within a horizontal dimension that represents standard logical tiers and within a vertical dimension that represents infrastructure service levels. The interactions between the components depend on their functions as distributed infrastructure services (interactions between infrastructure service levels) or their roles within a tiered application architecture (interactions within and between logical tiers).

In this architecture, Access Manager, accessing user information stored in Directory Server, is the arbiter of single sign-on authentication and authorization for Portal Server and other web-based components in the presentation tier. Messaging Server components include a message store (Messaging Server-STR) in the data tier, sending and retrieving components in the business services tier, and an HTTP access component and Communications Express in the presentation tier.

The logical architecture also shows the infrastructure service dependencies between the various Java ES components. Portal Server, for example, depends on Communications Express for its messaging and calendar channels and on Access Manager for authentication and authorization services. These components, in turn, depend upon Directory Server for user information and configuration data. A number of components require web container services provided by Web Server.

For more information about Java ES solution logical design, see the Sun Java Enterprise System 2005Q4 Deployment Planning Guide.