Details
-
Feature
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Using a process class with only one JobScheduler Universal Agent should be enabled for file order sources.
- A new attribute file_watching_process_class for the <job_chain> element denotes a process class for monitoring files on remote agents
- This process class is used
- file order sources
- file sinks
- If the attribute file_watching_process_class is empty, it defaults to the process class of the job chain (
JS-1301) - The process class must denote only one agent. Using process classes with multiple agents will be implemented in
JS-1427 - Changing the process class at runtime will have no effect on the file_order_source or file_order_sink
The element <remote_schedulers> will be ignored when the process class is used for the attribute file_watching_process_class in the <job_chain> element. The atttribute remote_scheduler must be configured in this case.
For example:
<process_classes > <process_class max_processes="1" remote_scheduler="http://wilma:4444" name="test"> <remote_schedulers > <remote_scheduler remote_scheduler="http://homer:4444"/> <remote_scheduler remote_scheduler="http://test:4000"/> </remote_schedulers> </process_class> </process_classes>
Attachments
Issue Links
- is related to
-
JS-1422 <file_order_sink> on JobScheduler Universal Agent
- Released
- is required by
-
JOE-157 Allow attribute file_watching_process_class for <job_chain> Element
- Released
-
JS-1428 Deprecation of attribute remote_scheduler for file_order_source
- Deprecated
- relates to
-
JS-1291 JobScheduler Universal Agent
- Released
-
JS-1300 <file_order_source> on JobScheduler Universal Agent
- Released
- mentioned in
-
Page Loading...