                 SoftSolutions(R) 4.1 NLM Update

                     DOCUMENTATION REVISIONS
                               for
SoftSolutions Document & Security Server for NetWare(R) Reference

        (C) 1995 Novell, Inc.  All Rights Reserved.  5/95
_________________________________________________________________

This file was created as an ASCII text file.  Any portion of this
file may be reproduced for use by licensed users of SoftSolutions
4.1f or DOS or Windows.
_________________________________________________________________

This document provides revisions to the SoftSolutions 4.0
Document & Security Server (DSS) for NetWare Reference, dated
3-30-94, for updating to the SoftSolutions 4.1 NLM.

>> About Security in SoftSolutions  p. 2

Replace all of the paragraphs under this section with the
following:

     SoftSolutions document security offers simple setup, speed
     of enforcement, robust security, and convenient maintenance.

     System administrators assign security rights for individual
     users and defined groups to a single document, and each
     document can feature different security levels for different
     users and groups.

     This strong internal security is sufficient if users cannot
     access the document file outside of SoftSolutions.  However,
     users may have access to SoftSolutions documents, either at
     the operating system command line or through file management
     utilities.

     Allowing a user to directly access documents from the server
     weakens the security infrastructure and creates
     inefficiencies.  To enforce any document security designated
     by a user in SoftSolutions, network operating system access
     rights can be set to match the specified SoftSolutions
     access rights.

     SoftSolutions' DSS overcomes the complexities of security
     enforcement by minimizing unauthorized file access and
     network management of document access rights.  DSS provides
     a simple method for enforcing SoftSolutions' security
     outside of its normal domain.  This protects documents
     managed by SoftSolutions against unauthorized access at the
     network AND operating system levels.

     The DSS security architecture offers safeguards at the
     Profile, file and network levels.  With SoftSolutions'
     implementation of the client-server architecture, the client
     makes requests to DSS, then in turn retrieves the document
     if it receives security clearance.

>> How the Document & Security Server Works  p. 3

Change the heading "How the Document & Security Server Works" to
"How DSS Works."  Also, it is appropriate to replace most
instances of the product's full name (Document & Security Server)
with the "DSS" acronym.

>> How DSS Works  p. 4

Replace the last two paragraphs of the section with:

     When a document is accessed in SoftSolutions, the
     appropriate OAM determines whether the document is located
     on a NetWare server.  If it is, the OAM sends a request to
     DSS for access to the document.  If the document is to be
     moved or copied to another server or to a local drive, DSS
     grants the user access to the document, which is then moved
     by the client software.  Otherwise, DSS either grants the
     user rights to the document file if it is a managed file or
     is in a managed directory, OR moves or copies it onto the
     same server.

     DSS also performs all deletions and returns status
     information requested by the OAMs.  DSS revokes users'
     access rights to documents when they are finished.

>> Installation  p. 5

Add the following immediately after the "Requirements" section.

     INSTALLATION _______________________________________________

     Before installing the Document & Security Server for the
     first time:

        * Install SoftSolutions 4.0a for Windows or DOS on the
          server using the SoftSolutions INSTALL program.  (See
          the SoftSolutions Installation Guide for information on
          installing the SoftSolutions programs and data.)

        * Ensure that 150kb of file server memory is available
          for the Document & Security Server.

        * Ensure that you have the correct version of the
          Document & Security Server.  Versions 4.0 and 4.0a of
          the DSS.NLM and the client software are incompatible
          with each other (e.g., SoftSolutions 4.0 will not work
          with a 4.0a DSS.NLM, nor will SoftSolutions 4.0a work
          with a 4.0 DSS.NLM).

        * CLIB.NLM dated March 1993 or later (e.g., CLIB 3.11d,
          CLIB 3.12f) is required.

     To install:

       1. Copy all the files from the SoftSolutions 4.1 Document
          & Security Server diskette to the server containing the
          documents that will be managed by SoftSolutions.

             * These files may be placed in the SoftSolutions
               programs directory, the NetWare SYSTEM directory,
               or any other directory the system administrator
               chooses.

       2. Create the configuration file as outlined below.

>> Date and Time Stamps  p. 10

Insert the following section before the "Loading the Document &
Security Server" section.

     DATE and TIME STAMPS _______________________________________

     DSS compares the date and time stamps of files it copies. 
     Therefore, for this comparison to produce correct results,
     the client (workstation) and server (where DSS is installed)
     must have the time zone information set up properly.  All
     time zone settings are in relation to GMT (Greenwich Mean
     Time), or UTC (Universal Coordinated Time).

     SETTING the SERVER TIME ZONE

     On the NetWare server that will run DSS.NLM, the time zone
     is set at the file server's console:

          SET TIME ZONE = [Time Zone
               Abbreviation][{+/-}d]{Daylight Savings Time Zone
               Abbreviation}

     where [Time Zone Abbreviation] is an abbreviation for the
     standard time zone, [{+/-}d] is the number of time zones
     sooner or later (-/+) than UTC (in hours---one or two
     digits), and {Daylight Savings Time Zone Abbreviation} is an
     optional abbreviation for Daylight Savings time.  For
     example:

          SET TIME ZONE = CST6CDT

     NOTE
          NetWare 4.x users:   For time zones that are offset a
          fraction of an hour (such as 30 minutes) past a full
          time zone hour, the minutes can be added after the
          hour's number by separating the hours and minutes with
          a colon (:).  For example:

               SET TIME ZONE = NST3:30NDT

     For the server, these abbreviations can be several
     characters in length, although three is usually sufficient
     to indicate a time zone (e.g., "MST" for "Mountain Standard
     Time").  The abbreviations are NOT STANDARDIZED---they can
     be made up (note the abbreviations in the following
     examples).

     Note in the following examples that the + is optional, but
     the "-" must be included.  Also note that the numbers are
     always in reference to UTC, even if not so noted by the
     abbreviations used.

     EXAMPLE                       SETS TIME ZONE FOR ...
     ____________________________________________________________

     SET TIME ZONE = EST5          East coast's Eastern Standard
                                   Time ("EST" = Eastern Standard
                                   Time)

     SET TIME ZONE = PST+8         West coast's Pacific Standard
                                   Time

     SET TIME ZONE = PST8          West coast's Pacific Standard
                                   Time

     SET TIME ZONE = PST+8PDT      West coast's Pacific
                                   Daylight-savings Time ("PDT" =
                                   Pacific Daylight-savings Time)

     SET TIME ZONE = TST-9         Tokyo, Japan's Standard Time

     SET TIME ZONE = AST-10        Sydney, Australia's Standard
                                   Time

     SET TIME ZONE = MEZ-1         Germany's Standard Time
                                   (Continental Europe)

     SET TIME ZONE = GMT0GDT       London's Daylight-savings Time
                                   ("GDT" = Greenwich Daylight-
                                   savings Time)

     When the SET TIME ZONE command is given, NetWare reads the
     time zone abbreviation (alphabetical characters only), reads
     one or two numbers (including any + or - sign), and then
     reads the optional Daylight Savings Time code, if there.  If
     ANY alphabetical characters follow the one or two digit Time
     Zone number, NetWare considers that Daylight Savings Time
     may be in effect at some time during the year.

     SETTING the CLIENT TIME ZONE

     For EACH client (workstation) under DSS's influence, the
     time zone is set as a DOS environment variable:

          SET TZ = [Time Zone Abbreviation][{+/-}d]{Daylight
               Savings Time Zone Abbreviation}

     The difference in the syntax (from the server's) is that
     "TIME ZONE" is abbreviated as "TZ."   For the Client, the
     [Time Zone Abbreviation] and {Daylight Savings Time Zone
     Abbreviation} abbreviations must be exactly three characters
     each.

     DOS reads the alphabetical characters, then reads the next
     one to two numbers, including any + or - sign.  DOS then
     reads the optional {Daylight Savings Time Zone
     Abbreviation}, which can be used to indicate to the user
     that Daylight Savings Time is in effect.  The 3-character
     abbreviations are NOT STANDARDIZED---they can be made up
     (note the abbreviations in the above examples).

>> SoftSolutions Setup  p. 11

Replace the CAUTION with the following:

     RECOMMENDATION
          Novell, Inc. recommends that the SoftSolutions option
          of visiting the Location Segment field during Profile
          creation be disabled and that you take advantage of
          SoftSolutions' Dynamic Document Maintenance, which you
          as a system administrator can set up to automatically
          use only secured paths, thus preventing users from
          accessing unsecured paths.

>> SoftSolutions Setup  p. 12

Delete the last sentence of item "2)" and insert the following
heading and sentence before the "/E=" switch information:

     /E= and /T= Switches

     One of the following two switches may also be used on an OAM
     command line:

>> SoftSolutions Setup  p. 13

Replace the two notes and bullet on this page with:

     MULTIPLE DATASETS or SERVERS and the ECHO and TEMPORARY
     LOCATIONS

     For multiple file servers, DSS must be running on EACH file
     server that contains SoftSolutions documents or that has a
     SoftSolutions Temporary or Echo Location.  The Temporary or
     Echo Location directories do not need secured paths.  In
     other words, whichever file servers contain Echo and
     Temporary Location directories, they must also have DSS
     loaded.

     In multiple datasets, "launch" and "preview" functions can
     use the same Echo or Temporary Location directories.  But,
     these directories cannot be mixed for a particular function
     type.  For example:

        * If one "launch" uses the /T= switch, ALL launch
          functions must use the /T= switch.

        * If one "preview" uses the /E= switch, ALL preview
          functions must use the /E= switch.

        * If one "launch" uses the /T= switch, ALL launch
          functions must use the /T= switch.

        * If one "preview" uses the /E= switch, ALL preview
          functions must use the /E= switch.

        * Launches can use the /T= switch while previews use the
          /E= switch.

        * Launches can use the /E= switch while previews use the
          /T= switch.

        * If launches are using the /T= switch, preview functions
          can also be using the /T= switch.

        * If launches are using the /E= switch, preview functions
          can also be using the /E= switch.

     In multiple dataset environments, duplicate Document Numbers
     should not be permitted to exist.  To ensure this, the
     beginning Document Number for each dataset should be
     different.  For example, Dataset NY might begin with
     Document Number 1,000 and Dataset LA with 100,000.  The
     range between beginning Document Numbers should be
     sufficient for each dataset's potential growth.

     DRIVE LETTERS for the ECHO and TEMPORARY LOCATIONS

     The echo and temporary locations must use a DRIVE LETTER and
     path---the VOLUME and path syntax cannot be used.  Drive
     letters and paths may be substituted with the %EC and %TMP
     variables, respectively.  These variables represent the echo
     and temporary locations found in the SoftSolutions
     WORKSTATION screen.

     For example, a typical command line would be changed from
     the following:

          SSOAM.INT %H %J %P

     to:

          SSOAM.INT %H %J %P%F /DSS {[Options]}

     NOTE
          The command line of OAMEND must contain ALL of the DSS
          parameters found on the command lines of OAMLAUNC and
          OAMPREVI.
