| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Scope
- This article explains configuration of the Classic JobScheduler Agent
Display feature availability EndingWithRelease 1.10 - For configuration of the JobScheduler Universal Agent see JobScheduler Universal Agent - Installation & Operation
Display feature availability StartingFromRelease 1.10
JobScheduler and Agent
- The architecture for JobScheduler and Agents forces some prerequisites.
- Make sure that the JobScheduler can communicate with the Agent JobScheduler and vice versa.
JobScheduler Agent configuration
For this, edit the ./config/scheduler.xml of the Main JobScheduler:
...
- Make sure that no firewall restricts the communication.
- See also http://www.sos-berlin.com/doc/en/scheduler.doc/remote_execution.xml
Process Class configuration
Now you need a Process Class and a Job in the Hot Folder (./config/live) of the JobScheduler to test the JobScheduler Agent.
...
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="ISO-8859-1"?> <process_class max_processes="30" remote_scheduler="wilma:4410"/> |
Job configuration
- Create the job that uses the above process class.
- Click on Jobs in the left tree of the JobScheduler elements.
- With New Standalone Jobs on the right hand side you create a new job in the list of the jobs and in the left tree. Select it to open an empty job configuration element.
...