Setting Properties to Control fPserver:

The server is contained in the Server.jar file and is run using the fpserver.bat file provided. The server is controlled by it's configuration file prop.fpserver which it looks for in the lib directory under the directory the batch file is run from.

You can use the fPserver Administration Gui Interface to edit the prop.fpserver file and to create, edit and/or modify the config.default and config.username files. How to use the Configuration Editor

prop.fpserver configuration values:

The prop.fpserver file is used to specify various server operating parameters:

Configuration Variable	Default values	Description
port	4350	This specifies the port on which the server listens for connections.
producers	200	This value/2 is the maximum number of simultaneously connected clients.
consumers	10	The number of threads dedicated to delivering messages received by the producers threads. The absolute numbers and ratio between producer and consumer threads is situation specific. Each pair of producer threads is dedicated to listening for messages from a specific client and it's filePro program. If a customer only has a 16 user filePro license they would be wasting threads and memory by setting producers higher than 32. The producer threads place messages on an internal stack. If there are any messages on this stack the consumer threads are awakened to deliver the messages. Since only a percentage of the producer threads are sending messages at any given time a smaller number of consumer threads is required to deliver the messages in a timely fashion. The actual number of consumer threads required to keep the messages from lingering on the message stack depends on how many producer threads are active at one tije, and how busy those threads are.
logDirectory	/logs directory beneath the server starting directory	The directory where log files are to be placed. This included the .doc files saved from the admin gui.
users	/users directory beneath the server starting directory	The directory where the server expects to find user configuration files and config.default.
exec	fpdaemon_nt	The program to be exec'd by the server to run the filePro programs. A full path should be provided if this program is not in the system path.
admin	true	Should the Administrative gui be run when the server is started.
autosave	false	Should .doc files form the admin gui beautomatically saved when the server and client windows are closed.
shutdownOnExit	true	Should the server be shutdown automatically on exit from the gui administrative tool. If set to true, fpserver will shut down when you exit from the GUI tool even if you do now select Stop on the Server Menu
log	The name of the server log file.	Defaults to no logging.
debuglog	The name of the server debug log file.	Defaults to no debug logging. The debug logging is extensive. Every message is logged in detail, as well a number of other pieces of information generated by the receipt and delivery of every message. As a result, debug logging significantly slows the performance of the server and should only be used when absolutely required.

Examples of prop.fpserver:

Developer installed filePro and fPserver using the default installation on his C: drive on a Native 32 Windows PC:

port=4350
producers=200
consumers=10
debuglog=c:/fp/fpServer/logs/debug.log
log=c:/fp/fpServer/logs/fpServer.log
users=c:/fp/fpServer/lib
exec=c:/fp/fpdaemon_nt

Developer installed filePro and fPserver into his C:\50win directory on a Native 32 Windows PC:

port=4350
producers=200
consumers=10
debuglog=c:/50win/fp/fpServer/logs/debug.log
log=c:/50win/fp/fpServer/logs/fpServer.log
users=c:/50win/fp/fpServer/lib
exec=c:/50win/fp/fpdaemon_nt

Developer installed filePro and fPserver using the default installation on a SCO UNIX PC:

port=4350
producers=200
consumers=10
debuglog=/appl/fp/fpServer/logs/debug.log
log=/appl/fp/fpServer/logs/fpServer.log
users=/appl/fp/fpServer/users
exec=/appl/fp/fpdaemon_nt

fPClient User Log In

When a client connects to the server a message is sent back to the client requesting a login. fPclient prompts for the User Name. This name is used to find and read a config.username in the directory specified by the users configuration option in prop.server file.

The user password (if any) is read from this file. If a password is required for this user it is prompted for and compared to the stored value. If it matches, the exec program is run and is passed the startcmd specified in the config.username config file. This is a simplification, but from that point on the server basically does nothing more than relay messages between the client and filePro.

User configuration

The configuration for each user is detailed in the config.default and config.username files contained in the users [/lib] directory. These files take the form of succesive lines of key=value. Lines beginning with # are ignored as comments. The user config files serve two purposes (1) to control the server treatment of the client session; and (2) to set the environment which is passed to the exececuted filePro programs.

The config.default file provides a default configuration for each user and the config.username files can add to and/or override entries in the config.default file. A special file config.anon will, if present, set the server treatment of the client session and the filePro environment for logins by users who do not have config.username files in the users directory.

All entries in the config.default file are automatically added to the config.username entries unless they have been overriden by entries with the same key from the config.username file. For example, if an administrator wanted PFDATA=C: set for nearly all users then he would place that in the config.default file. If the administrator wanted user name joe to get his data from the D drive then he would override this setting by placing PFDATA=D: in config.joe

It is important to note that the environment which is passed to the filePro programs (and any programs they may execute) is wholly specified by the entries in the config file(s). If a setting is not in the config file it will NOT be part of the filePro environment. This includes PATH, TERM, COMSPEC, etc.

config.default and config.username User config settings used by fPserver
Configuration Variable	Value	Description
startcmd		The command passed the the 'exec' program (fpdaemon_nt) which is in turn exec'd by that program. For example "p dpromenu". If this command has embedded spaces it must, like the example, be enclosed in quotes.
password		The user password. Currently this is not encrypted. Encryption will be added to passwords and to message bodies once the server has passed alpha testing.
log	default is false	Acceptable settings are true and false. This controls if a client specific log file is created and used. the name of the log file is automatically generated based on the username, client id, and time of day.
debuglog	default is false	Acceptable settings are true and false. This controls if a client specific debug log file is created and used. the name of the log file is automatically generated based on the username, client id, and time of day.
displaymessages	default is false	Acceptable settings are true and false. This controls whether the messages sent between the client and filepro are displayed in the administrative gui window dedicated to that client. Turning this option on causes a significant slowdown in the server and should only be used if absolutely necessary.

Examples of config.default:

Developer installed filePro and fPserver using the default installation on his C: drive on a Native 32 Windows PC:
```
startcmd="p dpromenu"
PFDSK=C
PFPROG=C:/50WIN
PFDATA=C:
PFDROPSHADOW=OFF
PFDIR=/50WIN
pfign=abd
PFNEWNTCONSOLE=ON
PATH=%PFPROG%/fp;%path%
log=false
debuglog=false
displaymessages=false
```
Copyright 2000, fP Technologies, Inc. All Rights Reserved
These documents are covered under the terms and conditions of the fP Technologies, Inc. Program License Agreement
rev. 9/27/2000