Previous     Contents     Index     DocHome     Next     
iPlanet Application Server Installation Guide



Chapter 2   Preparing to Install


This chapter includes the following topics:

Read this chapter before using the ezSetup, Typical, or Express iPlanetTM Application Server installations. For any late breaking updates to these instructions, check the Release Notes at:

http://docs.iplanet.com/docs/manuals/ias.html

For more information about configuring your application server after installation, refer to the iPlanet Application Server Administrator's Guide.



Minimum System Requirements


Your system must meet the following requirements before you can install iPlanet Application Server.


Solaris

Your SolarisTM system must meet the following requirements before you can install iPlanet Application Server:

  • Sun® SPARCTM running Solaris 2.6 or Solaris 8

  • 400 MB free hard disk space

  • 256 MB RAM (512 MB recommended)

  • One of the following Web Servers:

    • iPlanet Web Server Enterprise Edition 4.1, SP7

    • Apache Web Server 1.3.19

  • The following Web browser:

    • NetscapeTM Communicator 4.5 or later


      Note The web server and browser need not be present on the same machine if you are performing a Webless installation. For more information, see "Webless Installations"


  • Solaris Patch Requirements

    iPlanet Application Server 6.0 bundles Solaris Production JDK 1.2.2_07 for SPARC. The following patches for JDK 1.2.2_07 must be applied on Solaris 2.6. These patches can be downloaded from the http://sunsolve.sun.com Web site.


    Table 2-1    Required JDK 1.2.2_07 patches

    Patch

    Patch Description

    105181-23  

    Kernel update patch  

    105210-32  

    libaio, libc & watchmalloc patch  

    105284-37  

    Motif 1.2.7: Runtime library patch  

    105568-18  

    Libthread patch  

    105633-48  

    OpenWindows 3.6: Xsun patch  

    105669-10  

    libDtSvc Patch  

    106040-14  

    X Input & Output Method patch  

    106409-01  

    Fixes the Traditional Chinese TrueType fonts  

    107733-08  

    Linker patch  

    108091-03  

    ssJDK1.2.1_03 fails with fatal error in ISO8859-01 Locales  

For Solaris 8, apply the recommended JDK 1.2.2_07 patches listed on the http://sunsolve.sun.com Web site.


Table 2-2    Recommended Solaris 8 OS patches

Patch

Patch Description

108991-12  

libc and watchmalloc patch  


Windows

Your Microsoft Windows system must meet the following requirements before you can install iPlanet Application Server:

  • Microsoft Windows NT 4.0 with SP6a or Windows 2000 Professional

  • 275 MB free hard disk space (NTFS)


    Note On a FAT file system, the installer may not calculate the needed space correctly and may run out of disk space without warning.


  • 256 MB RAM (512 MB recommended)

  • One of the following Web Servers:

    • iPlanet Web Server Enterprise Edition 4.1, SP7

    • Microsoft Internet Information Server 4.0

    • Apache Web Server 1.3.19

  • One of the following Web browsers:

    • Netscape Communicator 4.5 or later

    • Internet Explorer 4.0 or later


      Note The web server and browser need not be present on the same machine if you are performing a Webless installation. For more information, see "Webless Installations"




Installation Options

iPlanet Application Server provides the following installation options:

The first three options require very little user input and thus enable you to get the application server up and running in a matter of minutes. The installer sets up the application server with default values for port numbers, passwords, and so on. These settings are sufficient for running many of the iPlanet sample applications and for providing a platform for you to use in deploying your own sample applications.


Ezsetup

The ezsetup installation is a standalone application you launch from the desktop. It is the easiest of the installation options. The ezsetup installer runs a script which assigns default values to administrator user names and passwords. You only have to enter information to two questions to start the installation process.

For installation instructions, go to "Running ezsetup on Windows," on page 54, or "Running ezSetup on Solaris," on page 71.


Express or Typical

The Express and Typical options afford more flexibility than ezSetup. The express and Typical options will install iPlanet Application Server with the most common settings. You can configure your iPlanet Application Server instances after installation by using the Administration Tool.

For instructions on installing on Windows, go to "Running the Wizard Installation," on page 56, and for installing on Solaris, go to "Starting Solaris Installations," on page 73.


Custom

The Custom installation option allows you to configure the application server and its associated components during the installation. The Custom installation option requires a lot of user input and is recommended for advanced users.

For instructions on installing on Windows, go to Chapter 5 "Advanced Installations for Windows", and for Solaris, see Chapter 4 "Advanced Installations for Solaris".


Note You must use the Custom installation option to test the clustering samples.



