iServer Version 1.7.0 01/09/2000

-----------------------------------------------------------------------------
CONTENT

    Introduction

    Release Notes
    Requirements
    Installation
    How To

    Feedback

-----------------------------------------------------------------------------
INTRODUCTION

iServer is a small, fast, affordable, scalable and easy to administer
platform independent Application/Web Server written entirely in JavaTM.

iServer is the perfect Web Server for serving static Web pages and a powerful
Application Server for generating dynamic, data driven Web pages using Java
Servlets, Java Server Pages (JSP), iScript, Common Gateway Interface (CGI)
and Server Side Includes (SSI). iServer is also a feature rich Servlet Engine
able to provide Servlet capabilities to any Application/Web Server supporting
Apache Modules, ISAPI, NSAPI, CGI or Java.

iServer provides a rich environment for building and deploying cross
platform Web-based business critical Internet and Intranet applications.
iServer is also a robust, scalable platform that individuals, workgroups
and corporations can use to establish a Web presence.

iServer features include:

Feature         Description
==============  =============================================================
Platform        iServer is built using Java and will run on any platform
Independence    that supports the Java Runtime Environment (JRE) version
                1.1.x or later.

Open Standards  iServer supports open standards such as Java, Servlets, HTTP,
                JSP, CGI, SSI, HTML, TCP/IP, RMI, IIOP, CORBA, JDBC and XML.

High            iServer is built around a high performance multi-threaded
Performance     Web engine that supports Hypertext Transfer Protocol
Web Engine      (HTTP) 1.1.

Keep-Alive /    iServer keeps connections alive across multiple requests
Persistent      reducing the overhead associated with re-establishing a
Connections     connection.
                
                iServer's keep-alive implementation is resistent to denial of
                service attacks. It allows clients to remain connected to the
                server for a specified amount of time and for a specified
                number of requests without having to re-establish a connection
                to the server for each equest.

Request         iServer boots client performance by allowing clients to send 
Pipelinging     multiple requests to the server without blocking.

Virtual Hosts   iServer can be configured to support multiple domains or
                Web sites mapped to the same server each with their own
                content space.

Full-featured   iServer runs Servlets that follow the Java Servlet API 
Servlet Engine  versions 2.0 and 2.1.

                iServer can also be used as the Servlet Engine for any
                Application/Web Server supporting Apache Modules, NSAPI,
                ISAPI, CGI or Java.

Expandable      iServer can be easily expanded using Servlets, JSP, CGI and
Architecture    iScript.

                These servlets can access TCP/IP, RMI, IIOP, CORBA, JDBC and
                XML to create highly scalable n-tier enterprise solutions.

Scalable        iServer's built-in load-balancing cluster redirector and 
Solution        cluster proxy create a robust, fault-resistant, scalable
                solution where a group of servers seamlessly work together
                to meet the needs of a large number of clients.

                iServer leverages Java's multiprocessor support to increase
                the number of users that a single server can service.

Fault Tolerant  iServer provides a robust environment for serving Web pages
                and for running server side Internet applications. iServer's
                crash protected and recovery technology automatically traps,
                recovers from and logs exceptions. Additionally iServer
                protects the integrity of the server environment by
                preventing exceptions occuring in one request handler from
                affecting other requests that the server is processing.

                iServer includes integrated failover clustering support where
                a group of servers are used to ensure that even a some of the
                servers fail, that others take over and make sure that the
                site continues to be available for client requests. This
                provides customers with a reliable means of ensuring that the
                site stays up in the event of a hardware or software failure.

Multi-Threaded  iServer simultaneously services multiple client requests,
                logs access/errors/events and manages sessions using a pool
                of worker threads. iServer's worker thread pool ensures
                scalability and smooth performance.

Object          Using iServer developers create object oriented reusable
Oriented        modules, Servlets, that encapsulate business logic used to
                generate dynamic content and to automate tasks.

n-Tier          iServer is an integral part of client/server computing,
Solution        where a Web Browser is responsible for the presentation,
                a Web Server for creation and delivery of content, an
                Application Server for the business logic and a Database
                Server for storage and retrieval of information.

Data Access     Using iServer developers can use JDBC to create data-driven
                Web-based applications that have access to a variety of data
                sources.

Tiny Footprint  Unlike other Web and Application Server that require
                considerable resources, iServer uses less than 70K of disk
                space for the base package and under 175K for the works.

