Details
-
Feature
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
Jobs which send emails by reading mail settings from factory.ini do not work in the Universal Agent because the Universal Agent does not have these configuration files.
Desired Behaviour
This should be discussed
- is it desired that jobs on the Agent should send mails?
- This might require mail server / firewall admins to allow more hosts
- is it desired that jobs on the Agent should receive email credentials?
- alternatively: is it better to pass emails (e.g. from JobSchedulerManagedDatabaseReportJob) back to the Master Jobscheduler and have the Master send the mail?
Affected jobs
- sos.scheduler.managed.JobSchedulerManagedMailJob
The implementation already provides to set all parameters with the job or order configuration. If the job is used with a configuration coming from a SETTINGS table in a database, this has to be changed to parameters. As the job tries to read the settings from the factory.ini coming with the running JobScheduler instance a warning is written to the log.
[WARN] error occurred processing order [(none)]: Universal Agent does not support method 'sos.spooler.Spooler.ini_path'
To avoid this, the job has to be changed. If already parameters are specified, the file factory.ini should not be read (the method sos.spooler.Spooler.ini_path should not be called).
- sos.scheduler.managed.ManagedReporter
The parameters log_mail_from, mailUser, mailPassword always are readed from the configuration in the file factory.ini.
New parameters for the job are
<params > <param name="host" value="localhost"/> <param name="from" value="agent@sos-berlin.com"/> <param name="smtp_user" value="ur"/> <param name="smtp_password" value="y"/> </params>
- com.sos.jitl.housekeeping.dequeuemail.JobSchedulerDequeueMailJobJSAdapterClass
This job is a housekeeping job that will not run on an Universal JobScheduler Agent but on the JobScheduler Master.
Solution [draft]
- use solution from
JITL-189