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, Express or Custom 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, Enterprise Edition 6.0, SP4:

  • Sun® SPARCTM running Solaris 2.6 or Solaris 8

  • 750 MB free hard disk space

  • 512 MB RAM

  • One of the following Web Servers:

    • iPlanet Web Server, Enterprise Edition 6.0 , SP1

    • 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_10 for SPARC®. The following patches for JDK 1.2.2_10 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_10 patches

    Patch

    Patch Description

    105181-28  

    Kernel update patch  

    105210-38  

    libaio, libc & watchmalloc patch  

    105284-41  

    Motif 1.2.7: Runtime library patch  

    105568-23  

    Libthread patch  

    105633-57  

    OpenWindows 3.6: Xsun patch  

    105669-10  

    libDtSvc Patch  

    106040-16  

    X Input & Output Method patch  

    106409-01  

    Fixes the Traditional Chinese TrueType fonts  

    106429-02  

    Kernel/drv/mm patch  

    107733-09  

    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_10 patches listed on the http://sunsolve.sun.com Web site.


Windows

Your Microsoft Windows system must meet the following requirements before you can install iPlanet Application Server, Enterprise Edition 6.0, SP4:

  • Microsoft Windows NT 4.0 with SP6a, or Windows 2000 Professional, or Windows 2000 Server SP2, or Windows 2000 Advanced Server

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


  • 512 MB RAM

  • One of the following Web Servers:

    • iPlanet Web Server, Enterprise Edition 6.0, SP1

    • iPlanet Web Server Enterprise Edition 4.1, SP7

    • Microsoft Internet Information Server 4.0 or 5.0

    • Apache Web Server 1.3.19

  • One of the following Web browsers:



Prerequisites for Installation

Before you begin installing iPlanet Application Server, Enterprise Edition 6.0, SP4, 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, 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.0, SP4 with a remote user must install the iPlanet Directory Server 5.0 SP1 patch before installing iPlanet Application Server.

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

  • If you choose not to install the Directory Server Suite on a fresh installation of iPlanet Application Server, Enterprise Edition 6.0, SP4 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.

    The libnspr3.dll file can be found on the product CD in the /Windows/iAS directory.

  • The default directory suffix format in SP4 has been changed to dc=sales,dc=sun,dc=com from the earlier format, o=sales.sun.com. If your applications use LDIF files to populate user directory data, you must change the directory suffix format to that specified during the installation of iPlanet Application Server, Enterprise Edition 6.0, SP4 .

  • Make sure that no other service is running on port 9010 before installing iPlanet Application Server, as the CXS engine uses port 9010 for IIOP, and it gets registered automatically during installation.

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

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

    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.

  • On Solaris platforms, ensure that the machine has its fully qualified domain name mentioned in the /etc/hosts file, as shown in this example:

    #
    # Internet host table
    #
    127.0.0.1 localhost
    192.168.0.255 myhost.company22.com myhost loghost

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

  • Configure the Web Server

    • 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 is available for download at: http://www.iplanet.com/downloads/download

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

    • Webless Installation

      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 "Configuring Apache Web Server".


  • Create a Raw Partition (Optional)

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

  • Create a Mirror Directory for Transaction Manager (Optional)

    Create a directory on a separate drive from the iPlanet Application Server installation directory and specify a path to it - prior to installing the application server.

  • Install and Configure Database Servers

    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, 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 the iPlanet Application Server Administrator's Guide.


    Note PointBase database server and its third party JDBC driver is automatically registered with the Administration Server. It also populates the sample databases of e-Store, J2EEGuide, Database, and Bank sample applications.

    For more information on how to register database drivers and deploy applications, see the iPlanet Application Server Administrator's Guide and the online help of the Deployment Tool.




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.0, SP4 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 SP4".

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


To Install the Patch on Solaris

  1. Copy the contents of the product CD under the Solaris/iAS directory to a local directory on yourmachine.

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

  1. Run the iPlanet Application Server, Enterprise Edition, 6.0 SP4 installation from this local directory.


To Install the Patch on Windows

  1. Copy the contents of the product CD under the Windows\iAS directory to a local directory on your machine.

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

  3. Run the iPlanet Application Server, Enterprise Edition, 6.0 SP4 installation from this local directory.



Installation Options

iPlanet Application Server provides the following installation options:

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 57, or "Running ezSetup on Solaris," on page 74.


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 60, and for installing on Solaris, go to "Starting Solaris Installations," on page 77.


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 SP4


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

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

Upgrading from SP2 and SP3 to SP4 is fairly straightforward. Your applications are automatically migrated to SP4 when you run the SP4 installation program. For more information on upgrading from SP2 and SP3 to SP4, see Upgrading from SP3 to SP4.

The following topics are covered in this section:


Before You Start

Make sure to follow these guidelines before upgrading to SP4:

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

  • Stop iPlanet Application Server before starting the upgrade process. If the current iPlanet Application Server installation is part of a cluster, then you must stop all application servers running in that cluster before upgrading.

  • Make sure that the Directory Server is running.

  • While upgrading from SP1 RevB or SP2 to SP4 on Solaris, existing kas, kxs, kjs and kcs scripts are backed up in the iASInstallDir/ias/backup directory. If you had previously made changes to these scripts, then you must re-enter those values in the iasenv.ksh file, after upgrading.

  • 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) to make those changes.

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

  • The default directory suffix format in SP4 has been changed to dc=sales,dc=sun,dc=com from the earlier format, o=sales.sun.com. If your applications use LDIF files to populate user directory data, you must change the directory suffix format to that specified during the installation of iPlanet Application Server, Enterprise Edition 6.0, SP4 .

  • To enable support for Iona Orbix 2000 1.2.1 on Solaris, you must modify the iasenv.ksh file after upgrading to SP4. For more information, see Chapter 14, "Enabling Support For Corba-Based Clients", in iPlanet Application Server Administration Guide.


