        LOTUS INTERNOTES WEB PUBLISHER RELEASE 4.0
        ==========================================

INTRODUCTION

InterNotes Web Publisher Release 4.0 is designed to work
with Notes Release 4 servers.

This README file contains information you may need to get
up and running with Lotus InterNotes Web Publisher, as well
as information that will help you troubleshoot potential
problems.  It includes the following sections:

I.  GETTING STARTED WITH INTERNOTES WEB PUBLISHER:

    This section provides an overview of starting
    InterNotes Web Publisher and publishing the
    sample database.

II. THINGS YOU SHOULD KNOW:

    This section contains information on InterNotes Web
    Publisher known issues and is divided into the
    following sections:

    ABOUT PUBLISHING
    ABOUT INTERACTIVITY
    ABOUT PLATFORMS
    ABOUT SECURITY


I.  GETTING STARTED WITH INTERNOTES WEB PUBLISHER
-------------------------------------------------

The following checklist provides an overview of starting
InterNotes Web Publisher and publishing the sample
database.

1.  Make sure the HTTP server is running.

2.  Make sure the Notes server is running, and that the
    Notes server and Notes client machines are able to
    access Notes databases.

3.  Install the InterNotes Web Publisher software.

4.  (OS/2 users only) Copy INOTES.EXE to the cgi-bin
    directory.

5.  Add the InterNotes Web Publisher databases to the Notes
    workspace of the machine from which you plan to
    administer InterNotes Web Publisher.

6.  Edit the WebMaster Options document in the
    Configuration database to set the "Publishing enabled"
    field to Enabled. If necessary, specify the output
    directory for HTML files, the appropriate file
    extension for your HTTP server, and the path to the CGI
    program files.

7.  If you want, view the Database Publishing Record for
    the sample database. (MERCURY.NSF)

8.  Start InterNotes Web Publisher and the interactivity
    module at the Notes server console. (Type load webpub
    to start the web publisher, and type load inotes to
    start the interactivity module.)

9.  Use a Web browser to view the published sample database.

10. If you want to see how the InterNotes Web Publisher
    automatically updates, edit a document in the sample
    database (Mercury Sports), and view the results of your
    edits using a Web browser.


WARNING: 
-------
    WEB PUBLISHER IS CONFIGURED TO AUTOMATICALLY
    PUBLISH THE SAMPLE DATABASE

    InterNotes Web Publisher includes a sample database,
    Mercury Sports (MERCURY.NSF). Once you enable
    publication, InterNotes Web Publisher is configured
    to automatically begin publishing this database.

    If you have an existing Web site with an existing
    home page, make sure that the output directory you
    specify in the WebMaster Options document is different
    than the directory that contains your current home page.
    Otherwise, InterNotes Web Publisher may overwrite your
    current home page with the Mercury Sports home page
    when you publish the sample database.

    DISABLING THE PUBLICATION OF THE MERCURY SPORTS DATABASE

    The Web Publisher Configuration database includes
    preconfigured Database Publishing Records for the
    sample databases included with InterNotes Web Publisher.
    Only the Mercury Sports sample database, however, is
    enabled for publication.

    If you don't want to publish Mercury Sports, follow these
    steps:

    1.  Open the Web Publisher Configuration database.

    2.  Choose View - Database Publication - by Database Name.

    3.  Double-click the record for MERCURY.NSF.
        The Database Publishing Record appears.

    4.  Press CTRL+E to put the document in Edit mode.

    5.  Select Disable in the "Publishing status" field.

    6.  Save and close the document


THINGS YOU SHOULD KNOW ABOUT PUBLISHING
---------------------------------------

