PDoc-System Defaults

System Default Registry Settings

Local system settings default to the machine name, and everthing is built from that.

Simple machines

The name assigned to the computer is used as MachineID, unless this is overriden by using [MachineID]. This override allows different setups to be tested simply by changing the one entry and not having to rename a machine.

Then Base is set to c:\MachineID\ unless it is overridden.

Then Data is set to MachineID:Base\Data\ unless it is overridden.

Picture,Profile and Text follow the same pattern, using the Base\xxx\ format. These may beoverriden in the System4 registry key.

Logging will default to the local logging directory, with a sub-directory of the program name.

Other directory defaults need to be checked in each program.

So all that is required is to set the machine name, and default directory structure, and then we have the following setup
 

Base	c:\Computer\
Data	Computer:c:\Computer\Data\
Picture	c:\Computer\Picture\
Profile	c:\Computer\Profile\
Text	c:\Computer\Text\
Logging	c:\Computer\Logging\XXX ( Sub Directory of program )

Message Polling is carried out to ServerMain, which defaults to the local machine when that entry is not set, so that all messaging is contained within the machine.

Multiple machine setups will then override some parts of this as required.

Single Station with multiple computers

LocalHub running in NetworkMode = 0

In this configuration, [ServerMain] will define the location of the site specific server, and all defaults will be modified to reflect this change.
 

Base	s:\	( s:\ will be mapped to the ServerMain:c:\ServerMain\ directory )
Data	ServerMain:c:\ServerMain\Data\
Picture	default
Profile	default
Text	s:\Text\	See Base for setting of s: drive
Logging	default	Normally local to each machine

Each computer on the system requires it's own ID, and the bulk data is stored on each machine in it's own base directory. The local data and text files are then overriden to use the server machine instead of the local information.

This situation also applies to multiple machines in a control center situation, but in this configuration, the Picture and Profile directories will need to be manually overriden to the shared s: drive, so that changes are correctly handled.

In this setup, the ServerMain entry identifies the machine that is to be contacted when message replies are being sent. The EquipmentManager main program is required to be running on the MainServer, but can be overriden using [MessageMain] registry entry, when it is required to use two machines to provide the server facilities.

Multiple Station - Remote Machines

LocalHub running in NetworkMode = 1 or 2

In this network mode, the slave stations work with two levels of connection. All of the local database accesses are controlled by the default settings, while a second level of connection provides replication of data from the control center to the local copies. The location of the control center is provide by the [NetworkMain] entry, and in most situations this will be the main server at the control center. This can be overidden by the NetworkBase entry if required, and the location of EquipmentManager can also be modified by the [MessageMain] entry.
 

Base	local default
Data	local default
Picture	local default
Profile	local default
Text	local default
NetworkBase	NetworkMain:\c:\NetworkMain\Data\

FTP transfers are processed using the MachineID as the key element. This is also used as the default [User] name. So for FTP transfers to take place, the target Machine name and user name should be left at default. Password for FTP is the same as used for the database access, but the system requires that the same setting is used for every machine, as the local setting is used for verification, and so must match the remote end.

Split Station Working

This is simply a special case of the Multiple Station setup, where the remote station runs normally, but a single machine provides both server and station operations at the same time. this is configured as a simple station setup, but runs two copies of CIS Operator, one for the train movements, and a second for the local station displays.

User Name and Password

By default, a machine's user name defaults to the MachineID. Because of problems with inconsistant operation within different versions of Windows operating system, the convention has been adopted that only Upper Case names will be used. Where Windows converts the MachineID to some other combination, the internally accessed value is forced to Upper Case. The Firebird server, then only requires a matching Upper Case User Name to allow access.

Because of the way FTP pransfers are handled, a single Password is required across the system, and defaults to "letmein". If it is required to change this, then the same new password must be entered into the registry on all machines. The security aspects of this may need to be reviewed later.

Port Numbering

The system uses a block of TCP/IP ports for communications between modules. These default from the LocalListen entry, but sub-sections can be moved away if required. The default value for LocalListen is 40000, which places it in the user defined area of port numbers, and should only need to be changed if it is found that other private applications are using addresses in that area. The basic map is as follows:-
 

LocalListen	Local Hub Module
+1	Local Program 1
+2	Local Program 2
+3	Local Program 3
+4	Local Program 4
+5	Local Program 5
+6	Local Program 6
+7	Local Program 7
+8	Local Program 8
+9	( Spare )
+10	NetworkListen	[NetworkListen]
+11	NetworkSend	[NetworkSend] *
12 to 20	( Spare )
+ 21	Ftp	[Ftp] **

* NetworkSend defaults to NetworkListen + 1, so if NetworkListen is overridden, then NetworkSend will move as well unless it has it's own entry provided.

** Ftp services are only enabled on a machine if the ServerMain machine name is set and has a different value to the MachineID. If it is required to disable Ftp, then an override of [Ftp]=0 can be used.

Local Listen can be enabled by simply setting it to 0 ( [LocalListen]=0 ). This can be used if it is required to run a local program module without the LocalHub management, but since it is a global setting, it's use would be confined to test purposes only.

Multicast Address

The default Multicast Address has been set to 238.240.1.1but on a managed network, the Multicast Address we use should be allocated by the network administrator. Multicast is currently only used to broadcast poll messages from EquipmentManager, in order that a group of stations can be accessed at once. The current reply mechanism transmits back direct to the EquipmentManager program. This is normally located on the ServerMain, but can be overriden if required by providing a [MeassageMain] entry.

Further development of the system should restore dual multicast operation, so that a pair of servers can monitor the network in parallel, and if one fails, the second unit can talk over automatically. This is a facility that is currently disabled, because of problems with the way Frame Relay implements multicast.

Issue C - Added UserName and Password, Port Numbering and Multicast Address Sections