Setting up the GIserver Configuration:
Please note: The admin=true property must be set in giserver/lib/giserver.cfg file in order for the GIserver administration tool to run.
The GIserver administration program can be used to add, delete and edit any server configuration giserver.cfg file and user configuration username.cfg files:
- first select Edit from the top menu:
Editing the GIserver properties file settings[giserver.cfg]:
- Select Edit Server Configuration:
- Once you have selected Edit and then Edit Server Configuration from the
top menu as above, the Configuration Editor window will appear and it will reflect the current settings of the giserver.cfg file that you can change:
- You can then change any setting by clicking on an On/Off Button setting:
- or change a Value as in the case of port number etc. In order for GIserver server properties changes to become effective GIserver must be re-started.
- You can save your changes by clicking on the Save button [See how GIserver displays tool tips when you mouse over a button:
- To exit the Configuration Editor either click on the X box in the upper right hand corner of the window or click on the Cancel button:
Setting the Administrative Password properties for GIserver:
- If you click on the Password button, you will be able to change the Administration password for GIserver
- The Set Administrative Password dialog box will appear:
- Enter the values you want and click on the OK button:
- Sets the administrative password. Defaults to blank if this is blank no remote administration is allowed.
Setting the User password control properties for GIserver:
- If you set the Initial Password Change to On:
- GIserver will require that the fileproGI client force the User to change their
password when they log in for the very first time.
- GIserver will require that a user change their password after a specified number of days. You enter the number of days you want to use in the Password expiration days input box. GIserver will set the expires= to that value in the giserver.cfg file. A value of 0 specifies no password expiration testing. The example shows a 60 day period:
Setting the Idleout property for GIserver:
- The Idleout property is used by GIserver to check for users that are unresponsive, for example someone who went home while still logged in to the server. If idleout is in effect for that user - when the idleout time has been exceeded without any client activity the user will be logged out. By default idleout is turned off. For it to be in effect for any user there must be an idleout value set (in minutes) in the server properties:
- and the doIdleOut property must be set to true in the default.cfg file for all users:
- or can be over-ridden as set in a username.cfg file for a particular user:
Setting the timeout and recall properties in the giserver\lib\giserver.cfg file
- The timeout and recall values in the giserver\lib\giserver.cfg file are used by GIserver to check for client software that is no longer responsive, either because the connection has been broken or because the software is locked up. The default values are in minutes and are timeout=3 and recall=1
- With the default settings (timeout = 3, recall=1) it would take only 5 minutes for the server to realize that the client was not responding and close the connection. Smaller values increase network traffic and place a heavier burden on the network and on the server. Larger values mean that dead clients hang around longer.
GIserver Logging Properties
If you set the Log Server Activity to ON and have debug=true in giserver.cfg GIserver will maintain detailed activity and debug logs. These logs are for the current session.
For more details click here
What properties in giserver\lib\giserver.cfg does the Server Configuration Dialog window set?
-
Dialog Window Control | giserver.cfg property set |
Administrative Window | admin=true/false |
Administrator Login | adminName=value |
Server Name | serverName=value |
Server Address | serverAddress=value |
Shutdown on Window Close | shutdownOnExit=true/false |
Log Server Activity | log=true/false |
Initial Password Change | forcePassword=true/false |
Server port | port=value |
Administrative port | adminport=value |
License port | licensePort=value |
Password expiration days | expires=value, 0 means no expiration |
Idle user timeout period | idleout=value, 0 means no idelout |
Define New Server
- Define New Server updates the servers file which is maintained in the ~/giadmin/lib directory as "servers":
- :
- :
Edit Server Definition
- Edit Server updates the servers file:
- :
- :
Delete Server Definition
- :
Examples of giserver.cfg files for various platforms
Adding/Deleting/Editing the user properties files [default.cfg and username.cfg]:
- The displayed entries in these config files consist of the specified environment values that GIserver uses to set the entire environment that it uses when it launches filePro. The default environment is specified in the default.cfg file. It is important that the entire environment that is required is set in the default.cfg file including environment variables that may be required when filePro launches external programs using the system command. When a user logs in to GIserver, GIserver uses the default environment and modifies it based on entries in the corresponding username.cfg file [lee.cfg, mary.cfg etc.]
- The configuration for each user is detailed in the default.cfg and
username.cfg files contained in the giservers/users 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 default.cfg file provides a default configuration for
each user and the username.cfg files can add to and/or override entries in
the default.cfg file. A special file anon.cfg will, if present, set the server treatment of the client session and the filePro environment for logins
by users who do not have username.cfg files in the users directory.
- All entries in the default.cfg file are automatically added to the
username.cfg entries unless they have been overriden by entries with the
same key from the username.cfg file. For example, if an administrator wanted
PFDATA=C: set for nearly all users then he would place that in the
default.cfg 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 joe.cfg
- 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. Please Note that two very important environment variables: SystemDrive and SystemRoot associated with Windows NT and Windows 2000 [W2k} must be included in the default.cfg otherwise GIserver will not work.
New User Configuration
- Select New User Configuration from the Edit top menu option:
- This will provide a blank window to enter the "user unique" variables. Enter any variables that you want to override in the default.cfg file. In the following screen we are overriding the starting menu name:
- The Please enter new user name Dialog box will appear:
- and then click the OK button.
Edit User Configuration
- Once you have selected the Edit User Configuration from the
top menu as above:
- a list of the username.cfg files will appear:
- Either double click on the config file you want to edit or highlight it and click the Okay button:
- The Configuration Editor will bring up a window that contains the selected config file. The editor will not display any password setting:
- If you decide you do not want to make the changes before you save them, you can select click on the Cancel button:
- You can save your changes by clicking on the Save button:
- If you would like you can also load a username.cfg file, make changes to it, and save it to a different using the the saveAs button:
- If you want to enable user logging or debug logging for a particular user [example is for lee], load the user config file:
- Then click on the Log and/or Debug log buttons, then click on the Save button:
- If you examine the lee.cfg file with the windows Notepad or Word Pad you will see that GIserver has set two values in the lee.cfg file...log and debugLog... to true:
- The GIserver administration tool also allows the system administrator to change the users password. Load the lee.cfg file and then click on the Password button:
- The Change User Password dialog box will appear. Enter the current password for the user along with the new password [entered twice for confirmation] and then click the OK button:
- If you now re-examine the lee.cfg file with the windows Notepad or Word Pad you will see that GIserver has changed two values in the lee.cfg file...lastChanged and password...:
- To exit the Configuration Editor either click on the Cancel button or on the X box in the upper right hand corner of the User Configuration window:
The startdir property
fpdaemon sets the current working directory to whatever 'startdir' is set to (if it is set) just before the 'startcmd' is run. This has the same effect as if you had switched to the drive and directory specified in 'startdir' just before running 'startcmd' .This was added because some applications require that they be run from a particular directory. If startdir is not set then the current working directory remains whatever it was when giserver was started - typically the fp/giserver directory.
Typical setting: startdir=c:\Roadshow\fp|
What properties in giserver\users\*.cfg does the User Configuration window set?
Examples of giserver.cfg:
-
Developer installed filePro and Giserver using the Roadshow installation on his C: drive on a Native 32 Windows PC:
password=àîä)EΧfˆ
recall=1
remoteShutdown=true
log=true
serverName=Ray1
idleout=0
timeout=3
port=4350
admin=true
adminName=ray
remoteShutDown=true
debug=true
forcePassword=false
serverAddress=192.168.0.5
exec=C:/Roadshow/fp/fPdaemon_win
licensePort=4550
shutdownOnExit=true
adminPort=4450
expires=0
-
Developer installed filePro and GIserver into his C:\50win directory on a Native 32 Windows PC:
password=àîä)EΧfˆ
recall=1
remoteShutdown=true
log=true
serverName=Ray1
idleout=0
timeout=3
port=4350
admin=true
adminName=ray
remoteShutDown=true
debug=true
forcePassword=false
serverAddress=192.168.0.5
exec=C:/50win/fp/fPdaemon_win
licensePort=4550
shutdownOnExit=true
adminPort=4450
expires=0
-
Developer installed filePro and GIserver using the default installation on a SCO UNIX PC:
password=àîä)EΧfˆ
recall=1
remoteShutdown=true
log=true
serverName=Ray1
idleout=0
timeout=3
port=4350
admin=true
adminName=ray
remoteShutDown=true
debug=true
forcePassword=false
serverAddress=192.168.0.5
exec=/appl/fp/fPdaemon_sco
licensePort=4550
shutdownOnExit=true
adminPort=4450
expires=0
Examples of default.cfg:
-
Developer installed filePro and GIserver using the c:\Roadshow Directory installation on his C: drive on a Native 32 Windows 98 PC:
startcmd="p dpromenu"
PFDSK=C
PFPROG=C:/Roadshow
PFDATA=C:
PFDROPSHADOW=OFF
PFDIR=/Roadshow
pfign=abd
PFNEWNTCONSOLE=ON
PATH=%PFPROG%\fp;C:\WINDOWS\COMMAND
log=false
debuglog=false
doIdleOut=false
-
Developer installed filePro and GIserver using the c:\50WIN Directory installation on his C: drive on a Native 32 Windows NT PC...Note the addition of two key environment variables: SystemDrive and SystemRoot if they are absent GIserver will not work on an NT or Windows 2000 [W2K] platform:
startcmd="p dpromenu"
PFDSK=C
PFPROG=C:/Roadshow
PFDATA=C:
PFDROPSHADOW=OFF
PFDIR=/Roadshow
pfign=abd
PFNEWNTCONSOLE=ON
PATH=%PFPROG%\fp;C:\WINDOWS\COMMAND
SystemDrive=C:
SystemRoot=C:\WINNT
log=false
debuglog=false
doIdleOut=false
Copyright 2001-2003, fP Technologies, Inc. All Rights Reserved
These documents are covered under the terms and conditions of the fP Technologies, Inc. Program License Agreement
rev. 01/24/2003