Chapter 1 Evaluation Scenario Overview

This chapter covers the goals of this deployment scenario, the architecture used in this deployment scenario, and the procedures you follow in this deployment scenario to install, configure, and use Sun Java^™ Enterprise System.

About Java Enterprise System

Java Enterprise System is infrastructure software that supports a wide range of enterprise computing needs, such as creating a secure intranet portal to provide the employees of an enterprise with secure access to email and in-house business applications.

Java Enterprise System is composed of software components, such as Sun™ ONE Directory Server and Sun ONE Identity Server. To meet the computing needs of different enterprises, Java Enterprise System components can be combined in many different ways.

Each enterprise assesses its own needs and plans its own deployment of Java Enterprise System components. The optimal deployment for an enterprise depends on the types of applications that Java Enterprise System is supporting, the number of users, the kind of hardware that is available, and similar considerations.

Java Enterprise System supports custom, distributed, enterprise applications, but it also provides many end-user services without custom programming. This deployment example describes how to configure a set of core shared network services without custom application programming.

For more information on Java Enterprise System technical concepts and terminology see Java Enterprise System Technical Overview (http://docs.sun.com/doc/817-5085).

About the Evaluation Deployment Scenario

This deployment example describes how to install Java Enterprise System components on a single computer in order to evaluate the system. In addition to installing Java Enterprise System, this deployment example describes how to configure system components to work together and provide basic enterprise services.

This section describes how the deployment architecture for the evaluation deployment example was developed.

Evaluation Use Cases

The system evaluation described in this deployment example includes the following use cases:

Installer use case: install the Java Enterprise System components on one machine using default values.

Component instance configuration use case: use Java Enterprise System administrative interfaces to configure component instances.

Administrator use case: provision a single end user.

End user use case: interact with mail, calendar, and portal services to demonstrate successful installation and configuration of system components.

Administrator use case: configure Identity Server single sign-on (SSO).

End user use case: interact with mail, calender, and portal services to demonstrate successful configuration of SSO.

Administrator use case: configure proxy authentication.

End user use case: use the portal desktop to interact with the mail and calendar services to demonstrate successful configuration of proxy authentication.

These use cases show you how to set up a working Java Enterprise System, with messaging and calendar services, and end users who can access these services.

Deployment Scenario

This section describes the deployment scenario developed for the evaluation use cases listed in Evaluation Use Cases. The deployment scenario consists of two pieces, the logical architecture and the system requirements.

Logical Architecture

The logical architecture identifies the Java Enterprise System components that provide the services described in the use cases. The logical architecture developed for the evaluation use cases is illustrated in Figure 1-1.

The arrangement of the components in Figure 1-2 represents the following characteristics of this logical architecture:

Application Server and Directory Server support the other components. For this reason, these servers are placed below the other servers.

Portal Server and Identity Server run in Application Server’s web container. For this reason, these servers are placed directly above Application Server.

Portal Server is accessed directly by end users. For this reason, this server is placed at the top.

Messaging Server and Calendar Server do not depend on Application Server’s web container. These servers run in their own web containers. Messaging Server and Calendar Server do depend on services provided by Directory Server. For this reason, these servers are placed higher than Application Server and Directory Server, but not directly above any other server.

System Requirements

The system requirements specify important characteristics of the deployment that are not specified in the logical architecture. The system requirements for the evaluation deployment example are listed below:

Load and performance requirements: None

Availability requirements: None

Security requirements: Authentication, single sign-on

Serviceability requirements: None

Scalability requirements: None

These requirements are appropriate for evaluating Java Enterprise System. The deployment scenario for a production deployment typically includes specifications for all of these requirements.

Evaluation Deployment Example Deployment Architecture

The deployment architecture is a plan for deploying the logical architecture in such a way as to meet the system requirements. Figure 1-2 shows the deployment architecture for the evaluation deployment example. This deployment architecture combines the logical architecture that is shown in Figure 1-1 and the system requirements that are specified in System Requirements.

Figure 1-2 shows the same set of components as Figure 1-1. The components are all installed on a single computer. The relationships among the components are unchanged.

The deployment architecture used for the evaluation deployment scenario is not a production architecture. This architecture does not address many of the considerations you face in designing and configuring a production deployment, such as security considerations, scalability, and high availability.

Evaluation Scenario Procedure Summary

This deployment example describes how to set up a Java Enterprise System environment that supports the use cases listed inEvaluation Use Cases. The major steps covered in this document are as follows:

Implementing the deployment architecture by installing the components one computer. This step uses the Java Enterprise System installer. The installer configures many of the components. This step is covered in Chapter 2, "Installing the Java Enterprise System Evaluation Deployment."

Configuring the Java Enterprise System components that the installer does not configure. The configuration sequence includes steps for starting and verifying the component instances that are configured by the installer. This step is covered in Chapter 3, "Configuring Java Enterprise System."

Configuring Identity Server as a general-purpose user provisioning tool. This step is covered in Chapter 4, "Provisioning a Java Enterprise System User."

Provisioning a Java Enterprise System end user and giving this user access to Java Enterprise System messaging and calendar services. This step is covered in Chapter 4, "Provisioning a Java Enterprise System User."

Logging in as a Java Enterprise System end user and separately accessing the portal desktop, messaging, and calendar services. This step is covered in Chapter 5, "Verifying End User Access to Java Enterprise System Services."

Configuring Identity Server single sign-on (SSO). This step is covered in Chapter 6, "Configuring Single Sign-On."

Logging in as a Java Enterprise System end user and verifying SSO. This step is covered in Chapter 6, "Configuring Single Sign-On."

Configuring proxy authentication, which allows the portal desktop direct access to the messaging and calendar services. This step is covered in Chapter 7, "Configuring Proxy Authentication."

Logging in to the portal desktop as a Java Enterprise System end user and verifying that you can use the messaging and calendar services directly from the portal desktop. This step is covered in Chapter 7, "Configuring Proxy Authentication."

Goals of the Evaluation Deployment Example

By following the procedures in this deployment example, you discover how Java Enterprise System supports an organization. You learn how to configure Java Enterprise System components to deliver services to the organization’s users. More specifically, you will become familiar with these tasks:

Installing Java Enterprise System components

Using Java Enterprise System administration tools

Configuring Java Enterprise System components to work together as a system

Specifying the Directory Server Lightweight Directory Access Protocol (LDAP) organization that is supported by a Java Enterprise System deployment

Starting and stopping Java Enterprise System components in correct sequence

Provisioning a Java Enterprise System user

Configuring system-wide single sign-on (SSO)

Accessing end-user services such as the portal desktop, Messaging Server’s web interface (known as Messenger Express), and Calendar Server’s web interface (known as Calendar Express).

For more information on installing and configuring Java Enterprise System, see the Java Enterprise System Installation Guide.

Previous Contents Index Next
Sun Java Enterprise System 2003Q4 Deployment Example Series: Evaluation Scenario