| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Use the attribute configuration_directory in ./config/scheduler.xml
| Code Block |
|---|
<spooler>
<config mail_xslt_stylesheet="config/scheduler_mail.xsl"
port="4444"
configuration_directory="/path/to/another/live/folder"
>
...
</config>
</spooler>
|
By setting the attribute @configuration configuration_directory of the config element you can specify a folder for the configuration of the jobs, job definitionschains, orders, schedules , run-times et ceteraetc.. The default setting is the live directory, which itself is to be found in the same directory as the configuration file ./config/scheduler.xml.
See also here for further information.
Alternatively you can use the command line option -configuration-directory.
| Code Block |
|---|
> ./bin/jobscheduler.sh start -configuration-directory="/path/to/another/live/folder" |
Usage with multiple live folders
It is not possible to configure multiple live folders but you can use symlinks in the live folder so that a subfolder of live pointed to another.
For example, if you have job configurations in /mnt/other_host/live/ then you can add it to the live folder like this:
| Code Block |
|---|
> cd ./config/live
> ln -s /mnt/other_host/live/ live_on_other_host
|
In this case you have a subfolder live_on_other_host in live that contains all objects from /mnt/other_host/live/.