Technical Case Study: Sun Java Enterprise System SunWeb 4.0

Key Objectives of SunWeb 4.0

The following table lists the key objectives of the SunWeb 4.0 deployment. These objectives might be similar to your own.

Table 1–2 Key Objectives of SunWeb 4.0

Objective 

Description 

Integration and consolidation

SunWeb resources were split across many systems and the integration and consolidation of services was a key driver for the SunWeb 4.0 deployment. The SunWeb 4.0 portal integrated Portal Server Secure Remote Access, mobile access, communication channels (mail and calendar), a blogs channel, and the SunWeb portal desktop into one common platform. This integration of services onto one platform required substantial modification to the existing architecture. 

Single sign-on functionality was also implemented to provide single sign-on between Portal Server with Access Manager to other applications. 

Multitier architecture implementation

A key objective of the deployment was to implement a multitier reference architecture to meet new scalability needs and to decouple the Portal Server, Access Manager, and Directory Server deployment for the multitier architecture. 

Software upgrade

A software upgrade was necessary to leverage the latest functionality in Java ES components and the SolarisTM Operating System (Solaris OS). The SunWeb 4.0 framework implemented Sun Java Enterprise System 2005Q1 and Solaris 10 OS with zones (see Software in SunWeb 4.0).

Hardware upgrade

A hardware upgrade was long overdue. The SunWeb 4.0 deployment moved from shared hardware to dedicated Sun FireTM x64 servers running Solaris 10 OS, demonstrating a reference architecture with zones on AMD OpteronTM processors (see Hardware in SunWeb 4.0).