Example: Job 
The table and figure that follow describe an example of a job customized using the daemon framework in Customizing for Cross-Application Components under 
Demand Data Foundation 
Data Upload
Basic Settings Configure Jobs 
.
Attribute |
Value |
Explanation |
|---|---|---|
Start Date |
03.09.2012 |
Defines the date on which the background job is scheduled to start for the first time. |
Start Time |
21:00:00 |
Defines the time of day at which the background job is scheduled to start for the first time. |
Maximum Runtime |
1 |
Defines the length of time in hours that the job takes to run until completion. If you enter zero (0), the job runs forever or until it is stopped either manually or due to a problem. |
Period |
1 |
Controls when the job scheduler creates a new instance of the job. If you enter zero (0), the job will run once only and is not rescheduled. |
Sleep Time |
5 |
This is an optional setting that defines how long the job is inactive in between a run being completed and another run starting. If you enter zero (o), the job does not rest in between runs and it runs continuously. |
Example Job Based on Daemon Framework
The job is started on the defined start date and time.
It runs for one hour (runtime) and stops itself after one hour.
During its runtime, the job executes a function in a continuous loop. This function could be, for example, searching for new deliveries in all inbound folders for all active delivery agreements.
During the job's runtime it goes to sleep for 5 minutes after each loop.
Every hour (period), a new job instance is created.
Note
Only one job instance can exist at a time. If an instance exists, but a new instance has to be created in the next period, a new instance will not be created until the current instance is completed.