Silent

The Silent Installation feature allows iPlanet Application Server installation on multiple machines without running the installation program more than once.

For more information on running the Silent installation option on Windows, see "Installing on Multiple Windows Machines", and for Solaris, see, "Installing on Multiple Solaris Machines".



Upgrading to SP3


This section describes procedures to upgrade from iPlanet Application Server 6.0, SP1 RevB and SP2, to iPlanet Application Server Enterprise Edition (EE) 6.0, SP3 release.

Due to changes in SP3 to provide enhanced security, and the class loader, you must redeploy applications running on SP1 using the redeploy utility. For more information on upgrading from SP1 RevB to SP3, see Upgrading from SP1 RevB to SP3.

Upgrading from SP2 is fairly straight forward. Your applications are automatically migrated when you install SP3. For more information on upgrading from SP2 to SP3, see Upgrading from SP2 to SP3.


Note
  • Stop iPlanet Application Server before starting the upgrade process.

  • The installer performs an upgrade based on the existing configuration. If you want to make any changes to the existing configuration, first complete the upgrade procedure, and then use iPlanet Application Server Administration Tool (IASAT) and other utilities to make those changes.

  • If you are running a release earlier than iPlanet Application Server 6.0, SP1 RevB, then you must do a complete reinstall.

  • iPlanet Application Server installation or upgrade will cause the Directory Server installed locally on the same machine on which the application server is being installed, to restart. Other application server instances configured to the same Directory Server will display error messages, until the Directory Server is up again.

    After the Directory Server has restarted, all the iPlanet Application Server instances will function normally.


This section includes the following topics:


Upgrading from SP2 to SP3

Use the following procedure to upgrade to iPlanet Application Server Enterprise Edition 6.0, SP3.

This section includes upgrade procedures for the following platforms:


Upgrading on Windows Platforms

To upgrade to iPlanet Application Server 6.0 SP3 on Windows, perform the following steps:


Note Stop iPlanet Application Server before starting the upgrade process.


  1. Ensure you have met all the conditions listed in "Minimum System Requirements," on page 35, and "Prerequisites for Installation," on page 122.

  2. Run the setup program.

  3. Click Next after the Welcome screen appears.

  4. Click Yes to accept the license agreement.

    You must accept the License agreement to continue.

  5. Click Next to install the iPlanet Server and core components.

  6. Select Custom as the type of installation.

  7. The Setup program will automatically select the same location as your current installation. Click Next to continue.

    The Components to Install screen appears.

  8. Deselect Directory Server Suite.

  9. Select iPlanet Application Server 6.0.

    Make sure this is the only selected component.

  10. Follow directions in the installer as you would for a normal installation. You will require the License Key that you received along with the product CD.

  11. Enter configuration details, such as configuration directory administrator ID, password and port numbers, exactly as used for your current installation.

    The installer will display the port numbers as used by the existing installation. Do not modify any of the values.

  12. Click Next through the rest of the screens to complete the install.

    For more information on the installation procedure, see Chapter 5 "Advanced Installations for Windows".


Upgrading on Solaris Platforms

To upgrade to iPlanet Application Server 6.0, SP3 on Solaris, perform the following steps:


Note
  • Make sure to stop the iPlanet Application Server before starting the upgrade process.


  1. Ensure you have met all the conditions listed in "Minimum System Requirements," on page 35, and "Prerequisites for Installation," on page 53.

  2. Run the setup program.

    For detailed information on the installation procedure, see Chapter 4 "Advanced Installations for Solaris".

  3. Select Custom as the type of installation.

  4. Choose to install the software in the same location as your current installation. Press Enter.

    The iPlanet Server Products Components screen appears.

  5. Type-in 4 and press Enter to install only the iPlanet Application Server component

  6. Enter the Directory Server administrator ID and password.

  7. When you are asked whether you want to upgrade, type y at the prompt and press Enter.

  8. Follow directions in the installer as you would for a normal installation.

    Enter configuration details, such as, configuration directory administrator ID, password and the port numbers, exactly as used for your current installation.


    Note
    • Choose the same configuration options that you chose for the existing installation. You can make modifications to your configuration after upgrading.

    • The installer will not display the existing port numbers and configuration details. You must enter the same values as used by the existing installation.


  9. Follow directions in the installer as you would for a normal custom installation. You will require the License Key that you received along with the product CD.

    For more information on the installation procedure, see Chapter 4 "Advanced Installations for Solaris".


Upgrading from SP1 RevB to SP3

