Previous Contents Index Next |
iPlanet Application Server Installation Guide |
Chapter 2 Preparing to Install
This chapter includes the following topics:
Minimum System Requirements
Read this chapter before using the ezSetup, Typical, Express or Custom iPlanetTM Application Server installations. For any late breaking updates to these instructions, check the Release Notes at:Prerequisites for Installation
List of Certified Directory Servers
List of Certified Third Party JDBC Database Drivers
List of Certified Native Type 2 Database Servers and Clients
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, Enterprise Edition 6.5:
Sun® SPARCTM running Solaris 2.6 or Solaris 8
Apply the following JDK 1.3.1_02 patches on Solaris 8:One of the following Web Servers:
iPlanet Web Server, Enterprise Edition 6.0 , SP1, SP2, or 6.0.1
The following Web browser:iPlanet Web Server, Enterprise Edition 4.1, SP7 or later
NetscapeTM Communicator 4.5 or later
Solaris Patch Requirements
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"
- iPlanet Application Server 6.5 bundles Solaris Production JDK 1.3.1_02 for SPARC®. The following patches must be applied on Solaris 2.6 and Solaris 8.
- These patches can be downloaded from the http://sunsolve.sun.com Web site.
Table 2-1    Required JDK 1.3.1_02 patches on Solaris 2.6
Patch
Patch Description
Table 2-2    Required JDK 1.3.1_02 patches on Solaris 8
Patch
Patch Description
Apply the following OS patches on Solaris 8
Table 2-3    Required Solaris 8 OS patches
Patch
Patch Description
Note You must reboot your Solaris system after applying the kernel patch.
Windows
Your Microsoft Windows system must meet the following requirements before you can install iPlanet Application Server, Enterprise Edition 6.5:
Microsoft Windows NT 4.0 with SP6a, or Windows 2000 Professional SP2, or Windows 2000 Server SP2, or Windows 2000 Advanced Server SP2
400 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.
One of the following Web Servers:
iPlanet Web Server, Enterprise Edition 6.0, SP1, SP2 or 6.0.1
One of the following Web browsers:iPlanet Web Server Enterprise Edition 4.1, SP7 or later (not supported on Windows 2000)
Microsoft Internet Information Server 4.0 or 5.0
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"
To run Internet Information Server 5.0 on Windows 2000, a few manual configuration steps have to be performed. For more information see, "Registering the Plug-in on IIS 5.0 running on Windows 2000".
Prerequisites for Installation
Before you begin installing iPlanet Application Server, Enterprise Edition 6.5, verify that the following prerequisite conditions are met:
Meet the Minimum System Requirements for the platform on which you are installing iPlanet Application Server.
Have administrative privileges on the Windows or Solaris system.
On Solaris platforms, unset the environment variable LD_LIBRARY_PATH from the shell from which you are installing iPlanet Application Server.
On Solaris platforms, establish a UNIX user and group for iPlanet Application Server. Use this account to install and manage iPlanet Application Server.
Make sure you have your product key nearby; it's in the Welcome letter.
Ensure that a static IP address is assigned to the machine (contact your system administrator to get one).
If you are planning to use a fresh installation of iPlanet Application Server, Enterprise Edition 6.5 with a remote user directory, you must install the iPlanet Directory Server 5.0 SP1 patch before installing iPlanet Application Server.
If you choose not to install the Directory Server Suite on a fresh installation of iPlanet Application Server, Enterprise Edition 6.5 on Windows, then you must copy the libnspr3.dll file from the product CD to the Winnt\system32 directory. This is to ensure that your LDAP applications work properly when the configuration directory is on a remote machine.
- This patch must be installed even if you are using iPlanet Directory Server 4.13 or later versions, as your user directory. For more information on how to install the patch, see "Installing iDS 5.0 SP1 Patch".
Make sure that no other service is running on port 9092 before installing iPlanet Application Server as the bundled PointBase database application uses port 9092 by default.
- The libnspr3.dll file can be found on the product CD in the /Windows/iAS directory.
If you are running Windows 2000, ensure that the Primary DNS suffix has been correctly set on the machine on which you are installing iPlanet Application Server.
On Solaris platforms, ensure that the machine has its fully qualified domain name mentioned in the /etc/hosts file, as shown in this example:
- To set the Primary DNS suffix, go to Start menu> Settings>Control Panel>System>Network Identification>Properties. Ensure that the computer's name is entered correctly.
- Click More. Ensure that the DNS domain name is entered correctly in this panel. Click OK to update your changes.
#
# Internet host table
#
127.0.0.1 localhost
192.168.0.255 myhost.company22.com myhost loghostOn Solaris platforms, ensure that the Directory Server is installed on the local file system. Multiple physical drives can be used, but they should to be mounted locally.
Make sure that one of the recommended Web Server and Web Browser is installed and configured before you install iPlanet Application Server. The iPlanet Web Server, Enterprise Edition 6.0, SP1 or SP2 is available for download at: http://www.iplanet.com/downloads/download
Install and Configure Database ServersOn the Solaris platform, iPlanet Application Server user and the Web Server user must either be the same or from the same group. If the Web Server is installed as a regular user, and the iPlanet Application Server user is installed as the root user, a file permission problem will exist. The Web Server will not start because it doesn't have access to the registry file, reg.dat.
- If your web server runs on a different machine from the machine on which iPlanet Application Server is installed, you perform what is referred to as a "webless" installation. After performing a webless installation, you must install the Web Connector plug-in on the web server in your configuration.
- For more information, see "Webless Installations".
Note To use Apache Web Server, you must configure iPlanet Application Server to work with either the iPlanet Web Server or Microsoft Internet Information Server during installation. After installing iPlanet Application Server, install and configure the Apache Web Server.
Make sure to set the registry key permissions for the \SOFTWARE\iPlanet key to Full Control for all options.
- For more information on how to install and configure the Apache web server, see "Installing the Web Connector Plug-in".
- Before installing iPlanet Application Server, install the database servers and clients to use with this iPlanet Application Server installation.
- During application server Custom installation, you can choose to configure iPlanet Type 2, third party JDBC, or no JDBC drivers. Although only one type of JDBC driver can be configured during installation, either the Type 2 driver or third party JDBC driver, you can choose to configure both after installation.
- You can configure third party JDBC drivers after installation by executing db_setup.sh script on Solaris and jdbcsetup.exe on Windows, a JDBC driver configuration tool. When configuring the database drivers after installation, you must restart the application server to apply the changes. For more information, see iPlanet Application Server Administrator's Guide.
Installing iDS 5.0 SP1 Patch
This patch should be installed if you are planning to use a fresh installation of iPlanet Application Server, Enterprise Edition 6.5, with a remote user directory. This patch must be installed even if you are using iPlanet Directory Server 4.13 or later versions, as your user directory.You don't need to install the iPlanet Directory Server 5.0 SP1 patch if you are upgrading from an earlier version of iPlanet Application Server, Enterprise Edition, 6.0. While upgrading, make sure you do not select the iPlanet Directory Suite component. For detailed instructions on upgrading iPlanet Application Server, see "Upgrading to 6.5".
Follow these instructions to install iPlanet Directory Server 5.0 SP1 Patch. This patch must be copied to the appropriate directory before installing iPlanet Application Server, Enterprise Edition, 6.5.
To Install the Patch on Solaris
Copy the contents of the product CD under the Solaris/iAS directory to a local directory on yourmachine.
From the product CD, copy the nsslapd.zip file from the iDS50SP1patch/Solaris directory to the slapd directory under the iPlanet Application Server installables on your local machine.
Run the iPlanet Application Server, Enterprise Edition, 6.5 installation from this local directory.
To Install the Patch on Windows
Copy the contents of the product CD under the Windows\iAS directory to a local directory on your machine.
From the product CD, copy the slapd.z file from the iDS50SP1patch\Windows directory to the slapd directory under the iPlanet Application Server installables on your local machine.
Run the iPlanet Application Server, Enterprise Edition, 6.5 installation from this local directory.
Installation Options
iPlanet Application Server provides the following installation options:
Ezsetup
The first two 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 the easiest of the installation options. The ezSetup installer runs a script which assigns default values to administrator user names and passwords. You have to enter information to very few questions to start the installation process.For installation instructions, go to "Running ezSetup on Windows," on page 63, or "Running ezSetup on Solaris," on page 43.
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 66, and for installing on Solaris, go to "Starting Solaris Installations," on page 45.
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 6 "Advanced Installations for Windows", and for Solaris, see Chapter 5 "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 6.5
Due to changes in the transaction manager, you cannot upgrade from 6.0 SPx to iPlanet Application Server 6.5. You will have to perform a fresh install of iPlanet Application Server 6.5 and redeploy all your applications.For details on redeploying your existing applications, see Chapter 2, "Migrating Applications", in iPlanet Application Server Migration Guide.
List of Certified Directory Servers
The following directory servers are certified to work with iPlanet Application Server 6.5 on Solaris and Windows platforms.
Table 2-4    Certified Directory Servers
Directory Server
Version
List of Certified Web Servers
The following Web servers are certified to work with iPlanet Application Server 6.5.
List of Certified JVMs
The following JVMs are certified to work with iPlanet Application Server 6.5.
Table 2-6    Certified JVMs
Platform
Version
JVM
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.
This section includes the following topics:
Configuring Database Drivers
Configuring Database Drivers
Third party JDBC drivers need to be identified to iPlanet Application Server 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.
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 using the iPlanet Application Server Administration Tool. When configuring database drivers after installation, you must restart the application server to apply the driver changes.For more information, see iPlanet Application Server Administrator's Guide.
Database Support
iPlanet Application Server 6.5 is certified against the third party JDBC database drivers in Table 2-7. In addition, though not yet certified, other third party JDBC database drivers, which conform to JDBC 2.0 with Extensions specifications, should work with iPlanet Application Server 6.5.
List of Certified Third Party JDBC Database Drivers
Table 2-7    Third party JDBC database drivers certified in 6.5 on Windows and Solaris
Database Vendor
JDBC Driver
List of Certified Native Type 2 Database Servers and Clients
To maintain backward compatibility, iPlanet Application Server 6.5 continues to support database clients and servers for iPlanet Application Server Type 2 JDBC Database Drivers listed in Table 2-8.
Table 2-8    Certified Native Type 2 database servers and clients-in SP4
Database Server
Database Client
Platform
Note For proper functioning of the Sybase global transactions on Solaris, the following Sybase patches for client version 12 should be installed: These patches are available from the Sybase website at: http://www.sybase.com.
Previous Contents Index Next
Copyright © 2002 Sun Microsystems, Inc. All rights reserved.
Last Updated March 12, 2002