Launcher User's Guide

Launcher 2.0 contains major changes. So, follow these instructions to be Launcher 2.0 compliant

See also this page for a description of the Launcher's DTD.

Launcher Script

Launcher configuration file (*.xml) must be the first argument of the launcher script.

Moreover the Launcher configuration file must be an URL, e.g. file:myapp-config.xml.

launcher.sh exec "" "file:myapp-conf.xml $*"

On Windows System, you can't call the Launcher script directly in a shell. You rather should write you own script by setting variables.

1. You must set the LAUNCHER_ARGS variable. This variable contains arguments for the Launcher application

   set LAUNCHER_ARGS="file:myapp-config.xml" %*

2. You may have to set the LAUNCHER_JVM_ARGS variable. This variable is used to give arguments to the JVM that will run the Launcher

   set LAUNCHER_JVM_ARGS=-DXXX

3. Then you just have to call the Launcher script

   call openccm_launcher [exec|fork]

The root element of the Launcher DTD

The root element of the Launcher DTD is now Launcher (instead of LauncherConfig in previous versions).

<launcher> ... </launcher>

File reference

Each reference to a file must be an URL in launcher configuration files (e.g. pathes, includes, ...).

<include url="file:Compiler.xml" />

Launcher Arguments

Launcher 2.0 introduce two kinds of arguments :

• <arg value="arg1"/>

  for single argument

• <arg line="arg2 arg3"/>

  for multiple arguments.

Multiple arguments will be split into several individual arguments.