Sun Java Enterprise System 2005Q4 Technical Overview

Working With Java Enterprise System

Creating business solutions based on Java Enterprise System software involves a number of standard tasks. These tasks vary in scope and difficulty depending on your starting point for the adoption of Java Enterprise System and on the nature of the solution you are trying to create and deploy.

This section discusses two aspects of working with Java Enterprise System: the Java Enterprise System solution life cycle and the various adoption scenarios that are typically involved.

Java Enterprise System Solution Life Cycle

The tasks involved in creating business solutions based on Java ES software can be divided into several phases, as shown in Figure 1–3. The illustration also shows the category of Java Enterprise System user that generally performs the various tasks.

Figure 1–3 Solution Life-Cycle Phases and User Categories

Diagram showing life-cycle phases and the categories of Java
ES users that perform tasks associated with each phase.

The life-cycle phases shown in Figure 1–3 can be divided into the following general groupings:

The solution life cycle and the tasks in each of the phases shown in Figure 1–3 are discussed more fully in Chapter 4, Java Enterprise System Solution Life-Cycle Tasks.

Figure 1–3 shows the Java ES users who typically perform the tasks shown for the life-cycle phases. If you are working with Java ES, your job should fit one or more of the user categories shown in Figure 1–3. The following table describes the skills and background for each category of user.

Table 1–5 Java ES User Categories for Life-Cycle Tasks


Skills and Background 


Business planner

System analyst 

Has general rather than in-depth technical knowledge. 

Understands strategic direction of the enterprise. 

Knows business processes, objectives, and requirements. 

Business analysis 

Technical Requirements 

Logical design 


Is highly technical. 

Has broad knowledge of deployment architectures. 

Is familiar with latest technologies. 

Understands business requirements and constraints. 

Logical design 

Deployment design 

System integrator

Field engineer 

System administrator 

System manager 

Is highly technical. 

Is intimately familiar with information technology environments. 

Is experienced in implementing distributed software solutions. 

Knows network architecture, protocols, devices, and security. 

Knows scripting and programming languages. 

Deployment design 

Deployment implementation 

Specialized system administrator

Delegated administrator 

Support engineer 

Has specialized technical or product knowledge. 

Is familiar with hardware, platforms, directories, and databases. 

Is skilled at monitoring, troubleshooting, and upgrading software. 

Knows system administration for operating system platforms. 


Java Enterprise System Adoption Scenarios

The business needs that lead to the adoption of Java ES vary widely. However, the high-level goal for nearly every Java ES deployment fits into one of the following adoption scenarios:

Each adoption scenario has its own concerns and challenges. Regardless of which adoption scenario characterizes your situation, the solution life-cycle process shown in Figure 1–3 applies. Depending on your adoption scenario, however, the issues you need to address and the resources you need to invest in the life-cycle phases might vary.

The following concerns generally apply in varying degrees to the adoption scenarios:

The following table summarizes the nature of the concerns that apply to each of the Java ES adoption scenarios.

Table 1–6 Java ES Adoption Scenario Concerns

Adoption Scenario 





New system 

Not a concern 

Relatively easy to integrate new components 

Normally a significant concern 

Trade-offs between equipment costs and labor costs. [Using a few powerful computers generally increases equipment costs while requiring fewer IT resources. Using many smaller computers generally decreases equipment costs while requiring more IT resources.]


Can be a major concern 

Need to integrate new components with existing system 

Can be a significant concern 

Can involve significant constraints due to existing equipment 


Not normally a concern 

Might need to integrate new components with existing system 

Might be a significant concern 

Generally requires new hardware with same trade-offs as with a new system 


Can be a significant concern 

Relatively easy to integrate upgraded components 

Relatively minor concern 

Relatively minor concern