1.  UPGRADERS MUST REFRESH THE DESIGN OF THE CONFIGURATION
    DATABASE

    If you are upgrading from InterNotes Web Publisher 1.0
    or 2.0, you must refresh the design and fields in your
    InterNotes Web Publisher Configuration database.

    The InterNotes Web Publisher Configuration database
    template has new design elements. For example, the
    WebMaster Options and Database Publishing Record forms
    have been modified.  To use the new template, you must
    refresh the database's design to update the design
    elements before you start InterNotes Web Publisher.

    Note    If you do not refresh the Configuration
    database's design, when you start InterNotes Web
    Publisher, it will shutdown and display an error at the
    Notes server console.

    Updating the Web Publisher Configuration database

    To refresh the design of the InterNotes Web Publisher
    Configuration database, follow these steps:

    1. (Optional) Make a backup copy of the current
       InterNotes Web Publisher Configuration
       database (WEBCFG.NSF).
    2. Make sure InterNotes Web Publisher is installed.
    3. Highlight the InterNotes Web Publisher Configuration
       database.
    4. Choose Design - Refresh Design.  The Refresh
       Database Design dialog box appears.
    5. In the Template Servers text box, select the Notes
       server where InterNotes Web Publisher resides.
    6. Click OK.  A message appears asking if you wish to
       proceed.
    7. Click Yes.
       The Web Publisher Configuration database contains
       the WebMaster Options document, as well as Database
       Publishing Records for any databases you've
       published.  To use the new template, you must also
       refresh the fields in the database's existing
       documents.
    8. To refresh the fields, choose Tools -
       Refresh Fields -  All Documents.


2.  INTERNOTES WEB PUBLISHER SOMETIMES REMOVES ALL
    PUBLISHED OUTPUT BEFORE PUBLISHING A DATABASE

    If any of the following conditions are true, InterNotes
    Web Publisher will delete all published files in the
    html output directory before it publishes the database.

    * A form has been edited
    * InterNotes Web Publisher detects that the database is
      a new replica
    * A new version of InterNotes Web Publisher is
      publishing a database for the first time

    This was not the case in InterNotes Web Publisher
    Release 1.0 or 2.0.  The change was made to ensure that
    the html output is in sync with the Notes database.


3.  DO NOT PLACE FILES IN THE HTML OUTPUT PATH BECAUSE
    INTERNOTES WEB PUBLISHER MAY DELETE THEM

    If you have created subdirectories in your html output
    directory path and stored files in these
    subdirectories, InterNotes Web Publisher may delete
    these files before it republishes a database.
    For example:

    * You may have specified c:\htmldocs\ as the output
      html directory.
    * You then publish a database named Registrations, and
      InterNotes Web Publisher creates a directory named
      c:\htmldocs\registrations.
    * You then create a subdirectory named summer and
      manually move files to the
      c:\htmldocs\registrations\summer\ directory.

    When you publish the Registrations database and any of
    the conditions described in item #2 above are true,
    InterNotes Web Publisher will delete the contents of
    every directory in the c:\htmldocs\registrations
    path, including the summer directory.

    Do not place files in the path of the html output
    directory.  You will lose data.


4.  RELEASE 4.0 PUBLISHES A DOCUMENT USING ITS DEFAULT FORM
    ONLY WHEN IT'S REFERENCED FROM A PUBLISHED VIEW WITH
    NO FORM FORMULA

    InterNotes Web Publisher Release 1.0 and 2.0 published
    every document once using its default form, and once
    for every form specified in a form formula.  Having
    duplicate html versions of these documents could
    potentially take up lots of disk space.  Also, for
    users with third party Web indexers, a search would
    return two versions of the same document.

    InterNotes Web Publisher 4.0 publishes a document using
    its default form only if it is referenced from a
    published view with no form formula.  This gives you
    more control over what gets published in the html
    output directory.

    This change may cause a problem in certain
    circumstances.  For example, there are rare cases in
    which InterNotes Web Publisher is unable to resolve a
    complex form formula when creating a doclink.  In this
    case, InterNotes Web Publisher will create the link to
    the document using its default form.  Since this
    document is no longer published, the link InterNotes
    Web Publisher creates may be invalid.

    The workaround is to include a view that has no form
    formula in the Views to Publish field in the Database
    Publishing Record.  InterNotes Web Publisher will then
    publish the document using its default form, and the
    doclink will work correctly.


5.  A DATABASE WITH NO DOCUMENTS WILL NOT BE PUBLISHED

    A database must contain at least one document in order
    for it to be published.  For example, you may want to
    create a discussion on your Web site.  To do this, you
    complete the following tasks:

    * Design the database
    * Create the main topic and response topic forms
    * Create a Database Publishing Record for the database

    InterNotes Web Publisher will not publish the database;
    you must create a document in order for the database to
    be published.  Make sure any database you want to
    publish contains at least one document.


