This content applies to Weave 2.5. Weave 2.6 system properties should be set in a file in the |
There are various internal settings within Weave that globally alter the way the server functions. These settings can be altered by setting a "system property" which is read when the server starts up.
Occasionally you'll have to set a system property to alter the way the server behaves, to address a support ticket for example, and here we'll describe how that can be done.
Depending upon how you start Weave there are two places where system properties can be set. If you start Weave as a service the properties are set in ...\weave\service\conf\wrapper.conf
, and if you start Weave via startup.cmd
or startup.sh
the properties are set directly in that file.
No matter where the system property is defined, wrapper.conf
or startup.cmd/startup.sh
, what we will accomplish here is the passing of a new command line parameter to the Weave server process. The command line parameter we're trying to pass to the server process is specified in the format -Dname=value
. The -D
tells the Java process that we're defining a new property, name
is the name of the property we're creating and value
is what we want to set it to. As we do not start the Weave server process manually and rely on the service wrapper or startup.cmd/startup.sh
to do it for us, what we're outlining here is how we tell them to pass the new command line parameter to the process when it starts.
The setting of a system property, as described here, is only a subset of the things we can do with command line parameters set in the wrapper.conf
or startup.cmd/startup.sh
, but this How-to page will only cover setting system properties.
Setting a system property in wrapper.conf
...\weave\service\conf\wrapper.conf
in the text editor of your choice.wrapper.java.additional.## = ...
-Dname=value.
wrapper.conf
.wrapper.java.additional.22 = -Dweave.spatial.operation.limit=500 |
Setting a system property in startup.cmd
...\weave\startup.cmd
in the text editor of your choice.SET JAVA_OPTS
line in the file (they are set through the file and the last one would usually be defined near the end of the file).SET JAVA_OPTS=%JAVA_OPTS% -D...=...
JAVA_OPTS
variable that is then passed to the Java process at the end of the file.SET JAVA_OPTS
line after the last one with the format:SET JAVA_OPTS=%JAVA_OPTS% -Dname=value
SET JAVA_OPTS=%JAVA_OPTS% -Dweave.spatial.operation.limit=500 |
Setting a system property in startup.sh
...\weave\startup.sh
in the text editor of your choice.JAVA_OPTS="$JAVA_OPTS ..."
line in the file (they are set through the file and the last one would usually be defined near the end of the file).JAVA_OPTS="$JAVA_OPTS -D...=..."
JAVA_OPTS
variable that is then passed to the Java process at the end of the file.JAVA_OPTS
line after the last one with the format:JAVA_OPTS="$JAVA_OPTS -Dname=value"
JAVA_OPTS="$JAVA_OPTS -Dweave.spatial.operation.limit=500" |
... there's more content before here #******************************************************************** |
... there's more content before here REM Force coordinate axis order for compatability REM Uncomment the line below to allow a debugger to be attached REM Set Jetty options SET JAVA_OPTS=%JAVA_OPTS% -Dweave.spatial.operation.limit=500 cd jetty "..\jre\bin\java.exe" %JAVA_OPTS% -jar start.jar --ini=..\jetty.ini popd |
... there's more content before here # Force coordinate axis order for compatability # Uncomment the line below to allow a debugger to be attached # Set Jetty options JAVA_OPTS="$JAVA_OPTS -Dweave.spatial.operation.limit=500" cd jetty ../jre/bin/java $JAVA_OPTS -jar start.jar --ini=../jetty.ini cd .. |
The content by label feature displays related articles automatically, based on labels you choose. To edit options for this feature, select the placeholder below and tap the pencil icon.
|