	README.TXT for RDM for Windows v2.5 FCS		1/10/94
	=======================================

This document contains hints and release notes for version
2.5 FCS of Interleaf RDM for Windows.

=====================< CONTENTS >========================

This file has the following sections:

Part 1: RDM Requirements

Part 2: Setup and Configuration Notes

Part 3: RDM Initialization File Setup

Part 4: Setting up the RDM Password file

Part 5: RDM File "Bill of Materials"

Part 6: RDM Operation Description 

Part 7: Last Minute Corrections and "Bugs"

==============< Part 1: RDM Requirements >================

RDM for Windows requires a MINIMUM of 4MB of memory
running under Windows 3.1 with DOS 5.0/6.0.  RDM is only
supported in Enhanced mode.

This version of RDM requires communications with a UNIX
"RDM Server" which performs the actual ORACLE database
operations.  To accomplish this, RDM requires a version of
a TCP/IP communications kernel supported by the RDM
architecture.  Please refer to the RDM DOS/Windows 
Configuration Specifications for more information on qualified 
networking software.

Before starting an RDM installation on the PC, make sure
RDM v2.5 has been installed and tested on a supported UNIX
platform.  This will greatly simplify any troubleshooting 
procedures.

=======< Part 2: Setup and Configuration Notes >==========

You must modify rdm.ini for your site before running RDM.
The following entry must be in your services file:

    exec	512/tcp

The PC hosts file must contain an entry for the UNIX machine that 
will be running the CI.

The UNIX RDM server /etc/hosts file must contain an entry for the
client PC.

Before starting an RDM client on the PC, make sure that it is known to the
UNIX node acting as its RDM Server (i.e., PC is listed in the hosts file
of the server).  Otherwise, you may encounter the following error
message when starting RDM:

"End of file on read"

=======< Part 4: Setting up the RDM Password file >=======

RDM2.5\BIN\RDMTEMP.FTP	
----------------------
Template unencrypted RDMPSWD.FTP file

This file should contain exactly 4 uncommented lines (comment lines
have a ';' in column 1 of a line). The lines represent the
following:

Line 1:	RDM Vault Owner Username (OS user)
Line 2:	RDM Vault Owner Password
Line 3:	OS Username you will be running the Remote CI under (OS user)
Line 4:	OS Password for the Remote CI user

OS user:
========
	In the above explanation, 'OS user' is a valid account on the
	operating system(s) you will be connected to; i.e. UNIX or
	VMS. Since Vaults can reside on multiple machines running
	different operating systems, the Username and Password must
	be the same for the Vault user on every system.

Note:	
=====
	If there is no password for a user, the Password line should
	have the value 'NONE' (the four letters in uppercase). Blank
	lines are not permitted.

	Most implementations of the FTP protocol used by RDM for 
	transferring files require a password.  Therefore, a password
	must be supplied for the Vault Owner.  A password will also be
	required for the OS Username if RDM Reports are to be run.

Example:
========
	Change the following 4 lines to represent your configuration.
	The Vault Owner was specified during your UNIX RDM
	installation as the owner of the RDM hierarchy.
rdm
rdmpswd
demo
demopswd


To Finish:
==========
	Once finished editing these entries, use the RDMCRYPT utility
	supplied to encrypt this file as follows:

	C:\RDM2.5\BIN> rdmcrypt rdmtemp.ftp rdmpswd.ftp
	C:\RDM2.5\BIN> del rdmtemp.ftp (for security)

=======< Part 5: RDM File "Bill of Materials" >===========

\rdm2.5\windows:
rdm.ini*	The windows ini file for rdmjam.
		You have to set RDM site specific 
		variables in this file. See the comments. This file must be 
		copied to the windows directory.

\rdm2.5\bin:
rdmjam.exe*	The RDM executable.
rdmcrypt.exe	This executable encrypts and decrypt the RDM password file.
freelib.exe	Utility to free "stuck" DLLs that occasionally occur
		after exiting RDM.
distinct.exe	Files to support Winsock 1.1-based file transfer
ghost.exe
ftp.dll
oslib.dll
rpc.dll
tbxdll.dll
tnet.dll
rdmftp{d,f,n,w}.dll Files to support RDM file transfer methods.
rdmapi.dll	RDM high-level support DLL.
listhscr.dll	List handling
rdmmrg.dll	Notes merging.
rdmnet.dll	RDM client-server network connection
vltmthds.dll	RDM vault method handling
vbrun100.dll	WorldView Review support
wvreview.exe

\rdm2.5\data\msg:
french		The message files for foreign language support.
german

\rdm2.5\help:
*.*		Support files for the RDM help WorldView collection.

\rdm2.5\help\rdmhelp:
*.pl		Various WorldView files for the RDM online docs.

\rdm2.5\ui:
data.dic*	The RDM/JAM data dictionary.
egavid.bin*	The RDM/JAM video file.
jpllib.lib*	The RDM Jpl function library.
menulib.lib*	The RDM menu library.
msgfile.bin*	The JAM error messages file.
english*	The RDM english error messages file.
scrlib.lib*	The RDM screen library.
smvars.bin*	The RDM/JAM system variable file.
winkeys.bin*	The RDM/JAM key file.
xsmsetup.bin*	The RDM/JAM key/function mapping and variable file.

==============< Part 6: RDM Operation Description >==================

This is a short description on how the RDM Jam User Interface works.

The RDM Jam Interface is implemented using a client server model.
The UI running on the PC is the client and rdmci5 running on the UNIX 
machine is the server. The programs communicate with sockets using TCP/IP. 

The CI is started on the UNIX machine using the name and password of the 
login user specified in the second entry of the password file.

When the UI starts you are presented with the login screen. After RDM user name
and password are entered, the UI starts the CI on the UNIX machine 
using the value of the RDM_COMMAND variable in the rdm.ini file. 
If the CI is started the returned version message is checked for compatible 
version numbers.

File transfer during checkin and checkout is accomplished using ftp. The
startup shells of the users in the RDM password file must be standard shells.
The first entry in the RDM password file is the UNIX user that has permission
to modify RDM vaults. This user is used for transferring files during checkin
and checkout.

File transfers also occur when writing reports. The report is written on the
UNIX machine using the users work area path as specified in the database. This
must be a UNIX path. The file is then transferred to the directory on the PC 
as specified by the user on the report screen. This must be a PC path. The file
on the UNIX machine is then deleted.

========< Part 7: Last Minute Corrections and "Bugs" >===========

