Chapter 4
Installation, Administration, and Deployment

This chapter describes the differences between installing and administering Sun™ ONE Application Server 7, Enterprise Edition and iPlanet™ 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

iPlanet Application Server 6.x, Enterprise Edition had a few supported products that needed to be installed to get it up and running. Compared to it, Sun One Application Server 7 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 iPlanet Application Server and Sun ONE Application Server 7, Enterprise Edition, respectively.

Table 4-1  Installation Differences

Products	iPlanet Application Server 6.x	Sun ONE Application Server 7
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 (Java 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 iPlanet Application Server 6.x and Sun ONE Application Server. The left column lists the components, while the center and right columns list the requirements for iPlanet Application Server 6.x and Sun ONE Application Server 7, Enterprise Edition, respectively.

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

Component	iPlanet ApplicatioN Server 6.x	Sun ONE Application Server 7
Operating System	Solaris 2.6, 8, 9 (SPARC) HP-UX IBM AIX Windows NT, Windows 2000	Solaris 8, 9 (SPARC)
Hard Disk space	400 MB	250 MB
RAM	512 MB	256 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
Directory Server	iPlanet/Sun ONE Directory Server 5.0	Not required
High-Availability Database	Not available	Supplied with product.

Installation Procedure differences

Unlike iPlanet Application Server 6.x, you do not have to install iPlanet Web Server or iPlanet Directory Server before installing Sun ONE Application Server 7. However, you will need a separate web server to install the load balancer plug-in.
Before you install Sun ONE Application Server 7, 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 ONE Application Server 7, Enterprise Edition, System Deployment Guide.

iPlanet 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 ONE Application Server 7, Enterprise Edition supports a simple, round robin scheme, with sophisticated health checking and failover capabilities.

---

Administration and Deployment Differences

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

Table 4-3  

Products	iPlanet Application Server 6.x	Sun ONE Application Server 7
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 4 or asadmin.
Registry Editor	GUI: iPlanet Registry Editor (kregedit).	Not required.
cladmin	Not available	Sets up HTTP/S session persistence with the most common working requirements.
clsetup	Not Available	Sets up Sun One 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

Administration and Deployment Differences

Non-root Installation and Administration

Sun One Application Server 7, Enterprise Edition does not require root privileges to install. For details see, Sun One Application Server 7, Enterprise Edition Installation Guide.

---

Deployment Topologies

For various, detailed Sun ONE Application Server 7 deployment topologies, see Sun ONE Application Server 7, Enterprise Edition System Deployment Guide.

Previous      Contents      Index      Next

---

Copyright 2003 Sun Microsystems, Inc. All rights reserved.