Technical Case Study: Sun Java Enterprise System SunWeb 4.0

Capacity Requirements

SunWeb provides services to two primary classes of internal users: those accessing SunWeb when connected to the corporate network (SWAN) and those accessing SunWeb using the public Internet and secure remote access gateways (SRA). SWAN users connect directly to the portal server through a load balancer. Internet users (SRA) access load-balanced gateways that connect to the portal servers for serving content and other applications.

Each class of user has access to the same set of services, which includes e-mail, blogs, search, file access, content, tools, applications, and a personalized desktop. Access to specific services, tools, and content is based on an employee's role at Sun (executive, people manager, individual contributor, and so on). The following table lists the approximate number of users in each class.

Table 2–1 Number of Users of SunWeb Services

Service Class 

Number of Users 

Local users logging in to SunWeb from a computer connected to SWAN (includes access via VPN) 

Approximately 19,000–21,000 unique users per day 

Remote users logging in to SunWeb from a computer or mobile device not connected to SWAN (SRA) 

Approximately 1,700–2,100 unique users per day 

The SunWeb user base is expected to grow as more applications are integrated into the portal. For the initial deployment of SunWeb 4.0, the requirement was that the system be scalable to support 6,000 concurrent users. To meet future needs, the deployed system must be scalable to accommodate an increasing number of users, with the growth rate for users expected to be 10-15% per year.