Server Side     iScript makes it easy to deliver personalied customized
Scripting       content to users. Using iScript dynamic and data driven Web
                pages can be easily generated from templates.
                
                iScript's scripting langage is simular to Visual Basic Script
                (VBScript). iScripts templates are simular to Microsoft's
                Active Server Pages (ASP), but are platform independant.

Servlet Tag     iServer supports template pages with embedded
                <servlet></servlet> tags.

Common Gateway  iServer fully supports the Common Gateway Interface (CGI).
Interface

Server Side     iServer generates pages that contain Server Side Includes 
Includes        (SSI).

Database        iServer has built-in support for database connection pooling
Connection      that when used provides performance optimization and  
Pools           efficient resource allocation.

Security /      iServer access control allows resources to be protected from 
Access Control  users or computers access using Web-based authentication.

                Users, groups, computers, realms, access rights, resources
                and access control lists (ACL) can be easily defined using
                the iServer Administrator.

                Entries can be stored in flat files or in any JDBC accessible
                database.

                iServer supports the Basic authentication scheme with BASE64
                encoding.

Session         iServer is able to maintain information across multiple
Support         requests using Cookie or URL based user sessions.

File Cache      iServer maintains an optimized cache in memory of the most
                recently accessed files to improve performance and to reduce
                disk IO.

Multi-Part      iServer multi-part form technology allows file uploads 
Forms / File    without impacting the server's memory footprint. The files
Uploads         being uploaded are written to disk as they are received
                without first being loaded into memory.

Administration  iServer supports centralized Web-based and Command-line
                administration of a single server or a group of servers.

                Administrators can securely monitor and manage multiple
                servers remotely using any Web browser.

                iServer can also be directly administered using simple
                commands that can be easily integrated into user scripts.

                The Administrator can be used to monitor, stop, restart and
                configure any number of servers.

Servlet         Developers and administrators can dynamically load and unload
Load / Unload   Servlets without having to stop and restart the server.

Fully           Developers can easily reconfigure iServer by editing simple
Configurable    text files and html pages.

                All server parameters, session, logger, file aliases,
                servlets, virtual hosts, workgroup servers, filters, mime
                types, error messages, connection pools, users groups,
                computers, realms, access rights, resources, access control
                lists and html templates are fully configurable.

Log Files       iServer generates detail logs of server access, errors and
                events. Log entries can be sent to the console's
                stdout/stderr, written to a flat file on the disk or to any
                JDBC accessible database. Log files can rollover daily,
                weekly, monthly or never. Access log entries are added using
                user definable templates.

Open Java API   iServer exposes variables and methods that can be used to
                easily integrate the iServer engine into any 3rd party
                applications.

                The iServer engine can be easily accessed from Java or from
                any other programming or scripting language which interfaces
                with Java.

Examples        iServer distributions include numerous working examples with
                full source code demonstrating may of the key features
                supported by iServer.

Online          All iServer documentation is available as Web pages.
Documentation

Other           iServer supports other functionality found in professional
                Application/Web Servers.

-----------------------------------------------------------------------------
RELEASE NOTES

iServer Version 1.7.0 01/09/2000 features Apache/ISAPI/NSAPI
iServer Gateway with load-balancing, failover and client session support;
ClusterProxy with failover and client session support; adds support for
Servlet and Mimetype Chaining and for Virtual Hosts.

The release also features combined servlets and filters configuration files;
allows Java VM parameters to be specified in JAVA_EXE environmental variable;
adds session support to the ClusterRedirector; allows configuration of
additional server parameters; adds new template and session configuration
variables; allows stopping/restarting server from the command line or from
other programs; includes new and updated examples, expands documented API,
includes notes for using iServer as Windows 9x/NT Service, contains many more
changes, bug fixes and updates to configuration files and documentation.

You can help shape the development of iServer, send your comments,
suggestions and problems to support@servertec.com.

-----------------------------------------------------------------------------
REQUIREMENTS

Storage 
    1 MB for classes and executables 
    3.5 MB for classes, executables, examples and documentation

JRE
    Java Runtime Environment (JRE) version 1.1.x or later.
    Download the JRE from JavaSoft at:
    http://java.sun.com/products/jdk/1.2/jre/
    http://java.sun.com/products/jdk/1.1/jre/

