The date on which you want the server to execute the service for the first time. Use the format YYYY/MM/DD to specify the date. If you leave this field blank, the server starts the task on the current day

The time at which you want the server to begin executing the service. Use the format HH:MM:SS to specify the time (using a 24-hour clock). If you leave this field blank, the server starts the task immediately.

The date on which you want the server to execute the service for the last time. Use the format YYYY/MM/DD to specify the date. If you leave this field blank, the server executes the service for an indefinite period of time or until you cancel the scheduled user task.

The time on the last date at which you want the server to execute the service. Use the format HH:MM:SS to specify the time (using a 24-hour clock). If you leave this field blank, the server uses the current time.

Whether Integration Server should wait for the previous execution of a service to complete before starting the next.

For example, suppose the GetData service is scheduled to run every minute, but sometimes takes longer than that to complete. By default, the server will start the next execution even though the previous one has not yet completed. If you check the Repeat after completion box, Integration Server will wait for the service to complete before running the next execution of the service. Executions that could not run while the service was executing are delayed.

Time interval, in seconds, at which you want the service to execute. For example, if you want the server to execute the service every 24 hours, specify 86400 seconds for the interval.

Every hour on July 1st in the year 2010.

Start Date

2010/07/01

Start Time

00:00:00

End Date

2010/07/01

End Time

00:00:00

Interval

3600