The following changes made to iPlanet Applications Server EE 6.0, SP3 make it necessary to redeploy applications running on SP1 RevB:

  • Applications that contain code which tries to read the username and password from a HTTP request string will not work on SP3, even after redeploying the application on SP3. You will have to modify the application's source code to use Form Based Authentication.

  • iPlanet Application Server EE 6.0, SP3 extracts class files in a .war file under the directory, <iASInstallDir>/ias/APPS/<app-name>/<module-name>/classes, compared to <iASInstallDir>/ias/APPS in SP1.

    The Jasper compiler integrated with iPlanet Application Server 6.0, SP3 specifically expects this directory structure.


    Note The Jasper source files have been modified to work better with iPlanet Application Server 6.0 SP3. Use the archives that are bundled with the application server installation.


  • The new Class Loader implemented in SP3 might not be able to load class files from previously deployed .war components of .ear files are placed in the wrong path.

    For more information, see the iPlanet Application Server Migration Guide.


To upgrade from SP1 RevB to SP3

To upgrade from SP1 RevB to SP3, on both the Windows and Solaris platforms:

  1. Install SP3 in the same location where SP1 is currently installed.

    Follow instructions given in Upgrading from SP2 to SP3.

  2. After completing the SP3 installation, run the redeploy utility to migrate applications to SP3.

    The redeploy utility is shipped along with iPlanet Application Server 6.0 EE SP3 and can be found at the following location:

    • On the Windows platform, run:

      <iASInstallDir>/ias/bin/redeploy.exe

    • On the Solaris platform, run the redeploy shell script from

      <iASInstallDir>/ias/bin/redeploy

    The redeploy utility finds all applications and the corresponding ear files deployed on SP1, and re-deploys each application on SP3. All class files from the .war components of applications deployed on SP1 are moved to the following location:

    <iASInstallDir>/ias/trash/sp1

    A directory structure corresponding to the package structure of that class is recreated in this location.


    Note
    • Applications that contain code which tries to read the username and password from a HTTP request string will not work on SP3, even after redeploying the application on SP3.

    • Applications that consist of only .war files (not packaged within an .ear file), will have to be redeployed manually after upgrading.

    • If you have applications deployed on SP1 that uses database clients not supported by SP3, then you must register a database client compatible with iPlanet Application Server EE 6.0, SP3 and register the data sources for these applications.

      To register the database drivers, run dbsetup.exe (for native drivers) and jdbcsetup.exe (for third party drivers) on Windows, and db_setup.sh on Solaris after completing the upgrade.

      Use the iasdeploy utility to register datasources.




List of Certified Directory Servers

The following directory servers are certified to work with iPlanet Application Server 6.0, SP3.

Table 2-3    Certified Directory Servers

Directory Server

Version

iPlanet Directory Server  

4.13 (bundled with iPlanet Application Server 6.0, SP3)  



List of Certified Web Servers


The following Web servers are certified to work with iPlanet Application Server 6.0, SP3.

Table 2-4    Certified Web Servers

Wed Server

Interface

iPlanet Web Server Enterprise Edition 4.1 SP7  

NSAPI  

Microsoft Internet Information Server 4.0  

ISAPI  

Apache 1.3.19  

APACHEAPI  



List of Certified JVMs


The following JVMs are certified to work with iPlanet Application Server 6.0, SP3.

Table 2-5    Certified JVMs

Platform

Version

JVM

Windows 2000  

Professional  

JDK 1.2.2_007  

Windows NT  

4.0 SP6a  

JDK 1.2.2_007  

Solaris  

2.6, 8  

JDK 1.2.2_07  



Accessing Databases


To configure a new iPlanet Application Server instance for database access, it is recommended that you use one of the iPlanet Application Server database setup tools after installation. You can use these tools to configure your applications and components for third party JDBC access.


Note In addition to the JDBC third party driver support, the Custom installation option provides wizard panels for configuring iPlanet Application Server Type 2 database access. However, these drivers are planned for deprecation in the next major release of iPlanet Application Server.


This section includes the following topics:


Configuring Database Drivers

Third party JDBC drivers need to be identified to iPlanet either during application server installation, or by using registration tools after installation. Registration must occur on each application server instance that houses applications which use third party JDBC driver data sources.

When you create your own applications, you can elect not to specify the particular database you want the application to use. In this case, the application will attempt to connect to the configured databases in the priority order you specify during installation.


Note During installation, third party JDBC drivers are automatically setup, even if you choose not to configure database drivers. This is to ensure the proper working of the PointBase database server, which is installed by default during installation.



During Installation