6.  INTERNOTES WEB PUBLISHER SHUTS DOWN IF IT CANNOT OPEN
    THE CONFIGURATION DATABASE

    If InterNotes Web Publisher cannot open the
    Configuration database, WEBCFG.NSF, it will retry
    frequently for up to five minutes.  After five minutes,
    the server add-in terminates.  When you resolve the
    problem, restart InterNotes Web Publisher at the Notes
    server console.

    To restart InterNotes Web Publisher, enter the
    following command at the Notes server console:

        load webpub


7.  PUBLISHING OPTIONS

    When a database is scheduled for frequent publishing
    (for example, less than every 30 seconds), disable
    publishing before you edit the Database Publishing
    Record.  Otherwise, you may have a conflict with the
    server when you attempt to save the Database Publishing
    Record.  If the Notes server attempts to read the
    Database Publishing Record while you are saving it,
    the following error appears:

    "Another copy of this document was saved while you were
    editing it.  Save your changes also as a Save Conflict
    document? Yes No."

    Select No to prevent a save conflict, then disable
    publishing.  To disable publishing, use the Tools-Run
    Macros-Disable Publishing macro.  You can enable
    publishing after you modify the Database Publishing
    Record.


8.  YOU CANNOT PUBLISH TWO DATABASES WITH THE SAME FILE NAME

    InterNotes Web Publisher cannot publish two distinct
    databases with the same file name (for example, DB.NSF)
    even if the databases reside in different directories
    or on different servers.  Before InterNotes Web
    Publisher publishes a database, it checks to see if it
    has previously published a database with the same .NSF
    file name.  If it has, InterNotes Web Publisher does
    not publish the database; instead it posts the
    following error in the Log:

    "ERROR: Database 'filename' being published does not
    match already published database.  Different Replica
    IDs."


9.  MODIFYING THE MERCURY SPORTS SAMPLE DATABASE,
    MERCURY.NSF:

    The Mercury Sports sample database is pre-configured to
    be the home page database.  If you want to create a
    copy of the database which is not the home page
    database, or has a different filename, you must edit
    the URL's on the Help About page:

    1. Select the Mercury Sports sample database.
    2. Choose Design - Help Document - About Database.
    3. Double click on the "New Product Information" popup.
    4. Edit the URL to change or remove "mercury/".
    5. Click OK.
    6. Repeat for the remaining popups on the About page.


10.  LIMITATIONS IN NOTES FORMULAS

    Certain @functions are dependent on Notes user
    interface functionality, so InterNotes Web Publisher
    cannot convert them to HTML.  When you publish a
    document that contains formulas with any of the
    following @functions, the formulas have no effect.

    The @functions are:

    @Command
    @DbLookup
    @DbColumn
    @DDEInitiate
    @DDETerminate
    @DDEExecute
    @DDEPoke
    @MailSend

    InterNotes Web Publisher does not support the use of
    Notes formulas within pop-ups.


THINGS YOU SHOULD KNOW ABOUT INTERACTIVITY
------------------------------------------

1.  INOTES SERVER ADDIN READS CONFIGURATION DATABASE ONLY
    AT STARTUP

    INOTES, the Notes server addin that enables you to
    publish forms and search Notes databases from the Web,
    reads the Web Publisher  Configuration database only
    at startup.  The WebMaster Options document in the
    Configuration database is where you specify global
    publishing parameters, such as the output HTML
    directory, and the HTML file extension.  If you change
    any of the publishing options in the WebMaster Options
    document, you must stop INotes and restart it in order
    for the changes to take effect.

    To stop INotes, enter the following command at the
    Notes server console:

        tell inotes quit

    To restart INotes, enter the following command at the
    Notes server console:

        load inotes


2.  YOU CANNOT USE AN INPUT FORM AS THE HOME PAGE OF A
    DATABASE

    InterNotes Web Publisher does not support using an
    input form as the home page of a database.


