Page History

Anchor
_Toc154574490 _Toc154574490

Anchor
_Toc95297323 _Toc95297323

Root configuration files

Root configuration files define the behaviour of DELFT-FEWS on the local machine. These files are synchronised in the live system environment, nor are they available in the database. The files must be installed locally with the DELFT-FEWS system.

Anchor
_Toc154574491 _Toc154574491

Anchor
_Toc95297324 _Toc95297324

clientConfig

The clientConfig File determines if the instance of DELFT-FEWS is to run as a stand alone system, or if it is to connect to the master controllers defined below.
Since 2011.01 the clientConfig file is no longer required for stand alone. Stand alone is the default when the client config is missing

Figure 158 Elements of the clientConfig configuration

clientType

Definition of the client type. Enumeration of options includes;

• Operator Client
• Stand Alone

Anchor
_Toc154574492 _Toc154574492

Anchor
_Toc95297325 _Toc95297325

LogConfig

To be completed

Anchor
_Toc154574493 _Toc154574493

Anchor
_Toc95297326 _Toc95297326

synchConfig

Looks something like this for an OC:

...

The only setting that may demand editting is the <login timeout="10" />, which controls the timeout for a login attempt of the OC on the MC (in seconds). (This element may be absent, in which case the timeout is 10secs)
It may be needed to extend this timeout if the JMS server is very busy (very many clients starting up and synchronising at the same time, e.g. when all the PCs for a workshop are all starting up at the same time).
Note: the xml config can only extend the time out from the default 10 secs. Settings less than 10 secs are ignored)

Anchor
_Toc154574494 _Toc154574494

Anchor
_Toc95297327 _Toc95297327

synchProfiles

The file synchProfiles.xml contains several different profiles for fine-grained control over the synchronisation with the database.

...

See also User Administration - Active Users

Anchor
_Toc154574495 _Toc154574495

Anchor
_Toc95297328 _Toc95297328

synchChannels

To be completed

Working with pool of localDataStores (under Citrix)

A standard installation will have to be adjusted to work well in a Citrix environment. It is possible to keep your own localDatastore folder, which is then stored on your personal home directory on the Citrix server or the localDatastore can be stored centrally on the hard drive of the citrix server, in what we call a pool directory. This pool can currently exist of a maximum of 11 users at the same time (hard coded). In this case 11 localdatastore folders are created in de pooldirectory.

The following adjustments will have to be made:

   1. in the jpif file, used together with the executable to start up the application, the last line will have to be replaced with

      $USER_HOME$\Local Settings\Application Data\<name of application root directory>_OC
      This is needed to make sure FEWS is working in multi-user mode, with caching in the profile directory, where $USER_HOME$ is a reference to the profile of the user. At the same time you can also make use of the localDataStorePoolDir and therefore two more adjustments will have to be made. 

   2. het bestand \BOS_NZV_OC\global.properties hernoemen naar citrix_global.properties, zodat er een aparte variant voor citrix is.

   3. in het bestand \BOS_NZV_OC\citrix_global.properties de volgende regel toevoegen: localDataStorePoolDir=\[C:\FewsLocalDataStores\]
      zet voor de zekerheid nog een extra lege regel na deze instelling, er was onlangs een bugje dat de allerlaatste regel niet werd ingelezen.
      let ook op dat localDataStorePoolDir hoofdlettergevoelig. Uiteraard kun je zelf definiëren waar de pooldir moet staan.

Global.properties file