######################################################################
#  (C) Copyright IBM Corporation 1998.
#  All rights reserved.
######################################################################
 
Welcome to IBM ServletExpress Version 1.0 Beta 2!

This README includes the following topics:
>> THE JAVAONE CD
>> SUPPORTED PLATFORMS
>> DOCUMENTATION
>> PRODUCT FORUM
>> SERVICE AND PRODUCT SUPPORT
>> BROWSER REQUIREMENT FOR SERVLETEXPRESS MANAGER
>> PAGE COMPILATION
>> ENABLING LOGGING
>> KNOWN DEFECTS
 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>> THE JAVAONE CD
The JavaOne CD contains ServletExpress Version 1.0 Beta 2 for Windows NT only.
Information in this README file concerning ServletExpress on other platforms does
not apply to the JavaOne CD. The following defects are specific to the JavaOne CD:
- The ServletExpress sample servlets and applications do not work.
- Netscape Enterprise Server and FastTrack Server Version 3.51 are not supported.
- IBM ServletExpress CORBA Support is not supported.
- The Stop and Restart buttons in the ServletExpress Manager do not work.
- Servlet chaining and filtering is not supported.
To obtain fixes to these and other defects described in this README file,
please download the the latest ServletExpress code package from the Web site:
	http://www.ibm.com/java/servexp/

>> SUPPORTED PLATFORMS
IBM ServletExpress Version 1.0 Beta 2 supports:
- Domino Go Webserver 4.6.1 and 4.6.2 for Windows NT, Sun Solaris, and AIX
- Netscape Enterprise Server Version 2.01 and higher
  for Windows NT, Sun Solaris, and AIX
- Netscape FastTrack Server Version 2.01 and higher
  for Windows NT, Sun Solaris, and AIX
- Microsoft Internet Information Server Version 2.x, 3.x, or 4.0 for Windows NT
- Apache Server Version 1.2.4 for Sun Solaris and AIX
 

>> DOCUMENTATION
When you install IBM ServletExpress, HTML copies of the 
ServletExpress Webmaster's Guide, Web Programmer's Guide,
and this README file are installed on your Domino Go Webserver.
Use your browser to open:
- For Windows NT, open <servletexpress_root>\system\en_US\doc\index.html,
where <servletexpress_root> is the path where ServletExpress is installed.
- For AIX, open /usr/lpp/ServletExpress/system/en_US/doc/index.html.
- For Sun Solaris, open /opt/ServletExpress/system/en_US/doc/index.html.

For the most current level of ServletExpress documentation for Domino Go
Webserver, refer to the Documentation page of the Web site:
	http://www.ibm.com/java/servexp/sedoco.html

The Documentation page contains links for the following documents:
- ServletExpress Webmaster's Guide (HTML and PDF)
- ServletExpress Web Programmer's Guide (HTML and PDF)
- JavaSoft Java Servlet API Whitepaper
- JavaSoft Page Compilation tutorial
- Javadoc for Java Servlet API
- Javadoc for the ServletExpress extensions
- This README


>> PRODUCT FORUM
Use the ServletExpress Forum to communicate with other users and get
answers to questions.  Use your browser to open:
	http://www.ibm.com/java/servexp/sesupport.html
 
>> SERVICE AND PRODUCT SUPPORT
If you need service for ServletExpress, use the ServletExpress Forum to
submit your request.


