...
| No Format |
|---|
<lcsim>
<inputFiles>
<fileUrl />
<file />
<fileSet>
<file />
</fileSet>
<fileList />
<fileUrlList />
</inputFiles>
<control>
<dryRun>true</dryRun>
<logFile>/path/to/mylog.txt</logFile>
<cacheDirectory>/path/to/mycache/</cacheDirectory>
<skipEvents>1</skipEvents>
<numberOfEvents>1000</numberOfEvents>
<verbose>true</verbose>
<printDriverStatistics>true</printDriverStatistics>
<printSystemProperties>true</printSystemProperties>
<printUserClassPath>true</printUserClassPath>
<printDriversDetailed>true</printDriversDetailed>
</control>
<classpath>
<jarUrl />
<jar />
<directory />
</classpath>
<define>
<anExampleVariable>1234</anExampleVarible>
</define>
<execute>
<driver name="ExampleDriver" />
</execute>
<drivers>
<driver name="ExampleDriver" type="org.lcsim.example.ExampleDriver">
<exampleParam>1234</exampleParam>
<exampleArrayParam>1 2 3 4</exampleParam>
<exampleArray2DParam>1 2 3 4; 5 6 7 8</exampleArray2DParam>
</driver>
</drivers>
</lcsim>
|
Each of these xml sections will be explained in greater detail belowThe format is completely described by the LCSim XML Schema. At run-time, the actual schema is not read from the internet but from an embedded resource in the LCSim jar file. If your XML file does not follow this format, the job will fail, and a trace back will be printed with information about the error.
Input Files
The <inputFiles> section contains a list of local or remote files to be processed. It may contain a mixture of any of the elements described below, but it may not be empty. And it must result in at least one input file being found or the job will fail.
...