Table of Contents
This document describes the steps required to install and configure Enhydra Director.
For the most up-to-date information on Director, see the Enhydra Director Working Group .
Table of Contents
Director runs on Windows NT, Solaris, and Linux. Additionally, if you build Enhydra from the open source distribution, the Director module should compile and run on most Unix systems supported by Netscape/IPlanet web servers.
Note: Enhydra Director requires TCP/IP networking support. If you have not already done so, configure TCP/IP on at least one of your system's network interfaces.
Hardware:
Intel 80386 or later CPU. (Pentium 200Mhz or faster recommended)
Sparc-compatible system higher 64 MB RAM (128 MB Recommended)
Operating System: Windows NT 4.0, Service Pack 6 or later.
Web servers:
IPlanet/Netscape Enterprise Server version 4.0 or higher
Microsoft Internet Information Server, version 4.0 or later
Apache Web Server version 1.3.9 or later
Hardware: Sparc-compatible system with 64 MB RAM (128 MB Recommended)
Operating System: Sun Solaris version 2.6
Web servers:
IPlanet/Netscape Web Server version 4.0 or higher
Apache Web Server version 1.3.9 or later
Hardware:
Intel 80386 or later CPU. (Pentium 200Mhz or faster recommended)
Sparc-compatible system higher 64 MB RAM (128 MB Recommended)
Operating System: Version 2.2 kernel or later with support for recent versions of the glibc C library. (Redhat 6.1 recommended)
Web servers:
IPlanet/Netscape Web Server version 4.0 or higher
Apache Web Server version 1.3.9 or later
Before installing Enhydra Director, determine the following:
The machines on which you will be running Enhydra Multiserver.
The applications you will be running on the Enhydra Multiservers.
For each application:
The name of the machine and the port number on which each instance of the application will run. The port number is the 'port' used when configuring a connection of type 'EnhydraDirector' using the Multiserver Administration console.
The URL prefix used to identify the application. (For example '/demoApp')
Whether the application requires session affinity. That is, whether requests for the same session to an application should always be routed to the application server instance that created the session. Unless your application supports distribution of its sessions among other instances, you should assume that session affinity is needed. If your application does not use session information at all, you do NOT need session affinity.
The name of the web server instance on which you wish to configure Enhydra Director.
The TCP port of the web server instance on which you intend to configure Enhydra Director. By default, this is port 80.
For Netscape, determine:
The location of the obj.conf file for your web server instances. On Windows NT, this is typically:
C:\Netscape\Server4\<instance>\config\obj.confOn Unix this is often
/usr/netscape/server4/<instance>/config/obj.conf
Where to install the EnhydraDirector files. On Windows NT, we recommend:
C:\Netscape\EnhydraDirectorOn Unix, we recommend:
/usr/netscape/EnhydraDirector
For Apache, determine:
The location of the configuration files for Apache, typically
/usr/local/apache/conf
The location of the executables directory for your Apache server, typically
/usr/local/apache/bin
The following procedure assumes that you are using the Multiserver Administration console to add the connections for the application.
Create Enhydra Director connections for your application. - Bring up the MultiServer Administration page for your Enhydra server instance.
Select your application in the application list.
Click on the 'Connections' tab to manage connections for your application instance.
Within the 'Connections' tab, click 'Create'. A 'new connection' dialog box will appear.
In the dialog box, check 'EnhydraDirector' as the connection type.
Fill in the URL prefix and port. Also, if session affinity is NOT to be enabled, change the session affinity box from 'true' to 'false'.
Click 'OK' to accept the new connection.
In the main MultiServer admin page, click the 'Save State' floppy-disk icon to save your changes to the MultiServer configuration file. Click 'OK' to accept the rewrite of the configuration file.