>> BROWSER REQUIREMENT FOR SERVLETEXPRESS MANAGER
ServletExpress Manager is the user interface for managing servlets.  To run the
Manager, you need an appletviewer or a browser that supports Java Development 
Kit (JDK) 1.1. Examples of browsers that support JDK 1.1 are:
- Netscape Communicator 4.03 or 4.04 with the JDK 1.1 patch (available at
http://developer.netscape.com/software/jdk/download.html).
- Microsoft Internet Explorer 4
- Sun HotJava 1.1

>> PAGE COMPILATION
If your your servlets are invoked from SHTML and JHTML files, place those files
in the <servletexpress_root>\public_html directory, where <servletexpress_root>
is the path where ServletExpress is installed.

>> ENABLING LOGGING
This section contains instructions for enabling the ServletExpress engine logging.
  >>> Native DLL Logging
  These log messages are produced by the Web server C code before entering Java.
  To control this type of logging:
  1. Open the jvm.properties file, which is in the following path: 
  <servletexpress_root>\properties\server\ServletExpress\servletservice
  
  2. To enable logging:
  a. Set the property ncf.native.logison=true.
  b. Set the property ncf.native.logfile=<servletexpress_root>\logs\native.log.
  c. Restart your Web server.
  
  3. To disable logging:
  a. Set the property ncf.native.logison=false.
  b. Restart your Web server.
  
  >>> Java Standard Out Log
  Any System.out and System.err prints go to this log.
  To control this type of logging:
  1. Open the jvm.properties file, which is in the following path: 
  <servletexpress_root>\properties\server\ServletExpress\servletservice
  
  2. To enable logging to a file:
  a. Set the property ncf.jvm.stdoutlog.enabled=true.
  b. Set the property ncf.jvm.stdoutlog.file=true
  c. Set the property ncf.jvm.stdoutlog.filename=<servletexpress_root>\logs\ncf.log.
  
  3. To enable logging to a Java console window:
  a. Set the property ncf.jvm.stdoutlog.enabled=true.
  b. Set the property ncf.jvm.stdoutlog.file=false.
  
  4. To disable logging:
  a. Set the property ncf.jvm.stdoutlog.enabled=false.
  b. Set the property ncf.jvm.stdoutlog.file=false.
  

>> KNOWN DEFECTS
The defects listed below are organized by server and platform.
There are workarounds for most of the defects.
  >>> Session Support
  Session support is enabled by default. However, the following defects are known:
  - URL rewriting is not working.
  - The ServletExpress Manager does not yet support configuring session support.
  To configure session support, you must edit the session properties file, which is
  <servletexpress_root>\properties\server\ServletExpress\servletservice\sessions.properties.
  After you edit the file, you must restart the service or the Web server for the 
  changes to take effect. For a detailed description of session support,
  refer to the Java Server information at http://java.sun.com. The session properties are:

enable.sessions - set to true by default
enable.urlrewriting - set to false by default, but not working yet
enable.cookies - set to true by default
enable.protocolswitchrewriting - set to false by default;

session.inavalidationinterval - set to 10000 by default (in milliseconds)
session.swapinterval - set to 10000 (in ms)
session.persistence - set to true
session.swapdirectory - must an accessible path name. If commented out with a #,
	ServletExpress will create a directory under the
	<servletexpress_install_root>\logs directory.
session.maxresidents - default at 1024
session.invalidationtime - default 1800000 in ms

session.cookie.name- default sesessionid
session.cookie.comment - default ServletExpress Session Support
session.cookie.domain - leave commented out with a # unless you want to restrict who
	can have sessions with cookies
session.cookie.maxage - leave commented out with a # unless you want to restrict who
	can have sessions with cookies
session.cookie.path - leave commented out with a # unless you want to restrict who
	can have sessions with cookies
session.cookie.secure - leave commented out with a # unless you want to restrict who
	can have sessions with cookies

// new for clustering
session.server.host - the hostname or IP address of the instance of ServletExpress
	that will be contacted for sessions.  If this property is not present, is
	commented out with a #, or its value is blank, this instance of ServletExpress
	operates either as a potential server or a standalone session server
	(that is, the original session support).
session.cluster.host - for protocol switch rewriting in a clustered, session sharing
	environment, this is the hostname used to query your cluster. This host name
	will be used to determine whether protocol switching is occurring. 
	You can leave the value blank, comment out the property with a #,
	or delete the property from the file.

  >>> Servlet chaining and filtering is non-functional.

  >>> Domino Go Webserver on AIX
  If the ServletExpress Manager is running when you try to run a servlet,
  the Domino Go Webserver will core dump. To avoid this problem, perform
  one of the following procedures:
  - Do not run the ServletExpress Manager and servlets at the same time.
    After you finish using the ServletExpress Manager, 
    be sure to log off before you run any servlets.
  - If you are not using any of the Session Management features, disable
    the sessionManager servlet. In the ServletExpress Manager, set
    "Load on Startup"for the sessionManager servlet to No.
    Restart your Domino Go Webserver.  You can now run servlets at the same
    time as the ServletExpress Manager.

  >>> Apache on AIX and Sun
  ServletExpress does not shutdown when Apache server is shutdown. In such
  a case, you run ServletExpress Manager and not realize that the
  Apache server is not available. If this happens, perform one of the following
  procedures:
  - Restart the system.
  - Determine the pid of the ServletExpress Java Virtual Machine (JVM) by using
    the command ps -eaf. Stop the JVM and then change the ncf.native.outofproc.port
    in the ServletExpress configuration file (jvm.properties).


>>> INSTALLATION PROBLEMS
  >>> Installation for IIS 4.0 for this ServletExpress Beta 2.0 release 
      requires the following steps:
        1.  Open the Services Applet in the Control Panel.
        2.  Stop the World Wide Web Publishing Service
        3.  Install ServletExpress 
        4.  Restart the World Wide Web Publishing Service.
      
  
Upgrade to ServletExpress Beta 2.1 by downloading the new version from the
download website --
         http://www.ibm.com/java/servexp