or JDK
    Java Development Kit (JDK) version 1.1.x or later.
    Download the JDK from JavaSoft at:
    http://java.sun.com/products/jdk/1.2/
    http://java.sun.com/products/jdk/1.1/

-----------------------------------------------------------------------------
INSTALLATION - iServer

Use the following instructions to install iServer on Windows 9x/NT.

  1. Install Java JDK version 1.1.x or later. Follow JavaSoft's instructions 
     for installing the Java JDK.

  2. Unzip downloaded file(s). Follow instructions for extracting files from
     a zip file using folder names. Normally extract to c:\

  3. Using <iws_path>\install\win32\vars.bat as a template, define the
     following environmental variables in c:\autoexec.bat file.

     set JAVA_EXE = <java_path>\bin\java.exe
     set CLASSPATH = <iws_path>\classes;
        <iws_path>\classes\iws.jar;
        <iws_path>\classes\servlet.jar;
        <iws_path>\servlets;
        <iws_path>\samples\servlets;
        %CLASSPATH%
     set PATH = <iws_path>\bin\win32;%PATH%

     <iws_path>		the directory where the iServer was installed,
                  normally c:\iws.
     <java_path>	the base directory where Java was installed.

  4. Restart the computer. 

Use the following instructions to install iServer on Linux/Unix. 

  1. Install Java JDK version 1.1.x or later. Follow JavaSoft's instructions 
     for installing the Java JDK. 
  
  2. Login on account where iServer will be installed. 
  
  3. Unzip the downloaded file(s). 
  
     gzip -d filename 
  
  4. Untar the resultant file(s). 
  
     tar -xvpf filename 
  
  5. If not in root directory, move iws to root directory. 
  
     mv iws / 
  
  6. Make executables, as needed. 
  
     cd /iws/bin/linux 
     ./makeiws 
  
  7. Using iws_path/install/linux/iws.sh as a template, define the following 
     environmental variables in the user's login script. 
  
     export JAVA_EXE = "<java_path>/bin/java" 
     export CLASSPATH = "<iws_path>/classes:
        <iws_path>/classes/iws.jar:
        <iws_path>/classes/servlet.jar: 
        <iws_path>/servlets: 
        <iws_path>/samples/servlets: 
        ${CLASSPATH}" 
     export PATH = "<iws_path>/bin/linux:${PATH}" 
     
     <iws_path>		the directory where the iServer was installed, 
                  normally /iws.  
     <java_path>	the base directory where Java was installed.  
  
  8. Logout and log back in. 

-----------------------------------------------------------------------------
INSTALLATION - Apache Gateway

Use the instructions below to configure the Apache Web Server or other 
Application/Web Servers running on Windows 9x/NT supporting Apache Modules 
to use iServer as their Servlet Engine. 

  1. Install and configure iServer.

  2. Install and configure Apache Web Server or other Application/Web 
     Server that supports Apache Modules to use Dynamically Loadable 
     Modules. 

  3. Add the following lines to the httpd.conf file. 
	 
     LoadModule apache_gateway_module mod_path 
     <Location <alias>> 
        SetHandler apache-gateway-handler 
        Debug <boolean>
        Server <host_name>:<port>
        Interval <interval>
        Retry <retry>
     </Location> 
   
     <alias>      the URI used to access the iServer Apache Gateway, 
                  normally /servlet.  
     <boolean>    whether to make a dump of the request/response to 
                  \temp\apacheGateway.log [ true | false ], 
                  normally false.
     <host_name>  the name of the host computer running iServer. If iServer
                  is running on the same computer as the iServer Apache
                  Gateway then localhost can be used.
     <interval>   the number of milliseconds to wait before attempting to
                  retry a workgroup server that is down, a value greater than
                  or equal to 50 ms, normally 1000 ms.
     <mod_path>   the path to the iServer Apache Gateway,
                  normally c:/iws/bin/win32/apacheGateway.dll.  
     <port>       is the port number iServer is listening on,
                  normally port 8080.
     <retry>      the number of workgroup server to try to connect to,
                  normally 3.
     Notes:
     A separate Server parameter must be entered for each workgroup server.

  4. Restart the computer. 

