6.18 Appendix B: XMA BootRuntime Properties

The behavior of the XMA BootRuntime can be customized by the following properties. The parameters are read from the file settings/bootcfg.properties under the XMA BootRuntime installation directory. Note, that for end users this file is usually not editable. So the values have to be set during installation. Right now only the cache and log directory can be set by the installation, additional values may follow if requested.

XMA developers have the possibility to create a folder and a file settings/bootcfg.properties directly in their XMA project. If the XMA application is started by an Eclipse *.lauch file from to the project then the project's settings/bootcfg.properties file is used.

Parameter Name

Description

Default value

boot.datapath

The directory where the cache directory will be created. In the cache directory all downloaded resources (e.g. the client side code of all XMA-applications) will be stored.

 

boot.log.logdir

The directory where to put the logfiles. In the log directory one logfile per day will be written. They are deleted after the time specified in boot.cleaner.logfiles.cachetimeout.

"logs" created under the directory given in boot.datapath

boot.log.handlers

Fully qualified classnames of LogHandlers separated by ", ".

Logs into a file created in boot.log.logdir

boot.log.level

  • OFF: no logging at all

  • SEVERE: only errors preventing the XMA Runtime to work are logged

  • WARNING: all exceptions are logged

  • INFO: tracing of the caching mechanism activated

  • FINE: more tracing

  • ALL: all trace messages are logged

INFO

boot.xmlparser.validate

If true the application descriptor files xma-app.xml and plugins.xml are validated against its DTD on the client. If false they are only validated on the server side. This allows the addition of new elements or parameters to the xml-files for new versions of the XMA-BootRuntime without violation compatibility with older versions still installed on some clients.

false

boot.cleaner.initial_delay

Time for the cache cleaner demon to wait after the XAM-BootRuntime is started in seconds. After this time all resources in the cache are checked.

900 (=15 min)

boot.cleaner. cleanup_interval

Time between runs of the cache cleaner demon in seconds. After this time all resources in the cache are checked again.

10800 (= 3h)

boot.cleaner.logfiles. cachetimeout

Time (in seconds) after which logfiles are deleted. This time is measured from the last writing into the file.

2592000 (= 30 days)

boot.cleaner.application. cachetimeout

Time (in seconds) after which unused XMA applications are deleted from the cache.

This time is measured from the last start of the respective applications.

15552000 (= 180 days)

boot.session. keepalive_interval

Default interval between keep-alive calls in seconds. This property is used if the application did not specify xma.runtime.keepalive_interval.

3300 (= 55 min)

boot.transport. useproxysettings fromregistry

If true, read and use the current proxy settings of MS Internet Explorer. This overrides all other proxy parameters. That means, the following 6 properties are irrelevant if this property is set to true.

true

boot.transport. proxyenable

If true use the configured proxy servers for HTTP and HTTPS. If false always connect directly.

false

boot.transport. proxyserver

DNS name or IP address of the proxy server used for HTTP.

 

boot.transport.proxyport

Port of the proxy server used for HTTP.

 

boot.transport. secureproxyserver

DNS name or IP address of the proxy server used for HTTPS.

 

boot.transport. secureproxyport

Port of the proxy server used for HTTPS.

 

boot.transport. proxyoverride

List of hosts for which no proxy shall be used.

Supported are DNS names and IP addresses separated by ";" or "|". As wildcard "*" can be used at the beginning or end of each entry. E.g.: 172.18.*;*.sd.spardat.at

 

boot.transport. connecttimeout

The timeout for HTTP/HTTPS connection attempts in milliseconds.

300000 (=5 min)

boot.transport. readtimeout

The timeout for reading from an established connection in milliseconds.

600000 (=10 min)

boot.transport. hostnameverify.ignore

List of hosts for which the host name given in the URL and the host name given in its SSL-certificate do not need to match. This enables the use of HTTPS with simple test certificates at the listed hosts. Supported are DNS names and IP addresses separated by ";" or "|". As wildcard "*" can be used at the beginning or end of each entry.

Example: 172.18.*;10.*

 

boot.transport.hostname. accept

States hosts where a connection will be allowed. The format of this property is similar to boot.transport.hostnameverify.ignore.

If this property is empty then every host is accepted, otherwise the given host has to match an entry. A host name is also local DNS resolved to its IP address, so you can also allow or block hosts by IP addresses, even when the component is addressed by the host name at runtime.

Example: localhost;10.*

 

boot.transport. hostname.block

States hosts where a connection will be blocked. The format of this property is similar to boot.transport.hostnameverify.ignore, DNS resolving is like described above.

Even a host allowed by boot.transport.hostname.accept can be blocked by this property.

 

boot.transport. secure.truststore

The full pathname of a Java keystore file containing the root certificates trusted by the SSL implementation.

 

boot.transport. urlencoding

Encoding to use to escape non-ascii characters in URLs or URL parameters.

Default encoding of the JVM.

boot.transport. cookiepolicy

Fully qualified classname of an Object defining the details about cookie handling. One of the implementations contained in apache httpClient can be chosen here.

org.apache.commons. httpclient.cookie. CookieSpecBase

boot.showloghint

If true, a reference to the client side log file is placed at the end of error messages shown by the BootRuntime.

false

boot.swt.version

Default SWT Version for all XMA applications. It is used if the application has no swt-description tag in its descriptor file. If none of the versions described in the swt-description tag of an application, this version is used, too. seeSWT-Description

3.1.1

boot.swt.basedir

Directory to search for installed SWT versions.

Subdirectory "xma_swt" of XMA installation directory

Table 6.18. bootcfg.porperties


Between the proxy properties there are some interdependences.

If boot.transport.useproxysettingsfromregistry=true then the following properties are read from the Internet Explorer and these values in the bootcft.properties file are ignored:

  • boot.transport.proxyenable

  • boot.transport.proxyserver

  • boot.transport.proxyport

  • boot.transport.secureproxyserver

  • boot.transport.secureproxyport

  • boot.transport.proxyoverride