Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Where 'start' and 'end' represent the port number range within which the PI Service must find an available port. To fix the PI Service to a single port enter the same number twice.

Initializing the FEWS PI Service using a backend process

It is also possible to initialize the FEWS PI Service as a backend process. This is doen by starting a regular Operator Client application, but then without a user interface.

The backend FEWS PI Service can be started under Windows by using the following JPIF information:

Code Block

..\jre
-mx512m
-cp
$JARS_PATH$
nl.wldelft.fews.system.fewsserver.FewsEnvironmentShell
<OC-Name>

Or under Linux by changing the main class in the fews.sh file from nl.wldelft.fews.gui.explorer.Application to nl.wldelft.fews.system.fewsserver.FewsEnvironmentShell

This backend FEWS PI Service does not use the Explorer configuration, as described above, to obtain the listener port number. This is to avoid port conflicts when a client FEWS PI Service is started on the same machine as a backend FEWS PI Service or when multiple instance of a backend FEWS PI Service are running on the same machine.

Example code

Here follows some example code of how client applications can set up a connection the PI Service of a running FEWS OC.

...