Previous     Contents     Index     DocHome     Next     
iPlanet Application Server Installation Guide



Chapter 1   Installing on NT


This chapter explains how to install iPlanet Application Server on Windows NT. It includes the following topics:

Read this chapter carefully before installing iPlanet Application Server. Check the release notes for any updates to these instructions at:

http://docs.iplanet.com/docs/manuals/ias/60/sp1/releasenotes.htm

For more information about configuring your application server during and after installation, refer to Chapter 3 "Configuring iPlanet Application Server."



Preparing for Installation



Before you begin installing iPlanet Application Server, you need to:

  • Check system requirements

  • Install and configure the web server

  • Create a Mirror Directory for Transaction Manager

  • Create a raw partition on a separate disk drive

  • Install and configure all database servers


Check System Requirements

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

Table 1-1

Component

Requirement

Computer/Operating system  

PC running Microsoft Windows NT version 4.0 with Service Pack 5  

Memory  

Per CPU: 256 MB minimum; 512 MB recommended  

Available disk space  

Total disk space: 200 MB NT (NTFS)

CD-ROM drive  

Pre-installed software  

One of the following web servers:

  • iPlanet Web Server 4.1 Enterprise Edition

  • Microsoft Internet Information Server 4.0 (NT only)

Netscape Directory Server 4.1 (optional)

One of the following web browsers:

  • Netscape Communicator 4.5

  • Microsoft Internet Explorer 4.0 (NT only)

Database connectivity software (see the following table)  

iPlanet Application Server 6.0 SP1 is configured to work with the database clients and servers listed below:

Table 1-2

Database Client

Database Server

Oracle 8.1.6  

Oracle 8.05, 8i, 7.3.4  

Sybase 11.1.1  

Sybase 11.9.2, 12  

DB2 5.2  

DB2 5.2, 6.1  

ODBC 3.51  

Microsoft SQL Server 7  

Informix 2.4  

Informix Server 7.3, 9.1.4  


Install and Configure the Web Server

The web server and web browser must be installed and configured before you install iPlanet Application Server.

You need to know whether your web server runs on the machine where you are about to install iPlanet Application Server, or whether it resides on another machine. A "webless" installation of iPlanet Application Server occurs when it resides on a separate machine. After a webless installation you will need to install the Web Connector plug-in on the machine that has the web server. For more information on webless installations, see page 128.


Create a Mirror Directory for Transaction Manager

The default disk drive is where you are installing the iPlanet Application Server. It is recommended that you specify a path on a separate disk drive. This is only needed if you are planning to use global transactions.


Create a Raw Partition

It is recommended that you create a raw partition on a separate disk prior to running the installation program. This is where the transaction manager log file gets stored for each Java Server. Raw Partitions are described in more detail on page 129.


Install and Configure All Database Servers

Install and configure all database servers before installing iPlanet Application Server.



Installing the Application Server



You must be logged on to Windows NT as a user with administrator privileges to install iPlanet Application Server. Check the system requirements, and make sure a web server and web browser are installed on your system.

There are two ways to install: using setup.exe, and using ezSetup.exe. The ezSetup provides an easy installation without requiring various inputs. For more information on Using ezSetup, see page 49. This section covers the setup.exe installation options: Express, Typical, and Custom installation. The Typical installation process is the default.

The following table describes the different installations:

Table 1-3

Express Install  

Minimal input is sought form the user for settings and features.  

Typical Install  

Input is sought from the user for most common settings and features. This is the default setup option.  

Custom Install  

This is the most flexible and input is sought from the user for each and every setting and feature.  

The following table shows which dialog boxes are displayed for each type of installation. Use this table in conjunction with "Using the Custom Installation Wizard" instructions on page 14 of in this document.

Table 1-4

Dialog Box

Custom

Typical

Express

Welcome  

X  

X  

X  

Software License Agreement  

X  

X  

X  

Select Server or Console Installation  

X  

X  

X  

Installation Type  

X  

X  

X  

Location of Installation  

X  

X  

X  

Components to Install

  • Netscape Server Family Core Components

  • Netscape Directory Suite

  • Administration Services

  • iPlanet Application Server 6.0

 

X  

X  

X  

Netscape Server Family Core Components  

X  

 

 

Netscape Directory Suite  

X  

 

 

Administration Services  

X  

 

 

iPlanet Application Server  

X  

 

 

Directory Server  

X  

X  

 

User and group  

X  

X  

 

Directory Server Settings  

X  

X  

 

Configuration Directory Server Administrator  

X  

X  

X  

Administration Domain  

X  

X  

 

Directory Manager Settings  

X  

X  

X  

Replication  

X  

 

 

Populate Database  

X  

 

 

Disable Schema Checking  

X  

 

 

Admin IP address  

X  

 

 

Administration Server Port Selection  