You can configure the third party JDBC drivers only through the Custom installation option. If you use the Express or Typical installation, see the next section for configuring the third party JDBC drivers after installation of the application server.


After Installation

Configure third party JDBC drivers after installation by executing a JDBC driver configuration tool. When configuring after installation, you must restart the application server to apply the driver changes.

  • For Windows, execute the jdbcsetup.exe program. (Registration of iPlanet Type 2 JDBC drivers for the supported database platforms is automatic since iPlanet recognizes the presence of the supported native client libraries).

  • For Solaris, execute the db_setup.sh script. (The same command used to configure iPlanet Type 2 drivers).


    Note For more information on configuring Third Party JDBC drivers, see "Third Party JDBC Driver Support", and the iPlanet Application Server Administrator's Guide.



Database Support

Support for third party JDBC drivers was added as a new feature in iPlanet Application Server 6.0 SP1. This feature augments the previous database support for iPlanet Application Server Native Type 2 JDBC database drivers.

iPlanet Application Server will continue to support iPlanet Application Server native Type 2 JDBC database drivers until the next major version of iPlanet Application Server is released. At that time, they are planned for deprecation. Future iPlanet Application Server applications must function with JDBC database drivers.

iPlanet Application Server 6.0 SP3 is certified against the third party JDBC database drivers in Table 2-6. In addition, though not yet certified, other third party JDBC database drivers should work with iPlanet Application Server 6.0, SP3.


List of Certified Third Party JDBC Database Drivers


Table 2-6    Third party JDBC database drivers certified in SP3

Database Vendor

JDBC Driver

Oracle  

Oracle8i 8.1.6.0.1: Type 4 and Type 2  

Merant SequeLink  

DataDirect Java 5.0 (all databases supported by DDJ5)  

Sybase  

jConnect for JDBC 5.2 Type 4  

BM DB2  

IBM DB2 7.1 JDBC Client  

Informix  

Informix JDBC v1.22, Informix JDBC v2.1 (Type 4 driver)  


List of Certified Native Type 2 Database Servers and Clients

iPlanet Application Server 6.0 continues to support the database clients and servers for the iPlanet Application Server Type 2 JDBC Database Drivers listed in Table 2-7.


Table 2-7    Native Type 2 database servers and clients supported in SP3

Database Server

Database Client

Oracle 8.05, 8i, (7.3.4), 9i  

Oracle 8.1.5, 8.1.6. and 8.1.7  

Sybase 11.9.2, 12  

Sybase Open/Client System 12  

DB2 6.1, 7.1  

DB2 6.1, 7.1  

Informix 7.3, 9.1.4, 9.2  

Informix SDK 2.40  

Microsoft SQL Server 7  

ODBC 3.51  



Configuring iPlanet Application Server Clusters


A simple cluster configuration is demonstrated in the instructions on the iPlanet Developer's Web site. This simplistic cluster configuration is not representative of a true production configuration, but is sufficient to demonstrate the behavior of the iPlanet Application Server.

The configuration consists of two machines that each have a Web server instance and an iPlanet Application Server instance installed. One machine also has a Directory Server instance that is used by the application servers on both machines, as shown in the following illustration.

Figure 2-1    A simple iPlanet Application Server cluster configuration

In this simple cluster, configuration data is stored in the directory server on the first machine. When the second application server is installed, it uses the same directory server for configuration information. It's preferable to use the same data tree in the directory server, so that the same configuration information can be shared between all servers and Web connectors.

During installation of the second application server, you must enter the same value for the cluster name and global configuration name as specified during the first application server installation.

In this example, the Web servers are on the same machine as the iPlanet Application Servers. If the Web servers were housed on a separate tier of machines, then you would enter the same global configuration name and cluster name during the Web connector installation. See the iPlanet Application Server Samples for complete instructions on installing and configuring this simple cluster on a Windows or Solaris machine at:


Windows

http://developer.iplanet.com/appserver/samples/cluster/docs/nt-cluster.html


Solaris

http://developer.iplanet.com/appserver/samples/cluster/docs/unix-cluster.html

Note This is not a production configuration. If it were a production configuration, it would most likely have the Web servers on separate machines and a second Directory Server configured to act as a backup for the first Directory Server. For information on how to set up the iPlanet Directory Servers for replication and failover, see the iPlanet Directory Server Installation Guide at: http://docs.iplanet.com


For more information on configuring iPlanet Application Server clusters, see "Configuring Clusters and Data Synchronization", and the iPlanet Application Server Administrator's Guide.


Previous     Contents     Index     DocHome     Next     
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.

Last Updated June 25, 2001