Sun Java System Reference Configuration Series: Portal Service on Application Server Cluster

Chapter 1 Introduction to the Portal Service Reference Configuration

To meet the needs of portal service customers, Sun is developing a series of portal service reference configurations that use Sun JavaTM Enterprise System (Java ES) components. Each reference configuration is a tested, documented, and performance-tuned portal service solution that consists of a specific deployment architecture that uses a specific network topology and a set of recommended hardware.

This guide documents the Portal Service on Application Server Cluster reference configuration on the SolarisTM Operating System (Solaris OS). This reference configuration is designed to meet specific business and technical requirements, and covers the following aspects of the software solution:

This chapter introduces the Portal Service on Application Server Cluster reference configuration and includes the following sections:

Objectives of the Reference Configuration

The purpose of a reference configurations is to enable customers to deploy proven technology solutions with a minimum of design time and implementation difficulty. A reference configuration starts with a business problem and finishes with a deployed solution that meets specified business and technical requirements.

The Portal Service on Application Server Cluster reference configuration responds to the business needs of medium-sized organizations for portal services. The reference configuration provides a basic portal service architecture that organizations can customize with their own portal content and integrate with their existing applications and content management systems. This reference configuration guide explains the basic solution architecture and describes how to implement it. Once you have successfully installed, configured, and verified a reference configuration, you can customize it to meet your specific needs.

How to Use This Guide

This guide is the first of a number of portal service reference configuration guides. Each guide documents a different reference configuration architecture. The following table summarizes the steps you take, using this guide, to adopt and implement the Portal Service on Application Server Cluster reference configuration.

Table 1–1 Development and Deployment Cycle of the Reference Configuration


Covered In 

1. Determine if the reference configuration (or one of its deployment options) meets your organization's needs.

Business and Technical Requirements discusses the requirements that the Portal Service on Application Server Cluster reference configuration is designed to meet.Deployment Options for the Reference Configuration presents deployment options that might better meet your needs.

2. Understand the reference configuration deployment architecture.

Chapter 2, The Reference Configuration Deployment Architecture describes the Portal Service on Application Server Cluster architecture.

3. Modify the detailed deployment specifications.

Deployment specifications contain the low-level, detailed information needed to deploy the reference configuration in your environment. You need to modify the deployment specifications that appear in this guide by substituting the values you will be using in your own environment. 

Chapter 3, “Deployment Specifications,” describes how to develop the actual values that you use in the implementation procedures.

4. Implement the deployment architecture.

Four chapters in this guide describe the installation and configuration procedures for the four implementation modules of the Portal Service on Application Server Cluster architecture. 

The intent of this guide is to describe the portal service on Application Server Cluster reference configuration in such a way that you can re-create the architecture in your own environment. With very little adaptation, the information presented in this guide can be used to help you deploy your own portal service solution.

Business and Technical Requirements

This section describes the business and technical requirements that are the basis for the Portal Service on Application Server Cluster reference configuration. You can use the information in this chapter in the following ways:

This section divides the business and technical requirements into two categories:

Basic Functional Requirements

This section describes the basic features that the reference configuration provides. These features will meet the portal service needs of most medium-sized organizations. The basic feature requirements are the following:

Quality-of-Service Requirements

In designing a successful software solution, you must establish the relevant quality-of-service requirements for your business needs. Five important service qualities are used to specify such requirements, as summarized in the following table.

Table 1–2 Reference Configuration Service Qualities

Service Quality 



A measure of response time and latency with respect to user load conditions. 


A measure of how often a system's resources and services are accessible to end users (the uptime of a system).


A complex combination of factors that describe the integrity of a system and its users. Security includes the physical security of computer systems, network security, application and data security (authentication and authorization of users), as well as the secure transport of information. 


The ability to add capacity to a deployed system over time. Scalability typically involves adding resources to the system but should not require changes to the deployment architecture. 


The ease by which a deployed system can be maintained, including monitoring the system, repairing problems that arise, and upgrading hardware and software components. 

