For API jobs running on the Agent, most JobScheduler API functions are executed on the Master JobScheduler.
However, some functions need proxy implementations or special treatment to run directly on the Agent:
= treatment still unclear, open for discussion
| function | treatment | remarks |
|---|---|---|
| sos.spooler.Spooler.include_path | FunctionNotSupportedOnAgentException | "Returns the command line setting -include-path=." There no -include-path on the agent. |
| sos.spooler.Spooler.log_dir | FunctionNotSupportedOnAgentException | Task and Order logs are logged on the Master JobScheduler. |
| sos.spooler.Spooler.directory | Proxy | returns working dir of the agent |
| sos.spooler.Spooler.ini_path | FunctionNotSupportedOnAgentException | "The value of the -ini= option (the name of the factory.ini file)" There is no -ini option on the agent |
| sos.spooler.Spooler.create_xslt_stylesheet() | FunctionNotSupportedOnAgentException | deprecated, not used on the agent |
| sos.spooler.Log.log() and other logging functions | Proxy | Proxy checks log level to avoid unnecessary network api calls |
| sos.spooler.Log.start_new_file() | no Proxy | start new file for Master Scheduler |
| sos.spooler.Task.create_subprocess | Proxy | Required to kill subprocesses with task kill |
| sos.spooler.Subprocess all methods | Proxy | |
| sos.spooler.Task.priority_class | Proxy | Is this possible inside the jvm? |
| sos.spooler.Task.priority | Proxy | Is this possible inside the jvm? |
| sos.spooler.Task.std_err_text | Proxy | |
| sos.spooler.Task.std_out_text | Proxy | |
| sos.spooler.Task.std_err_path | Proxy | Do we have such a path in the Java-Based Agent? |
| sos.spooler.Task.std_out_path | Proxy | Do we have such a path in the Java-Based Agent? |
| sos.spooler.Xslt_stylesheet all methods | FunctionNotSupportedOnAgentException | deprecated, not used on the agent |