Use the instructions below to configure the Apache Web Server or other 
Application/Web Servers running on Linux/Unix supporting Apache Modules 
to use iServer as their Servlet Engine. 
  
  1. Install and configure iServer.

  2. Install and configure Apache Web Server or other Application/Web
     Server that supports Apache Modules to use Dynamically Loadable 
     Modules. 

  3. Add the following lines to the httpd.conf file. 

     LoadModule apache_gateway_module <mod_path>
     <Location <alias>>
        SetHandler apache-gateway-handler 
        Debug <boolean>
        Server <host_name>:<port>
        Interval <interval>
        Retry <retry>
     </Location> 
	  
     <alias>      the URI used to access the iServer Apache Gateway,
                  normally /servlet.
     <boolean>    whether to make a dump of the request/response to 
                  /tmp/apacheGateway.log [ true | false ], 
                  normally false.  
     <interval>   the number of milliseconds to wait before attempting to
                  retry a workgroup server that is down, a value greater than
                  or equal to 50 ms, normally 1000 ms.
     <host_name>  the name of the host computer running iServer. If iServer
                  is running on the same computer as the iServer Apache
                  Gateway then localhost can be used.
     <mod_path>   the path to the iServer Apache Gateway,
                  normally /iws/bin/linux/apacheGateway.so.
     <port>       is the port number iServer is listening on,
                  normally port 8080.
     <retry>      the number of workgroup server to try to connect to,
                  normally 3.

     Notes:
     A separate Server parameter must be entered for each workgroup server.

  4. Restart the Apache Server.

-----------------------------------------------------------------------------
INSTALLATION - ISAPI Gateway

Use the instructions below to configure Microsoft Personal Web Server, 
Internet Information Server or other Application/Web Servers supporting ISAPI 
to use iServer as their Servlet Engine. 

  1. Install and configure iServer.

  2. Install and configure Microsoft Personal Web Server, Internet 
     Information Server or other Application/Web Server that supports 
     ISAPI. 

  3. Define variables used by the ISAPI Gateway.

     For Windows 9x add the following entries to iserver.ini file in
     c:\windows and for Windows NT add the following entries to iserver.ini
     file in c:\winnt.

     [isapigateway]
     DEBUG=<boolean>
     SERVER=<hostname>:<port>
     INTERVAL=<interval>
     RETRY=<retry>
     ISERVER_URI=<alias>
     IGATEWAY_URI=/igateway/isapiGateway.dll

     <alias>      the URI used to access the iServer ISAPI Gateway, 
                  normally /servlet.
     <boolean>    whether to make a dump of the request/response to 
                  \temp\isapiGateway.log [ true | false ], 
                  normally false.  
     <host_name>  the name of the host computer running iServer. If iServer
                  is running on the same computer as the iServer ISAPI
                  Gateway then localhost can be used.
     <interval>   the number of milliseconds to wait before attempting to
                  retry a workgroup server that is down, a value greater than
                  or equal to 50 ms, normally 1000 ms.
     <port>       is the port number iServer is listening on,
                  normally port 8080.
     <retry>      the number of workgroup server to try to connect to,
                  normally 3.
  
     Notes:
     A separate Server parameter must be entered for each workgroup server.

  4. Add the following Virtual Directory. 

     For Microsoft Personal Web Server using Personal Web Manager click 
     on Advanced and add the following Virtual Directory. 
   
     Directory    the directory where the iServer ISAPI Gateway was 
                  installed, normally c:\iws\bin\win32.  
     Alias        the base URI used to access the ISAPI Extension, 
                  normally igateway.  
     Access       the privileges, normally Execute.  
  
     For Microsoft Internet Information Server using Internet Service 
     Manager right mouse click on the Web Site, then click on New, 
     followed by Virtual Directory and Use the New Virtual Directory 
     Wizard to add the following Virtual Directory. 
      
     Alias        the base URI used to access the ISAPI Extension, 
                  normally igateway.  
     Directory    the directory where the iServer ISAPI Gateway was 
                  installed, normally c:\iws\bin\win32.  
     Permissions  the privileges, normally Execute.
       
     For Microsoft Internet Information Server after adding the Virtual 
     Directory above, select the newly created Virtual Directory by
     right mouse clicking on igateway, then click on Properties and then
     on Directory Security tab. Finally in the Directory Security tab
     click on Edit and then set the Authentication Methods by selecting
     Allow Anonymous Access and clearing Basic Authentication and
     Windows NT Challenge/Response. 

  5. Define the ISAPI Filter. 

      For Microsoft Personal Web Server update the Registry. 
  
        i.  Modify c:\iws\install\win32\pws.reg as needed. 
         
            "Filter DLLs"="c:\\iws\\bin\\win32\\isapiGateway.dll" 
         
            Note: Each \\ represents a single \ 
  
        ii. Register it.
  
            regedit c:\iws\install\win32\pws.reg 
  
      For Microsoft Internet Information Server using Internet Service 
      Manager right mouse click on the Web Site, then click on Properties 
      and then on ISAPI Filters tab. Finally in ISAPI Filters tab add the 
      following Filter. 
   
      Filter Name   the name of the Filter, normally isapiGateway.  
      Executable    the path to the ISAPI Filter, 
                    normally c:\iws\bin\win32\isapiGateway.dll.  
    
  6. Restart the computer. 

