Normally an XMA application is started by a clicking an XMA HTTP link (a link ending at .xma). To start an XMA application like that, an XMA link (.xma) must be associated with the XMA Boot-Runtime's executable (xma.exe, xma.sh). Details about XMA web browser integration (e.g. Firefox issues) can be found at Calling XMA-Components via Browser Links.

Under Windows the XMA Boot-Runtime (and so the XMA application) is normally launched by an executable xma.exe. This executable is created by a utility called Launch4J. Beside launching the main class this executable sets the right classpath and library path entries and is able to find and to use a JRE (>= 1.4.2). If no JRE is installed an error dialog is shown. The MIME-type application/x-xmalauncher has to be associated with xma.exe to start an XMA application by an simple click at an URL link. For Internet Explorer this association is done by the Windows registry.

Under Linux / Mac OS X the XMA Boot-Runtime is normally launched by a script xma.sh. The absolute path entries (like the classpath and the path to the JRE) are configured during the XMA Boot-Runtime installation. The MIME-type application/x-xmalauncher has to be associated with xma.sh to start an XMA application by an simple click at an URL link.

The following Java libraries have to be in the classpath at startup. The xma.exe and xma.sh already set these entries. Whatever other method is used to launch an XMA application has to take care of these:

The following Java system properties are needed. The xma.exe and xma.sh already set these entries: