Date: Thu, 28 Mar 2024 21:38:00 +0000 (UTC) Message-ID: <1876870734.11999.1711661880452@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11998_828438943.1711661880452" ------=_Part_11998_828438943.1711661880452 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The general mail settings are made during the JobScheduler Setup. These =
are stored in the ./config/factory.ini file.
These settings apply to all jobs, but this can be overridden in the job co=
nfiguration.
In the section [spooler]<=
/strong> you have entries for the email addresses of the sender and recipie=
nts (incl. cc and bcc). Use a comma to separate multiple email addresses.=
p>
Further you must set the SMTP server The following entries control when a email will be sent. In a section [smtp] you can set an email account if necessary Look at the table here for more java mail properties. Look here for more informat=
ion about the factory.ini. When you configure a Job in JOE (JobScheduler Object Editor) then you ha=
ve the Job displayed in the left tree view.
Mail settings are only configurable for a Job. We assume that you have a Job Chain with multiple Order-Jobs in the foll=
owing structure. If you have set If you have set If you have set If you want exactly one 'success' mail per Job Chain Order then configur=
e all Jobs except the last Job with We recommend that you create a new Order-Job which is called e.g. /l=
astJobChainJob. This Order-Job is the only Order-Job which has the All other Order-Jobs should have You insert this Order-Job /lastJobChainJob to all Job Chains as=
the last Job. The Job /lastJobChainJob can use the internal API to modify the=
mail subject in the following form: log_mai=
l_from=09 =3D=20
log_mail_to=09 =3D=20
log_mail_cc=09 =3D=20
log_mail_bcc=09 =3D=20
smtp=09=
=3D=20
; =
send mail with job log in case of error (yes|no, default=
: no)
mail_on_error =3D yes
; send mail with job log in case of errors and war=
nings (yes|no, default: no); only for api jobs
mail_on_warning =3D yes
; send mail with job log in case of success (yes|n=
o, default: no)
mail_on_success =3D no
; send mail with job log in case of process steps =
(yes|no|1|2|n, default: no); only for standalone api jobs
mail_on_process =3D no
mail.sm=
tp.user =3D
mail.smtp.password =3D
mail.smtp.port =3D 25
Ma=
il Settings in the Job Configuration
Open the Job and then open the Job Settings.Mail Settings in the Job Chain Configuration
Whenever a Job in the Job Chain has an error then the Order goes to the En=
d Node 'error'.
Otherwise the Order goes to the next Job and finally in the End Node 'succ=
ess'.mail_on_error =3D yes
in the ./config/f=
actory.ini (recommended), then you get max. one error mail pe=
r Job Chain Order.mail_on_success
in the=
./config/factory.ini, then you get a success mail for ea=
ch Job in the Job Chain per Order. =3D
yesmail_on_success
in the =
./config/factory.ini (recommended), then you get no success mail for each Job Chain per Order. =3D
nomail_on_success
. =3D
=
no =3D
yes setting.mail_on_success
. =3D
=
no <?xm=
l version=3D"1.0" encoding=3D"ISO-8859-1"?>
=20
=20
<job order=3D"yes" stop_on_error=3D"no">
<settings>
<mail_on_success><![CDATA[yes]]></mail_on_success&g=
t;
</settings>=20
=20
<script language=3D"javascript">
<![CDATA[
function spooler_process() {=20
=20
=09spooler_log.mail.subject =3D "job chain '" + spooler_task.order.job_cha=
in.name() + "' has successfully finished";
=09return true;
}
]]>
</script>
=20
<run_time />
</job>