All Settings are made in a xml file which Contains the entries for each agent. You find the xsd-schema in config/scheduler_agent_installations.xsd
The file have the structure
In the globals entry, you specify the value which are used for all installation items. The installation items can overwrite these values. There is one installation item for each agent. You can make use of substitution in the values of the entries.
Example:<serviceId>scheduler_agent_${host}_${service_port}</serviceId>
The globals section have the following entries:
All Settings are made in a xml file which Contains the entries for each agent. You find the xsd-schema in config/scheduler_agent_installations.xsd
The file have the structure
In the globals entry, you specify the value which are used for all installation items. The installation items can overwrite these values. There is one installation item for each agent. You can make use of substitution in the values of the entries.
Example:<serviceId>scheduler_agent_${host}_${service_port}</serviceId>
The globals section have the following entries:
Der Job erzeugt Aufträge für die Jobkette "installation_job_chain".
Die Jobkette hat die vier Knoten:
Die Aufträge sind wie folgt parametrisiert::
Die Werte entstammen der XML Datei aus "installation_definition_file".
Als Update ausführen:Falls Sie die Installationen als Update ausführen wollen, setzen Sie den Parameter update=true. Damit werden bestehende Agenten aktualisiert und neue installiert. Ein angegebener Filter (host, port) wird dabei berücksichtigt.
All orders can run in parallel.
The orders are parameterized as follows:
The value are specified in the file "installation_definition_file"
Perform as an update:If you want to update your installations, set parameter update=true. This will update existing installations and install new agents. A given filter (host, port) is recognized.