Previous Contents Index Next |
Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Migrating and Redeploying Server Applications Guide

> ## Chapter 4
> Installation, Administration, and Deployment

> This 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 differences
> - Administration and Deployment Differences
> - Deployment Topologies

> ##

> Installation differences

> Sun 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.

> Table 4-1 Installation Differences

> Products | Sun ONE Application Server 6.x | Sun Java System Application Server 7 2004Q2
> --- | --- | ---
> Web Server | iPlanet Web Server. | Built-in. An additional web server installation is required for the load balancer plug-in.
> LDAP Server | iPlanet Directory Server | Not required.
> JMS | iPlanet Message Queue for Java | Built-in (Sun Java System Message Queue).
> High-Availability Database (HADB) | Not Required | Required for storing HTTP/S session state.

> ### 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.

> Table 4-2 Minimum Requirements for the two versions of application servers

> Component | Sun ONE ApplicatioN Server 6.x | Sun Java System Application Server 7 2004Q2
> --- | --- | ---
> Operating System | Solaris 2.6, 8, 9 (SPARC) HP-UX IBM AIX Windows NT, Windows 2000 | Solaris 8, 9 (SPARC) Solaris 9 (X86) Red Hat Linux 7.2 Red Hat Enterprise Linux 2.1 Windows 2000, 200 SP2, XP
> Hard Disk space | 400 MB | 250 MB
> RAM | 512 MB | 512 MB
> J2SE | 1.3.1_06 (iPlanet Application Server 6.5, SP1, Enterprise Edition) | 1.4.0_02
> Web server | iPlanet/Sun ONE Web Server 6.0, SP1, SP2, or 6.0.1, iPlanet Web Server 4.7 Apache 1.3.19, 1.13.26 Microsoft IIS 4.0, 5.0 | Sun ONE Web Server 6.0 SP2 Apache 1.3.27 Microsoft IIS 4.0, 5.0
> Directory Server | iPlanet/Sun ONE Directory Server 5.0 | Not required
> High-Availability Database | Not available | Supplied with product.

> ### 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:

> - Application server and HADB server node hosted on the same system
> - Application server and HADB server node hosted on separate systems

> 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.

> - Sun ONE Application Server 6.x supported various load balancing schemes, along with the web server plug-in and application server driven mechanism. Additionally, the web server plug-in driven method supported a wide variety of sticky round robin scheme.

> 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 Differences

> The following table lists the different administration and deployment utilities between the two application server versions.

> Table 4-3 Administration and Deployment Differences

> Products | Sun ONE Application Server 6.x | Sun Java System Application Server 7 2004Q2
> --- | --- | ---
> Administration Interface | Administration Server. Location: install_dir/ias/bin | Administration Server. Location: install_dir/domains/domain_dir/admin-server/bin
> GUI: Console based Administration Tool (iASAT). Command line too: iascontrol | GUI: Browser based administration tool. Command line too: asadmin
> Deployment tool | Separate deployment tool GUI: Console based deployment tool Command line tool: iasdeploy | Sun ONE Studio for Java 5, Update 1 or asadmin. Assembly Tool
> Registry Editor | GUI: iPlanet Registry Editor (kregedit). | Not required.
> cladmin | Not available | Command line tool for cluster administration.
> clsetup | Not Available | Sets up HTTP/S session persistence and Application Server in a typical cluster environment with the most common working requirements.
> Load balancing | Administration Tool | Configuration file based. The loadbalancer.xml file contains the configurable parameters.
> Session failover | Administration Tool | HADB command line utility

> #### 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 Topologies

> For various, detailed Sun Java System Application Server 7 2004Q2 deployment topologies, see the Sun Java System Application Server System Deployment Guide.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.