Sun Java Enterprise System 2005Q4 Technical Overview

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