X  

X  

 

Global Configuration Name  

X  

 

 

Product Key  

X  

X  

X  

Web Server Type  

X  

X  

X  

Number of Java and C++ Servers  

X  

 

 

Administration Port, Executive Port, and the specified number of Java and C++ server ports.  

X  

 

 

Administration Server Authentication  

X  

X  

X  

Database Client Selection  

X  

 

 

Global transactions  

X  

 

 

Transaction Manager  

X  

 

 

Transaction Manager LogVolDiskName  

X  

 

 

Third Party JDBC Drivers  

X  

 

 

Third Party JDBC Driver Settings

  • Driver name

  • Class name

  • URLprefix

  • CLASSPATH

 

X  

 

 

Resource Manager  

X  

 

 

Resource Manager Details  

X  

 

 

Internationalization  

X  

X  

X  

Cluster Configuration  

X  

 

 

Sync Server Candidate for cluster Default

  • The IP Address for DSync server

  • The Executive server port

  • The priority of this candidate

 

X  

 

 

Configuration Summary  

X  

X  

X  


Using the Custom Installation Wizard

The following procedure describes how to install iPlanet Application Server using the Custom installation option:

  1. Insert the iPlanet Application Server Install CD-ROM into the CD-ROM drive.

  2. Use Start on the Windows NT taskbar and then Run, or choose File - Run from the Windows NT Program Manager and click the Run button.

  3. Browse and go to the CD-ROM drive (for example, d:\).

  4. Open the NT folder and run the file setup.exe.


    Note For other installation types use the above table to refer to the relevant sections in the procedure described for custom installation.




Installing the Components

Click Next after each screen selection.

  1. Accept the default to select iPlanet Servers.



    Choosing iPlanet Servers installs the Netscape Server Products Core Components, Netscape Directory Suites, and Administration Services with the iPlanet Application Server.

    The iPlanet Console is an administration console. Select it only to install as a stand-alone application.

  2. Accept the default Typical installation, or select Express or Custom. (These steps detail a Custom installation.)



See Table 1-3 for an explanation of the installation types.

  1. Select the installation directory.



    The default directory is c:\iPlanet\iAS6. If you do not have 200MB available on this drive for the installation of iPlanet Application Server, browse to select a different drive. Do not use a directory name that includes spaces.

  2. Accept default selections.



    Do not select the Netscape Directory Server 4.1 Synch Service, even though it is listed.

  3. Accept the default "This instance will be the configuration directory server."



    If you will be use another directory server (local or remote) to store the iPlanet Application Server configuration information, select "Use existing configuration directory server" and enter those settings.

  4. Accept the default "Store data in this directory server" if you did not select an existing Directory Server in the previous step.



    If you want to use an existing directory server, select "Store data to existing Directory Server" and enter its settings.

  5. Accept the default Directory Server settings.





    Caution

    Entering an identifier other than the default will cause the installation to fail.



  6. Enter the Administrator ID and password for the configuration directory server administrator.





    Note
    The Administrator ID and password supplied here will be required to uninstall iPlanet Application Server and Directory Server.



    I

  7. Accept the default, or enter a unique name for the Administration Domain.



  8. Enter the Directory Manager Distinguished Name (DN) and a password of at least eight characters.



    The default value for the Distinguished Name is cn=Directory Manager. For more information about Directory Manager DN, see page 126.

  9. Accept the default supplier and consumer replication settings.



    For more information about consumer and supplier replication, see Netscape Directory Server documentation:

    http://docs.iplanet.com/docs/manuals/directory.html#dirserver

  10. Accept the default to populate the directory server with commonly used entries. These are provided to help you get started running iPlanet Application Server. Populate the database by selecting the appropriate radio button.



    For more information about populating the database, see Netscape Directory Server documentation:

    http://docs.iplanet.com/docs/manuals/directory.html#dirserver

  11. Accept the default, or disable schema checking.



    For more information about installing and configuring the Directory Server, see page 124, or the Netscape Directory Server documentation:

    http://docs.iplanet.com/docs/manuals/directory.html#dirserver


Configuring the Administration Server

  1. Accept the default or enter a specific IP address to bind to your Administration Server.



  2. Accept the default port number for the Administration Server.



    Netscape Console requires this port number to administer the Directory Server. For more information about the Administration Server, see page 126.

  3. Accept the default, or enter a unique global configuration name for this installation of iPlanet Application Server.



    The name you assign is stored on the configuration Directory Server, under the o=iPlanetRoot tree, along with the global configuration names of any other iPlanet Application Server installations.

  4. Enter the NT product key for iPlanet Application Server.



  5. Select the web server you want to use.

    In case of multiple instances of iPlanet Web Server (iWS), select the instance you wish to use.





Note If you are using a web server other than IIS or iWS, you must enter the doc and cgi-bin directories.