The requirements regarding these service qualities have a big impact on how application and infrastructure components are deployed in a physical environment.

The following sections describe the quality-of-service requirements upon which the Portal Service on Application Server Cluster reference configuration is based:

Performance Requirements

A portal service is an end-user service, and a fairly high level of performance (an acceptably short response time) is expected. The performance of Sun Java System Portal Server is generally measured by the response time of the standard channels that are available in the default desktop sample. The reference configuration is designed to provide a response time under two seconds for these channels at peak load levels. In a typical deployment, however, response time is dependent upon not only the portal service, but also the back-end applications that it aggregates.

Availability Requirements

Availability is a crucial requirement for a portal service. In many organizations, the portal is the employee's (or the customer's) gateway to critical information that is aggregated and displayed by the portal service. If the portal services fails, the employee or customer has no other way to access the information needed to conduct business.

Portal services can be classified according to the following levels of availability requirements:

The Portal Service on Application Server Cluster reference configuration is designed to provide service availability with both user session state and application session state availability. However, if application session state availability and/or user session state availability are not requirements of your organization, you can choose deployment architecture options that do not include them.

The reference configuration is not designed to sustain the complete failure of a data center. To overcome such failures, the portal service needs to be distributed across multiple locations. This kind of implementation is out of scope for the reference configuration.

The availability of a system should be measured from the user's perspective. Users care about how often a system fails and how long it takes to recover. There is no difference between a system being unavailable due to a systems failure or because of a scheduled maintenance window. Consequently, when measuring availability and when designing a highly available system, both planned and unplanned downtime needs to be considered. The reference configuration is designed to have no single points of failure. If implemented in conjunction with appropriate operational procedures and staffing, the reference configuration should result in less than one hour of unplanned downtime per year (99.99 percent availability).

Security Requirements

Portal services deliver varied content to varied users, often over the public Internet. In many cases, the content is confidential and should only be viewed by authorized users. Hence, the following security features are included in the basic feature requirements for portal services:

In addition, a more general set of security requirements is needed to provide secure access to confidential data. These requirements are shown in the following table.

Table 1–3 Security Requirements for Portal Services

Security Category 



  • Housed within a secure data center to which only authorized personnel have access


  • Internet firewall protection

  • Subnet design that secures vital services

  • Secure transfer and storage of data


  • All data stored in a manner that follows applicable regulations, corporate security policies, and corporate privacy policies


  • Authentication must be secure

  • Compatible with Secure Socket Layer (SSL)-enabled browsers and Transport Layer Security (TLS)

  • Strong encryption

The Portal Service on Application Server Cluster reference configuration is designed to support these security requirements.

Scalability Requirements

Most organizations anticipate growth in their user populations and want to know that their portal service can grow along with the size of their user populations.

As a result, no computer system should be more than 80 percent utilized under daily peak load. Also the deployed system should accommodate long-term growth of 10 percent per year.

While there are upper limits to how much any system can scale, due to the increased interactions among its components and the limitations of the network infrastructure, the Portal Service on Application Server Cluster reference configuration is designed to be easily scalable up to these limits.

Serviceability Requirements

Because a portal service is normally critical to conducting business, it must be maintained with minimal disruption and downtime.

Common servicing operations include database backups, replacement of applications and system software, upgrades, and other maintenance. Analyzing the solution's requirements for such servicing, and techniques to facilitate the servicing, should be a priority when you design the system.

For example, on an intranet-oriented portal, users are generally most active during the 8:00 a.m. to 5:00 p.m. working hours. This means all system servicing operations can be done after hours. However, if your organization is geographically distributed over multiple time zones, or users need 24–by-7 access to the system, there is no servicing window. Instead, the system needs to be designed so that all maintenance operations can be done with the system in operation or having little impact on the system's availability. In addition to an appropriate deployment architecture, it is necessary to have well-defined and tested operational procedures that ensure minimum downtime.

The Portal Service on Application Server Cluster reference configuration is designed to maximize serviceability, both with respect to scaling the portal service and upgrading software components in the configuration.