-----------------------------------------------------------------------------
INSTALLATION - NSAPI Gateway

Use the instructions below to configure the Netscape FastTrack, 
Enterprise Server or other Application/Web Servers supporting NSAPI 
to use iServer as their Servlet Engine. 

  1. Install and configure iServer.

  2. Install and configure Netscape FastTrack, Enterprice Server or
     other Application/Web Server that supports NSAPI. 

  3. Add the following Mime-Type to the mime.types file. 

     type=magnus-internal/servlet exts=servlet 

  4. Add the following lines in the Init section before 
     <Object name=default> to the obj.conf file. 
  
     Init fn=load-modules funcs=process_request shlib="<path>" 
	
     <path>       the path to the iServer NSAPI Gateway, 
                  normally c:/iws/bin/win32/nsapiGateway.dll.  

  5. Add the following lines in the NameTrans section in 
     <Object name=default> to the obj.conf file. 
    
     NameTrans fn=assign-name from=<alias>* name=igateway 
		
     alias        the URI used to access the iServer NSAPI Gateway, 
                  normally /servlet.  

  6. Add the following lines in the Service section in 
     <Object name=default> to the obj.conf file. 
    
     Service fn=process_request method="(<methods>)" 
        type=magnus-internal/servlet 
		
     methods      the request methods to use, normally GET|POST|HEAD.

  7. Add the following lines after <Object name=default> to the obj.conf
     file.

     <Object name=igateway> 
        ObjectType fn=force-type type=magnus-internal/servlet 
        Service fn=process_request 
          method="(<methods>)" 
          type=magnus-internal/servlet 
          debug=<boolean>
          server=<host_name>:<port>
          interval=<interval>
          retry=<retry>
     </Object> 
   
     <boolean>    whether to make a dump of the request/response to 
                  \temp\nsapiGateway.log [ true | false ], 
                  normally false.  
     <host_name>  the name of the host computer running iServer. If iServer
                  is running on the same computer as the iServer NSAPI
                  Gateway then localhost can be used.
     <interval>   the number of milliseconds to wait before attempting to
                  retry a workgroup server that is down, a value greater than
                  or equal to 50 ms, normally 1000 ms.
     <methods>    the request methods to use, normally GET|POST|HEAD.  
     <port>       is the port number iServer is listening on,
                  normally port 8080.
     <retry>      the number of workgroup server to try to connect to,
                  normally 3.

     Notes:
     A separate Server parameter must be entered for each workgroup server.
    
  8. Restart the computer. 

-----------------------------------------------------------------------------
INSTALLATION - CGI Gateway

Use the instructions below to configure other Application/Web Servers running 
on Windows 9x/NT supporting Common Gateway Interface (CGI) to use iServer 
as their Servlet Engine. 

  1. Install and configure iServer.

  2. Install and configure the Application/Web Server that supports CGI 
     enabling CGI executables. 

  3. Define variables used by the CGI Gateway. 

     For Windows 9x add the following environmental variables to the 
     autoexec.bat file. 
  
     set ISERVER_HOSTNAME = <host_name>
     set ISERVER_PORT = <port> 
     set IGATEWAY_DEBUG = <boolean>
      
     <boolean>    whether to make a dump of the request/response to 
                  \temp\cgiGateway.log [ true | false ], normally false.  
     <host_name>  the name of the host computer running iServer. If iServer
                  is running on the same computer as the iServer CGI Gateway
                  then localhost can be used.
     <port>       is the port number iServer is listening on,
                  normally port 8080.
  
     For Windows NT using the Control Panel double-click on System then 
     click on Environment tab and add the following System Variables. 
      
     Variable            Value  
     IGATEWAY_DEBUG      whether to make a dump of the request/response to
                         \temp\cgiGateway.log [ true | false ], 
                         normally false.  
     ISERVER_HOSTNAME    the name of the host computer running iServer. 
                         If iServer is running on the same computer as the 
                         iServer CGI Gateway then localhost can be used.  
     ISERVER_PORT        is the port number iServer is listening on, 
                         normally port 8080.
  
  4. Add the following Virtual Directory. 
   
     Alias        the URI used to access the iServer CGI Gateway, 
                  normally /servlet.  
     Directory    the path the iServer CGI Gateway, 
                  normally c:\iws\bin\win32\cgiGateway.exe.  
     Permissions  the privileges, normally Execute.  
  
  5. Restart the computer. 

