Versions Compared

Key

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

...

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

Or in Linux by changing the main class in the fews.sh file:using the Fews-piservice.sh file. This file should be placed in the same directory as the links to the JRE, BIN and the REGION dirs.

Code Block
# start changethe this
${JAVA_HOME:-/opt/fews/java}/bin/java -Xmx512M $JVM_OPTS -Djava.library.path=$BINDIR \
   -classpath "$classes" \
   nl.wldelft.fews.gui.explorer.Application $REGIONHOME $BINDIR

# to this
${JAVA_HOME:-/opt/fews/java}/bin/java -Xmx512M $JVM_OPTS -Djava.library.path=$BINDIR \
   -classpath "$classes" \
   nl.wldelft.fews.system.fewsserver.FewsEnvironmentShell $REGIONHOME $BINDIRservice
./fews_piservice.sh <REGION NAME> start

# stop the servie
./fews_piservice.sh <REGION NAME> stop

This backend FEWS PI Service does not use the Explorer configuration, as described above, to obtain the listener port number. This is to make sure that the client FEWS PI Services can run independently from the backend FEWS PI Services without port conflicts. Instead the backend FEWS PI Service obtains its listener port from the global.properties files, using the entry:

...