See "Web Server, "page 127, to learn more about web servers and webless installation.

  1. Enter the number of Java Servers (KJS) and C++ Servers (KCS) used to process applications.



    The default values are 1; increase these values to handle high processing loads.

    You can also adjust the values after installation using the Administration Tool. See the iPlanet Application Server Administrator's Guide for more information.

  2. Enter the port numbers for the Administrative Server (KAS), the Executive Server (KXS), the Java Servers (KJS), and C++ Servers (KCS).



All port numbers you specify for listener ports must be within the acceptable range (1 to 65535), and must be unique (not used by any other applications on your system). For more information, see "Port Numbers,"page 126.


Note
If the port number is already in use, the service will not start up when you run iPlanet Application Server.



  1. Enter the Administration Server username and password.



  1. Rank the installed databases in order of connection priority.



    The installation program lists all supported database clients. The clients are allow your applications to connect to your database back ends. Rank the clients according to connection priority, whether you've installed them yet or not. Client software can be added after installation. Sample applications are configured for the highest priority database. See "Database, "page 128, to learn more.


Configuring Transaction Manager

  1. Specify if the server will have global transactions.



  2. If you specified "Yes" to global transactions, enter the mirror directory path where the transaction manager restart.bak file for each KJS engine process gets stored.



    The default location is the disk drive on which you are installing iPlanet Application Server. It is recommended that you specify a path on a separate disk drive.

  3. Accept the default, or enter the log volume disk name where the transaction manager log file is to be stored for each Java Server.



    It is recommended that you specify a path on a separate disk drive. Indicate if the specified disk name is a raw partition.

    If the log volume is a raw partition, indicate Offset (starting page number) and Size (number of pages) in the raw partition. Make sure the size allocated for the log file is greater than 4 MB; the file should be greater than or equal to 1000 pages, at a size of roughly 4 KB per page. See "Raw Partitions," page 129, for more information.


Configuring Third Party JDBC Drivers

  1. Enter whether or not you will use third party JDBC drivers. If you answer yes, type in how many drivers will be configured.



For more information about Third Party JDBC Driver Support, see page 130.

  1. You will need to enter the following information for each third party JDBC driver you will use. Format your entries as shown in the examples.





Note For typical Classnames and CLASSPATHS, see Third Party JDBC Driver Support, page 130.

After installation you must register the datasource files for the third party JDBC drivers. The above reference also explains registration.




Configuring Resource Manager

  1. Indicate whether or not you want to configure the Resource Manager, and specify the number of Resource Managers you will use.



For more information about the Resource Manager, see page 140.

  1. Accept the defaults or enter new information for each Resource Manager.



See "Open String Information,"page 141, to learn more.

  1. Specify whether or not you want to enable I18N support.



    Enabling I18N support allows multi-lingual applications to be deployed to iPlanet Application Server.


Configuring Clusters

  1. Accept the default, or select "Yes" if you intend to synchronize session and state information across multiple servers for failover and fault tolerance. Then enter the name of the cluster that this instance of iPlanet Application Server participates in.



    For more information about "Clusters and Data Synchronization,"see page 142.

  2. Indicate if you are currently installing a Sync Server or a Sync Local. Then enter the total number of Sync Servers that you plan to have in the cluster.



A Sync Local server uses data synchronization services, but is not eligible to become a Sync Primary or the Sync Backup Server.

  1. If you selected Sync Server in the previous step, enter information for each Sync Server in the cluster. Then choose which Sync Server has the highest priority for taking over as Sync Primary, and rate all other servers in order of priority.

    .

  1. Review the summary provided by the installation program of the configuration you have selected.



The installation program confirms when all of the iPlanet Application Server files have been copied to your computer. Select OK on the final dialog to reboot your computer, allowing the new settings to take effect.



Using ezSetup



The ezSetup option provides a fast and easy installation of the iPlanet Application Server and can be used for evaluation purposes. It is a Typical installation with all the default values already set. The following usernames and passwords are set as defaults:

Table 1-5

Component

username

password

Configuration server administrator  

admin  

admin  

Directory manager

 

Directory Manager  

DManager  

iAS Administration server

 

admin  

admin  

You will need the iAS Administration server username and password when you log in to that server.

Before using ezSetup, make sure a web server is installed and running.


To Run ezSetup:

  1. Click the ezSetup.exe [<cdrrom_drive>\ezsetup\ezSetup.exe].

  2. Enter the path where you want to install the iPlanet Application Server.

  3. In case of multiple instances of iWS, select the instance you want to use. ezSetup will default to iWS, if both iWS and IIS are installed.

  4. Click OK in the confirmation dialog to reboot your system.



Upgrading iPlanet Application Server 6.0 to SP1