Use the instructions below to configure other Application/Web Servers running 
on Linux/Unix supporting Common Gateway Interface (CGI) to use iServer 
as their Servlet Engine. 
  
  1. Install and configure iServer.

  2. Install and configure the Application/Web Server that supports CGI 
     enabling CGI executables. 

  3. Define the following environmental variables in the server's login 
     script. 

     export ISERVER_HOSTNAME = <host_name> 
     export ISERVER_PORT = <port> 
     export IGATEWAY_DEBUG = <boolean> 
	  
     <boolean>    whether to make a dump of the request/response to 
                  /tmp/cgiGateway.log [ true | false ], normally false.  
     <host_name>  the name of the host computer running iServer. If iServer
                  is running on the same computer as the iServer CGI Gateway
                  then localhost can be used.
     <port>       is the port number iServer is listening on,
                  normally port 8080.

  4. Add the following Virtual Directory to the server's configuration 
     file. 
      
     Alias        the URI used to access the iServer CGI Gateway, 
                  normally /servlet.  
     Directory    the path the iServer CGI Gateway, 
                  normally /iws/bin/linux/cgiGateway.  
     Permissions  the privileges, normally Execute.  
  
  5. Logout and log back in. 

  6. Restart the Server.

-----------------------------------------------------------------------------
INSTALLATION - Java Gateway

Use the instructions below to configure other Application/Web Servers running 
on Windows 9x/NT supporting Common Gateway Interface (CGI) to use iServer 
as their Servlet Engine. 

  1. Install and configure iServer.

  2. Install and configure the Application/Web Server that supports CGI 
     enabling CGI executables. 

  3. Define variables used by the Java Gateway. 

     For Windows 9x add the following environmental variables to the 
     autoexec.bat file. 
  
     set ISERVER_HOSTNAME = <host_name>
     set ISERVER_PORT = <port> 
     set IGATEWAY_DEBUG = <boolean> 
     set CLASSPATH = <class_path>;%CLASSPATH% 
     set JAVA_EXE=<java_path>\bin\java.exe 
      
     <boolean>    whether to make a dump of the request/response to 
                  \temp\javaGateway.log [ true | false ],
                  normally false.
     <class_path> the path to the iServer Java Gateway, 
                  normally c:\iws\classes\isg.jar.  
     <host_name>  the name of the host computer running iServer. If iServer
                  is running on the same computer as the iServer Java Gateway
                  then localhost can be used.
     <java_path>  the base directory where Java was installed.  
     <port>       is the port number iServer is listening on,
                  normally port 8080.
  
     For Windows NT using the Control Panel double-click on System then 
     click on Environment tab and add the following System Variables. 
      
     Variable            Value  
     CLASSPATH           the path to the iServer Java Gateway, 
                         normally c:\iws\classes\isg.jar;%CLASSPATH%.  
     IGATEWAY_DEBUG      whether to make a dump of the request/response to 
                         \temp\javaGateway.log [ true | false ], 
                         normally false.  
     ISERVER_HOSTNAME    the name of the host computer running iServer. 
                         If iServer is running on the same computer as the 
                         iServer Java Gateway then localhost can be used.  
     ISERVER_PORT        is the port number iServer is listening on, 
                         normally port 8080.
     JAVA_EXE            the base directory where Java was installed.  

  4. Add the following Virtual Directory. 
   
     Alias        the URI used to access the iServer Java Gateway, 
                  normally /servlet.  
     Directory    the path the iServer Java Gateway executable, 
                  normally c:\iws\bin\win32\javaGateway.exe.  
     Permissions  the privileges, normally Execute.  
  
  5. Restart the computer. 

