| |
| Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Migrating and Redeploying Server Applications Guide | |
Chapter 4
Installation, Administration, and DeploymentThis chapter describes the differences between installing and administering Sun Java System Application Server 7 2004Q2 and Sun ONE Application Server 6.x Enterprise Edition. A brief description of deployment topologies is also included.
This chapter contains the following sections:
Installation differencesSun ONE Application Server 6.x, Enterprise Edition had a few supported products that needed to be installed to get the application server up and running. Compared to it, Sun Java System Application Server 7 2004Q2 installation is straight forward as many of the additional components are either built-in or, not required.
The following table provides a description of the differences. The left column lists the various products, the columns in the center and right list the corresponding products as used in Sun ONE Application Server 6.x and Sun Java System Application Server 7 2004Q2, Enterprise Edition, respectively.
Minimum Requirements
The following table provides a snapshot of the differences between the requirements of Sun ONE Application Server 6.x and Sun Java System Application Server 7 2004Q2. The left column lists the components, while the center and right columns list the requirements for Sun ONE Application Server 6.x and Sun Java System Application Server 7 2004Q2, Enterprise Edition, respectively.
Installation Procedure differences
- Unlike Sun ONE Application Server 6.x, you do not have to install iPlanet Web Server or iPlanet Directory Server before installing Sun Java System Application Server 7 2004Q2. However, you will need a separate web server to install the load balancer plug-in.
- Before you install Sun Java System Application Server 7 2004Q2, Enterprise Edition software, you will need to decide on product topology of the application server and the High-Availability Database (HADB) server.
They can generally be hosted in two ways:
In both cases, at least two systems per component are needed to achieve high availability.
Note
Only 8-16 connections are allowed per HADB node. To take care of high loads, you should plan to add more HADB nodes.
Details on the various topologies that can be implemented for the Always On Technology are discussed in the Enterprise Edition of Sun Java System Application Server, System Deployment Guide.
For detailed instructions for installing the Application Server software, see the Sun Java System Application Server Installation Guide.
For more information on these load balancing methods, see Sun ONE Application Server 6.x, Enterprise Edition, Administrator’s Guide.
Sun Java System Application Server 7 2004Q2, Enterprise Edition supports a simple, round robin scheme, with sophisticated health checking and failover capabilities. For more information on the load balancing schemes, see the Sun Java System Application Server Administration Guide.
Administration and Deployment DifferencesThe following table lists the different administration and deployment utilities between the two application server versions.
Non-root Installation and Administration
Sun Java System Application Server 7 2004Q2, Enterprise Edition does not require root privileges to install. For details see, Sun Java System Application Server Installation Guide.
Deployment TopologiesFor various, detailed Sun Java System Application Server 7 2004Q2 deployment topologies, see the Sun Java System Application Server System Deployment Guide.