3.  $$WEB SYNONYM SHOULD NOT BE LAST SYNONYM IN FORM

    When you create a form to publish on the Web, you must
    give it the synonym $$Web, so that InterNotes Web
    Publisher knows to publish the form.  If you have a
    database from which you are publishing a number of
    forms on the Web, check the form attributes to make
    sure that the $$Web synonym is not the last synonym
    listed.  For example, if you have a form named memo,
    the form name in Notes should read memo|$$web|memo.

    InterNotes Web Publisher uses the last synonym to refer
    to the form internally, just as Notes does.  If the
    last synonym is $$Web, InterNotes Web Publisher uses
    the second to the last synonym to refer to the form.
    To ensure that Notes and InterNotes Web Publisher store
    the same form name in documents, make sure the $$Web
    synonym is not the last synonym.


4.  PATHS TO THE IMAGE FILES IN RESPONSE FORMS MUST BE
    ABSOLUTE

    When InterNotes Web Publisher publishes a database, it
    creates a subdirectory for the database files within
    the output HTML directory.  It creates a separate file
    for each document and view in the database, as well as
    for the database home page.  It also converts any
    bitmaps in Notes documents to GIF files and stores the
    GIF files in the database subdirectory.  References to
    bitmaps are local (e.g. [<img src=graphic1.gif>]).

    When Web users submit response forms, the INotes CGI
    script creates responses "on demand."  If the response
    form includes bitmaps, INotes looks for the bitmaps in
    the current directory, which is the cgi program
    directory (e.g., /cgi-bin).  Since the bitmap is not in
    this directory, the published form will contain a broken
    link.  The workaround is to hand code absolute
    references to the gif files using the pass-through HTML
    feature (e.g. [<img src=/gifs/graphic1.gif>]) instead
    of pasting bitmaps into the response form.  For more
    information, see "Adding HTML code" in Chapter 5 of the
    InterNotes Web Publisher Guide.


5.  IF YOU INCLUDE CERTAIN CHARACTERS IN A FORM NAME IT
    WILL NOT BE PUBLISHED

    When you create a form to publish on the Web and
    include any of the following characters in the form
    name, InterNotes Web Publisher will not publish the
    form:

    \ (backslash)
    * (asterisk)
    : (colon)
    " (quote)
    < (less than)
    > (greater than)
    ? (question mark)
    / (forward slash)
    # (number sign)

    For example, InterNotes Web Publisher will not publish
    a form with a cascading name (such as
    Person\Accounting|$$Web).  However, InterNotes Web
    Publisher will publish any documents created in Notes
    that use this form.

    Also, do not include the | (vertical bar) in the name
    of any form you want to publish.   Notes uses the
    | (vertical bar) to separate multiple form names.


6.  PRESSING STOP DURING A SEARCH WILL NOT TERMINATE THE
    SEARCH

    If you press stop when in a search, the search does not
    terminate.  It is not possible to interrupt a CGI
    script.


7.  FULL TEXT SEARCHING LIMITATION WITH MULTIPLE
    CONFIGURATION DATABASES

    If you are working with multiple Web Publisher
    Configuration databases and perform a search, the
    search may return no documents.  This occurs because
    Inotes has no way of knowing which Web Publisher
    Configuration database you used to publish the
    database, so it looks only at the contents of the first
    WEBCFG.  If a Database Publishing Record for the
    database exists in the first WEBCFG, the search will
    work.  If not, the search will not return any
    documents.  If you want to provide search capabilities
    and have multiple WEBCFGs, you must create Database
    Publishing Records for each database you want to search
    in the first WEBCFG.


8.  NO ERROR DISPLAYED IF YOU ATTEMPT TO PUBLISH A SEARCH
    BAR FOR A DATABASE THAT DOES NOT HAVE A FULL TEXT INDEX

    If you add the $$ViewSearchBar field to a home page or
    view to search a database from the Web, InterNotes Web
    Publisher will publish the form, but the search bar
    will not be published if the database does not have
    a full text index.  No error message is generated.


9.  ENTERING AN INVALID SEARCH STRING RETURNS NO RESULTS

    Entering an invalid search string returns no results.
    InterNotes Web Publisher does not display a message
    stating that you entered an invalid string.  This may
    be confusing, since it is inconsistent with the way
    that Notes behaves.


