System properties are the main means of configuring WSO2 SOA Enablement Server for Java. Default values for these properties are in the resource META-INF/wasp.properties, which is in lib/runner.jar.
There are three ways of altering system properties, for three different types of WSO2 SOA Enablement Server for Java installation:
Standalone Installation: Set the property from the command line when starting the server from the WASP_HOME/bin/server.bat or server.sh script. The syntax is:
server(.sh) [ -Dname of property=value ] { start | stop }
For example:
server -Didoox.debug.level=4 start
WSO2 SOA Enablement Server for Java Embedded in an Application or As a Client: Create a java.util.Map and add your system property definitions to it. This map is passed as an argument to init(java.util.Map) in org.systinet.wasp.Wasp. For more information, please read Init and Destroy Steps.
WSO2 SOA Enablement Server for Java Ported as a Servlet: Default property values can be overridden in context-param elements in the web application deployment descriptor, web.xml. This is described in Porting WSO2 SOA Enablement Server Into a Servlet Container.
The following properties are checked when WSO2 SOA Enablement Server is initialized:
Property | Description | ||||
---|---|---|---|---|---|
ssj.socket.pooling.timeout.millis | Value is a positive integer representing timeout in milliseconds. Use this on client to set up how long a network socket can be held in a pool. This can be useful because some servers close connections after inactivity timeout. If the client is communicating with such a server and you experience "Connection reset" errors, set the value to the timeout setting minus the communication latency. | ||||
wasp.location | This property is mandatory for running the WSO2 SOA Enablement Server. It must point to the directory in which WSO2 SOA Enablement Server is installed. | ||||
wasp.config.location | This is an absolute or wasp.location-relative path pointing to the WSO2 SOA Enablement Server configuration file. Setting this property is optional; the default value is conf/clientconf.xml. | ||||
wasp.config.include | Comma-separated list of additional config paths to include. These paths can be either absolute or relative to the working directory. This property is optional. | ||||
wasp.impl.classpath | Sets a classpath for the WSO2 SOA Enablement Server implementation. This property is optional; if it is not set, WSO2 SOA Enablement Server interfaces and implementation are loaded in the same classloader. | ||||
wasp.instance.name | Sets a unique name for a running instance of WSO2 SOA Enablement Server or client. Used only by the database used with persistent WS-RM reliable messaging. Please see Overview.
| ||||
wasp.soap.caching | Globally sets the flag for SSJ's namespace optimization. Default value is "true". Set to "false" to turn off the optimization. This will allow you to use Microsoft InfoPath™ with any service or client on this instance of WSO2 SOA Enablement Server. Alternatively, you can turn off the namespace optimization for a single service or client, either in runtime configuration or persistently. | ||||
wasp.shutdownhook | Set to "true" if WSO2 SOA Enablement Server should be automatically destroyed just before JVM is destroyed. Set to "false" if you want to manage the shutdown process yourself. Default="true". | ||||
idoox.debug.level | Determines the number of debugging messages produced by WSO2 SOA Enablement Server:
This property is optional; the default value is 2 for the client and 3 for the server. The debug level is available in the non-stripped distribution only. The logging level specified by the idoox.debug.level property overrides the level specified in the configuration file determined by the log4j.configuration property | ||||
idoox.debug.logger | Specifies which logging system is used, waspLogger or log4j. Default is waspLogger. Setting the value of this property to log4j uses this logger, instead. | ||||
log4j.configuration | Specifies the location of the configuration (properties file) for log4j. This property can contain a relative (conf/log4j.config) or absolute (/home/waspuser/log4j.config) path to the configuration file. If it is not set, the default configuration (ConsoleAppender with the pattern %p: %c{2} - %m\n) will be used. An example configuration file for log4j, log4j.config, is located in the conf subdirectory of the WSO2 SOA Enablement Server installation directory. | ||||
log4j.modify.relative.paths | If set to true, it forces WSO2 SOA Enablement Server for Java on boot to modify relative file paths in the appender definitions (defined in the used log4j configuration file) and make them absolute. The absolute path for a particular file appender is constructed from the WSO2 SOA Enablement Server location detected in runtime and the relative file appender path. If it is not set, the WSO2 SOA Enablement Server for Java doesn't modify the log4j configuration at all.
|