<XMA_HOME>\xma\lib\commons-httpclient_3.0.1.jar

For HTTP communication the Jakarta Commons HttpClient is used.

See http://jakarta.apache.org/httpcomponents/httpclient-3.x/

<XMA_HOME>\xma\lib\commons-logging-1.1.jar

The Jakarta Commons HttpClient is dependent from this library

See http://commons.apache.org/logging/

<XMA_HOME>\xma\lib\javaxdelta-1.1.0.jar

Java library for delta download

See http://sourceforge.net/projects/javaxdelta/

<XMA_HOME>\xma\natives

Windows only: DLL with JNI implementations (for Windows Registry reading and Windows pipe handling). The Windows version of openXMA reads and uses the proxy settings form the registry (can be set in Internet Explorer).

<XMA_HOME>\xma\settings\bootcfg.properties

proxy setting and certificate store files

The proxy settings are determined by the bootcfg.properties file. The settings in this file are created by the installation. These settings can be changed afterward, but usually the primary configuration is also the desired one at runtime.

<XMA_HOME>\xma\settings\cacerts

A Java keystore file storing the public key certificates accepted as root for SSL communication. The JRE also provides such a keystore (jre/lib/security/cacerts), to use an own enables XMA to configure additional root certificates.

<XMA_HOME>\xma\xma_swt\

SWT Java library and natives. XMA is based at this GUI framework, which uses native controls. The SWT classes do not need to be in the XMA classpath at startup. The SWT version to use can be configured by each XMA application. Right now with the XMA-BootRuntime the SWT versions 3.1.2 , 3.2.2 and 3.3 are delivered.

SWT 3.3 is used by default. The default is configured by the bootcfg.properties, also every XMA application can decide on its own which SWT version to use.

Also see The Standard Widget Toolkit

<XMA_HOME>\xma\xma_bootrt\

XMA Boot-Runtime libraries: xmabootrt.jar, xmacom.jar

<XMA_HOME>\xma\version.txt

A text file stating the XMA Boot-Runtime’s version

<XMA_HOME>\xma\xma.exe

The executable/Java launcher (xma.exe, xma.sh) starting the XMA Boot-Runtime client

<Cache-Log-Directory>\Cache

Here the downloaded XMA components are cached.

<Cache-Log-Directory>\log

Here on XMA application startup, daily a new log file is created. This file serves for the logging of the client side of an XMA application. It is deleted after 30 days.