| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Scope
- This article explains configuration for the Classic JobScheduler Agent
FEATURE AVAILABILITY ENDING WITH RELEASE 1.10 - For general configuration of the JobScheduler Universal Agent see JobScheduler Universal Agent - Installation & Operation
FEATURE AVAILABILITY STARTING FROM RELEASE 1.10 - For dynamic assignment of JobScheduler Universal Agents to Jobs see:
Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1189
- Consider the How to split and sync a dynamic number of job instances for execution with Agents article.
Process Classes for use with JobScheduler Agents
...
Create the following job, e.g. setAgent, and add it to the job chain as the forerunner of the JobScheduler Agent job.
This job modifies the process_class setting of the successor job in the job chain according to the order parameters agent_host_ and _agent_port:
Code Block language html/xml <?xml version="1.0" encoding="ISO-8859-1"?> <job order="yes" stop_on_error="no"> <params /> <script language="java:javascript"><![CDATA[ function spooler_process() { var curOrder = spooler_task.order; var agentHost = curOrder.params.value('agent_host'); var agentPort = curOrder.params.value('agent_port'); var nextJob = curOrder.job_chain_node.next_node.job; spooler_log.info("Params agentHost:agentPort = "+agentHost+":"+agentPort); spooler_log.info("before: "+nextJob.process_class.remote_scheduler); nextJob.process_class.remote_scheduler = agentHost+":"+agentPort; spooler_log.info("after: "+nextJob.process_class.remote_scheduler); return true; } ]]></script> <run_time /> </job>
...