Upgrading from SP3 to SP4

Use the following procedure to upgrade to iPlanet Application Server Enterprise Edition 6.0, SP4. You should us e the same procedure to upgrade from SP2 to SP3.

This section includes upgrade procedures for the following platforms:


Upgrading on Windows Platforms

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

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

  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 Typical or 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. Select iPlanet Application Server 6.0.

    Make sure this is the only selected component. Do not select the other components.

  9. Enter the configuration directory administrator ID and password

  10. Click OK when you are asked whether you want to upgrade.

  11. Confirm the configuration directory information displayed and enter the password of the user directory administrator (typically cn=Directory Manager).

  12. Enter the Product Key. The product key is in the welcome letter you received with the product CD.

  13. Click Install to complete the upgrade.

    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, SP4 on Solaris, perform the following steps:


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


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

  2. Run the setup program.

  3. Enter y and press Enter at the Welcome Screen.

  4. Enter y and press Enter to accept the license agreement.

  5. Select 1 to install iPlanet Servers.

  6. Select Typical or Custom as the type of installation.

  7. Change the location of install to the same location as your current installation.

    Press Enter.

    The iPlanet Server Products Components screen appears.

  8. Enter 4 and press Enter to install only the iPlanet Application Server component.

    Make sure this is the only selected component. Do not select the other components.

  9. Select the sub-components shown in subsequent screens.

  10. Enter the fully qualified domain name (hostname.domain.com) of the machine on which you are installing iPlanet Application Server.

  11. Enter the system user and system group names.

  12. Enter the Administrator ID and password for the Configuration Directory Server.

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



  14. Enter the password of the user directory administrator (typically cn=Directory Manager).

  15. Enter the Product Key.
    The product key is in the welcome letter you received with the product CD.

  16. The installation program extracts the required files and completes the upgrade process.

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


Upgrading from SP2 to SP4

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

This section includes upgrade procedures for the following platforms:


On Windows Platforms

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

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

  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. Select iPlanet Application Server 6.0.

    Make sure this is the only selected component. Do not select the other components.

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

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

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


On Solaris Platforms

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

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

  2. Run the setup program.

    For detailed information on the installation procedure, see .

  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. Do not select the other components.

  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 SP4

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

  • iPlanet Application Server Enterprise Edition 6.0, SP4 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, SP4 specifically expects this directory structure.


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


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

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


To upgrade from SP1 RevB to SP4

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

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

    Follow instructions given in Upgrading from SP2 to SP4.

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

    The redeploy utility is shipped along with iPlanet Application Server 6.0 EE SP4 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 SP4. 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 SP4, even after redeploying the application on SP4. You will have to modify the application's source code to use Form Based Authentication.

    • 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 SP4, then you must register a database client compatible with iPlanet Application Server Enterprise Edition 6.0, SP4 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, SP4, on Solaris and Windows platforms.

Table 2-2    Certified Directory Servers

Directory Server

Version

iPlanet Directory Server  

5.0 SP1 (bundled with iPlanet Application Server 6.0, SP4)

4.13  



List of Certified Web Servers


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

Table 2-3    Certified Web Servers

Web Server

Interface

iPlanet Web Server, Enterprise Edition 6.0, SP1  

NSAPI  

iPlanet Web Server, Enterprise Edition 4.1, SP7  

NSAPI  

Microsoft Internet Information Server 4.0 (Windows NT)  

ISAPI  

Microsoft Internet Information Server 4.0 (Windows 2000)  

ISAPI  

Apache 1.3.19  

APACHEAPI  



List of Certified JVMs


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

Table 2-4    Certified JVMs

Platform

Version

JVM

Windows 2000  

Professional, Server  

JDK 1.2.2_010  

Windows NT  

4.0 SP6a  

JDK 1.2.2_010  

Solaris  

2.6, 8  

JDK 1.2.2_10  



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


Note During installation, third party JDBC driver for PointBase database server 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

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 to register either native or third party JDBC 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 SP4 is certified against the third party JDBC database drivers in Table 2-5. In addition, though not yet certified, other third party JDBC database drivers should work with iPlanet Application Server 6.0, SP4.


List of Certified Third Party JDBC Database Drivers


Table 2-5    Third party JDBC database drivers certified in SP4 on Windows and Solaris

Database Vendor

JDBC Driver

Oracle  

Oracle 8i 8.1.7 (Type 4 and Type 2)  

Merant SequeLink  

DataDirect Java 5.1 (all databases supported by DDJ5.1)  

Sybase  

jConnect for JDBC 5.2 Type 4  

IBM DB2  

IBM DB2 7.1 JDBC Client  

Informix  

Informix JDBC v1.5  


List of Certified Native Type 2 Database Servers and Clients

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


Table 2-6    Certified Native Type 2 database servers and clients-in SP4

Database Server

Database Client

Platform

Oracle 8.0.5, 8i  

Oracle8i 8.1.7  

Windows NT/Solaris  

Sybase 12  

Sybase Open/Client System 12  

Windows NT/Solaris  

DB2 7.1  

DB2 6.1, 7.1  

Windows NT/Solaris  

Informix 9.2  

Informix SDK 2.40  

Windows NT/Solaris  

Microsoft SQL Server 7, 2000  

ODBC 3.51  

Windows NT only (client)  


Note For proper functioning of the Sybase global transactions on Solaris, the following Sybase patches for client version 12 should be installed:

  • EBF 9651

  • EBF 9769

These patches are available from the Sybase website at: http://www.sybase.com.




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 November 22, 2001