10. NO MATCHING DOCUMENTS RETURNED IF THE LCT FILE IS
    MISSING

    If you delete a database's LCT file and then attempt to
    perform a search, the search will appear to work, but
    no matching documents will be returned.  InterNotes Web
    Publisher looks to the LCT file for the last
    publication date and time before it performs the
    search.  This is to ensure that search returns only
    documents that have been published. If InterNotes Web
    Publisher cannot find an LCT file, it will not execute
    the search.


THINGS YOU SHOULD KNOW ABOUT PLATFORMS
--------------------------------------

1.  (UNIX ONLY) FILE NAME CHANGES FOR SOLARIS AND AIX

    Users of InterNotes Web Publisher Beta 3 for Solaris
    and AIX, please note the following file name changes:

    The Inotes interactivity module file has been renamed:

    Old file name: inotes_s
    New file name: inotes

    Please delete the old inotes_s file from your Notes
    executable directory.  Also, please edit the NOTES.INI
    file, and remove any references to the old file name.

    The CGI program file has been renamed:

    Old file name: inotes
    New file name: iwpcgi

    Please delete the old inotes file from the CGI program
    directory.


2.  (OS/2 and UNIX) COPY INOTES.EXE TO THE CGI DIRECTORY

    If you are using InterNotes Web Publisher for OS/2,
    after you run Install, you must copy the file
    INOTES.EXE to the directory where your CGI files are
    located.  This applies only to OS/2 users.  See the
    InterNotes Web Publisher Guide pages 2-5 through 2-8
    for more information on copying INOTES.EXE to the CGI
    directory.


3.  (OS/2 only) NOTES SERVER REQUIRES HIGH PERFORMANCE FILE
    SYSTEM (HPFS)

    The OS/2 server on which you install InterNotes Web
    Publisher must have HPFS.  HPFS is an installable file
    system that lets you create file names with as many as
    254 characters.  For information on installing HPFS,
    refer to your OS/2 documentation.


4.  (OS/2 only) NOTES SERVER MUST BE CONFIGURED FOR
    CODEPAGE 850

    You must configure the Notes OS/2 server on which you
    install InterNotes Web Publisher for codepage 850,
    which is the International character set.

    Your server may be configured for codepage 437, which
    is the USA character set.  InterNotes Web Publisher
    assumes that the OS/2 Notes server is configured for
    codepage 850 when it converts characters to the
    codepage 8859 (ANSI) used by HTML.  To configure OS/2
    for codepage 850, refer to your OS/2 documentation.


THINGS YOU SHOULD KNOW ABOUT SECURITY
-------------------------------------

1.  RESTRICT ACCESS TO THE CONFIGURATION DATABASE

    Because the Configuration database is the central
    control for InterNotes Web Publisher, you should
    restrict access to it. InterNotes Web Publisher runs as
    an add-in on a Notes server.  Therefore, users who are
    authorized to edit Database Publishing Records in the
    Configuration database will be able to submit a
    publishing request for any databases to which the Notes
    server has read-access.


2.  DO NOT ALLOW INTERNOTES WEB PUBLISHER TO ACCESS
    DATABASES THAT CONTAIN CONFIDENTIAL INFORMATION

    InterNotes Web Publisher can publish a database on any
    server to which it has access; a user simply has to
    submit a publishing request.  For security reasons, you
    may want to restrict the server on which you install
    InterNotes Web Publisher, so that it cannot access
    confidential databases.  For information on the
    different methods to restrict server access, see your
    Notes documentation.

    For example, if you install InterNotes Web Publisher on
    a server named Server1, and you do not want the Web
    Publisher to be able to access a database named
    Internal Memos on Server2, you would do the following:

    1. Select the Internal Memos database on Server2.
    2. Choose File - Database - Access Control.
    3. In the People, Servers, Groups edit box, enter the
       name of the server on which you installed InterNotes
       Web Publisher (Server1).
    4. In the Access Level List, select No Access.
    5. Select Add to add the server to the access control
       list.
    6. Click OK.

    Repeat the procedure above for each database that you
    do not want InterNotes Web Publisher to access.