To upgrade iPlanet Application Server 6.0 to SP1, it is not necessary to uninstall the pervious version. Follow the installation steps as described earlier. Select only the components you wish to upgrade.



Verifying Installation of the Application Server



You can use a pre-installed application to verify that iPlanet Application Server is running. Since this basic application, which uses servlets and JSPs, does not rely on a backend database, it runs without any post-installation setup.


To Verify Installation:

  1. Open your browser and enter the following URL:

    http://yourwebserver:portnumber/ias-samples/index.html

  2. Press Enter.

  3. Click the Test Connectivity to iPlanet Application Server link to run a basic application.

  4. Press the shift key and click on the browser's Reload button to ensure the application repeatedly returns a new HTML stream.



Installing the Web Connector Plug-in

The Web Connector plug-in passes requests from your web server to applications on iPlanet Application Server.

iPlanet provides Web Connector plug-ins for the following web servers:

  • iPlanet Web Server

  • Microsoft Internet Information Server

If you install iPlanet Application Server on a different machine than where the web server resides, you are configuring what is referred to as a "webless installation" of iPlanet Application Server. If this is the case, you must install the iPlanet Application Server Web Connector plug-in on the web server machine.

Before you install the Web Connector plug-in, do the following:

  1. Check whether or not the iPlanet Application Server 6.0 Web Connector plug-in has already been installed. If it has, the web server instance is already configured for iPlanet Application Server and you do not need to re-install the plug-in.

  2. Stop running your web server instance.

  3. You must be logged on as an administrator before installing the iPlanet Application Server Web Connector plug-in.

This procedure assumes that you have already installed iPlanet Application Server and Directory Server.


To Install the Web Connector Plug-in:

  1. After you finish installing iPlanet Application Server as a webless installation, take the installation CD-ROM to the machine or machines that host the web server.

  2. Run the installation program as described "Installing the Application Server" on page 12.

  3. When prompted, select "iPlanet Servers" as an installation.

  4. Specify the installation type "Typical."

  5. Specify a target installation directory. Do not include spaces in the path name.

  6. When prompted for the components you want to install, select only "iPlanet Application Server 6.0" component.

  7. Select only the "Web Connector Plug-in Component" from the list of subcomponents.

  8. Follow the instructions of the installation program.

  9. Select OK on the final dialog to reboot your computer, allowing the new settings to take effect.

    More information about the iPlanet Application Server Web Connector Component is contained in the Administrator's Guide and in the Deployment Tool Help system.



Using the Sample Applications

To better understand specific technology features provided by iPlanet Application Server, run the iPlanet Application Server Technology Samples.


To Use the Sample Applications:

  1. Start running iPlanet Application Server.

  2. Open your browser, enter the following URL, and press Enter:

    http://yourwebserver:portnumber/ias-samples/index.html

  3. Select the iPlanet Application Server J2EE Application Samples link and select a specific sample application. Follow the application-specific setup instructions to establish the necessary database settings and to run the application.

After you become familiar with the iPlanet Application Server sample applications, run the Sun Samples, which are applications based on those found at http://java.sun.com. The Java Pet Store example in particular demonstrates how a popular J2EE application is deployed to iPlanet Application Server.

You can review the source code of the sample applications and associated J2EE XML Deployment Descriptors by browsing in the following location:

iAS Installation Path/ias/ias-samples/

You can also find compile scripts at this site for experimenting with the sample code.



Uninstalling



If you need to uninstall iPlanet Application Server, follow the steps described in this section. Do not uninstall iPlanet Application Server by deleting directories or modifying parameters in the registry.

This procedure is for uninstalling iPlanet Application Server and its subcomponents. By default, all components are selected for uninstall. Confirm that no other servers are using the Directory Server; if that is the case, deselect and do not uninstall the Directory Server.

Before running the iPlanet Application Server uninstall program, make sure that Directory Server is running.

During the uninstall process, you are prompted to provide a user name and password with administrator access to the configuration directory. Enter the user name and password given during installation. Another user name and password can be entered, if it has administrator privileges to the configuration Directory Server.

The following directories remain after you uninstall iPlanet Application Server:

  • iPlanet Application Server root directory

  • Any custom directories you created under the iPlanet Application Server directory

  • The install directory/APPS directory

After uninstalling iPlanet Application Server, decide if you want to remove these directories, particularly the custom and APPS directories, which may contain applications you've developed, and files you wish to keep.


To Uninstall:

  1. Click the Uninstall icon in the iPlanet Application Server 6.0 program group.

  2. Choose the components and subcomponents you wish to uninstall.

  3. When prompted, enter a user name and password with administrator access to the configuration Directory Server. If you do not know, or do not want to use the user name and password given during installation, enter another user name and password having administrator privileges on the configuration Directory Server.

  4. Enter the configuration Directory Server information.


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

Last Updated September 21, 2000