Use the instructions below to configure other Application/Web Servers running 
on Linux/Unix supporting Common Gateway Interface (CGI) to use iServer 
as their Servlet Engine. 
  
  1. Install and configure iServer.

  2. Install and configure the Application/Web Server that supports CGI 
     enabling CGI executables. 

  3. Define the following environmental variables in the server's login 
     script. 

     export ISERVER_HOSTNAME = <host_name> 
     export ISERVER_PORT = <port> 
     export IGATEWAY_DEBUG = <boolean> 
     export CLASSPATH = "<class_path>:${CLASSPATH}" 
     export JAVA_EXE = "<java_path>/bin/java" 
      
     <boolean>    whether to make a dump of the request/response to 
                  /tmp/javaGateway.log [ true | false ], normally false.  
     <class_path> the path to the iServer Java Gateway, 
                  normally /iws/classes/isg.jar.  
     <host_name>  the name of the host computer running iServer. If iServer
                  is running on the same computer as the iServer Java Gateway
                  then localhost can be used.
     <java_path>  the base directory where Java was installed.  
     <port>       is the port number iServer is listening on,
                  normally port 8080.

  4. Add the following Virtual Directory to the server's configuration 
     file. 
      
     Alias        the URI used to access the iServer Java Gateway, 
                  normally /servlet.  
     Directory    the path the iServer Java Gateway, 
                  normally /iws/bin/linux/javaGateway.  
     Permissions  the privileges, normally Execute.  
  
  5. Logout and log back in. 

  6. Restart the Server.

-----------------------------------------------------------------------------
HOW TO

To start iServer:

  Open a command shell and enter:

    iws { <path> | <archive> }

  where:

  <archive>   the JAR/ZIP archive containing the Web-site to use.
  <path>      the directory where iServer was installed or deployed,
              normally c:\iws for WIN32 and /iws for Linux/Unix.

To test iServer:

  Run iServer and from a Web Browser enter:

    http://<host>:<port>

  where:

  <host>      the name of the computer running iServer, normally localhost
  <port>      the port number iServer is listening on,
              normally port 8080.

  Then click on Samples, click on the sample to run and click on run.

To administer iServer:

  Asssuming iServer is already running from a Web Browser enter:

    http://<host>:<port>/admin.html

  where:

  <host>      the name of the computer running iServer, normally localhost
  <port>      the port number iServer is listening on,
              normally port 8080.

  Then login by entering admin for Username and admin for Password.
  Once login click on the name of the Server to administer and then in the
  Control Panel click on Manage.

To stop iServer:

  Assuming iServer is already running from a command shell enter:

    stop_iws <host>:<port> <id> <password>
  
  where:

  <host>      the name of the computer running iServer, normally localhost
  <id>        the user id of the administrator, normally admin
  <password>  the password used by the administrator, normally admin
  <port>      the port number iServer is listening on,
              normally port 8080.

  or from a Web Browser enter:

    http://<host>:<port>/admin.html

  where:

  <host>      the name of the computer running iServer, normally localhost
  <port>      the port number iServer is listening on,
              normally port 8080.

  Then login by entering admin for Username and admin for Password.
  Once login click on the name of the Server to shutdown, normally
  localhost:8080 and then in the Control Panel click on the STOP botton.

To use the iServer Gateway:

  Install and configure iServer and the appropriate iServer Gateway, start
  iServer and the Web/Application Server and then from a Web Browser enter:

    http://<host>:<port>/servlet/HelloServlet

  where:

  <host>      the name of the computer running the Application/Web Server,
              normally localhost
  <port>      the port number the Application/Web Server is listening on,
              normally 80
  
-----------------------------------------------------------------------------
FEEDBACK

At Servertec, we value what you have to say. We are committed to defining
our products based on your needs. Please send us your questions, comments,
suggestions and problems.

Product Information     sales@servertec.com
Sales information about new product availability, costs and licensing.

Technical Support       support@servertec.com
Answers to Servertec product questions.

Web Site                webmaster@servertec.com
Questions, comments or problems concerning the Servetec Web site.

General Information

    Servertec
    18 Oakwood Avenue
    Kearny, NJ 07032

    Phone: 201-998-1048 
