Introduction
This job template is used to send mail from an Agent.
- The job template makes use of the SMTP protocol.
- The job template can be used to access any database for which a JDBC Driver is available with the Agent.
- The JS7 includes a number of JDBC Drivers for supported DBMS, see JS7 - Database.
- For other DBMS you can provide an individual JDBC Driver and store the Driver's .jar file with the .
/lib/user_lib
directory of the Agent installation.
Usage
When defining the job consider
- to specify an Agent that should execute the job,
- to select the JITL job class,
- to specify the
com.sos.jitl.jobs.mail.MailJob
Java class name, - to provide variables specifying what to send and where to send mail.
You can use the job wizard like this:
Explanation:
- Add an empty job from the instruction panel.
- Specify a name and a label for the job.
In a next step invoke the job wizard that you find in the upper right corner of the job property editor. The wizard brings up the following popup window:
Explanation:
- From the list of available job template select the
MailJob
.
Then hit the "Next" button to make the job wizard display available job variables:
Explanation:
- Required job variables include the
to
variable to specify the recipient of mails. - Any other variables are optional provided that a job resource is used that specifies connection details to your mail server.
- Select the job variables
When hitting the "Submit" button the wizard adds the required settings to your job that should look like this:
The job arguments can be specified as follows:
Arguments
The com.sos.jitl.jobs.db.SQLExecutorJob
class accepts the following arguments:
Name | Required | Default Value | Purpose |
---|---|---|---|
command | yes | Carries the SQL statements. | |
| no | ./config/hibernate.cfg.xml | Specifies the configuration file (XML) format for Hibernate connections, see JS7 - Database. By default Agents ship without hibernate configuration files, however, if a file with the default name is available then it will be applied. |
| no | Raises a warning if the SQL statement creates a result set. | |
| no | If stored procedures are called that return a result set then this argument has to be set to | |
| no | Specifies how a result set is forwarded to order variables for subsequent jobs:
|
Explanation:
- Note that it is possible to define more than one instruction with the
command
argument.
Such instructions are then carried out in the order in which they are written and must be separated by a semicolon.- Some DBMS might require and additional newline character.
- For example
update MY_TABLE set a='foo' where b='bar'; commit;
- Note also that order variables and arguments can be injected to the SQL statement(s) of the
command
argument by use of the${variable}
syntax.
Further information
- Job Documentation: