Running Business Processes and Composite Applications 10.4 | Running Business Processes and Composite Applications | webMethods Integration Server Administrator’s Guide | Scheduling Services | Scheduling a User Task
 
Scheduling a User Task
Use the following procedure to schedule a user task.
* To schedule a user task
1. Open the Integration Server Administrator if it is not already open.
2. In the Server menu of the Navigation panel, click Scheduler.
3. Click Create a Scheduled Task.
4. Set the Service Information parameters as follows:
For this parameter
Specify
Description
A description of the task.
folder.subfolder:service
The fully qualified service name of the service you want Integration Server to execute.
Click Assign Inputs to enter new input values or modify existing values for the service you want Integration Server to execute.
Before assigning input values, note that:
*You can only assign values for top-level input parameters of data type String.
*Assigning input values using Assign Inputs overwrites any input values assigned to a service using the built-in services in thepub.schedulerfolder.
For information about specifying service names, see Fully Qualified Service Names.
Run As User
The user name you want the server to use when running the service. Click search icon to search for and select your user. A user can be selected from the local or central directory.
Integration Server runs the service as if the user you specify is the authenticated user that invoked the service. If the service is governed by an ACL, be sure to specify a user that is allowed to invoke the service.
Target Node
Whether you want the task to run on other Integration Servers connected to the same database:
*Select Any server if the task needs to run on only one server connected to the database, and it does not matter which one.
*For clustered servers only. Select All servers if the task needs to run on all Integration Servers in the cluster.
*Select the name from the list of Integration Servers connected to the database if the task needs to run on only a specific server.
The default is the current Integration Server.
For more information about the Target Node options, see Target Node Options.
5. Select an action to perform If the Task Is Overdue.
This parameter
Specifies that Integration Server should
Run immediately
Run the task immediately, no matter how late the task is.
Skip and run at next scheduled time
Skip this execution of the task, and run it again at the next scheduled run time. This option is not available for tasks that run just once.
Suspend
Place the task in a suspended state until an administrator resumes or cancels the task.
Integration Server periodically checks the status of scheduled tasks. If it finds a task that should have started but has not, Integration Server runs the task immediately, unless you have specified a special action to take for late tasks. Integration Server performs this "late action" if the task has missed its scheduled start time by a number of minutes you specify in the if more than xxx minutes late field.
Note: The maximum number of minutes that the if more than xxx minutes late field can accept is 35000.
For tasks that are late but do not exceed the specified period, Integration Server runs the task immediately.
6. Select Run Once, Repeating, or Complex Repeating to indicate when and how often you want Integration Server to execute the service.
Select
To
Run Once
Schedule a task to run just once. Specify the following:
*Date. The date on which you want Integration Server to execute the service.
Enter the date using the format YYYY/MM/DD. For example, if you want the server to execute the service on March 11, 2010, specify 2010/03/11.
*Time. The time at which you want Integration Server to execute the service.
Enter the time using the format HH:MM:SS (using a 24-hour clock). For example, if you want Integration Server to execute the service at 1:00:00 a.m., specify 1:00:00; if you want Integration Server to execute the service at 1:00:00 p.m., specify 13:00:00.
Repeating
Schedule simple repeating tasks, for example once a day at a specific time. Specify the following
*Start Date and Start Time. The date and time of the first execution.
For Start Date, use the format YYYY/MM/DD. For Start Time, use the format HH:MM:SS (using a 24-hour clock).
For example, if you want the service executions to start on May 3, 2010 at 1:00:00 p.m., specify 2010/05/03 for Start Date and 13:00:00 for Start Time.
*End Date and End Time. The date and time of the last execution.
For End Date, use the format YYYY/MM/DD. For the End Time, use the format HH:MM:SS (using a 24-hour clock).
For example, if you want the service executions to stop on June 4, 2010 at 2:00:00 a.m., specify 2010/06/04 for End Date and 02:00:00 for End Time. Omitting End Date indicates that you want this service to execute for an indefinite period of time. If you omit End Time, Integration Server uses the current time.
*Interval. Execution interval.
Enter the number of seconds that you want Integration Server to wait between executions of the service.
*Repeat after completion. Whether to wait for the previous execution of the 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, Integration 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.
For more information about using the Repeating option, see Simple Repeating Option.
Complex Repeating
Schedule a task that repeats at a more complex interval, for example, every other day, or twice a month. Specify the following:
*Start Date and Start Time. The date and time of the first execution.
For Start Date, use the format YYYY/MM/DD. For Start Time, use the format HH:MM:SS (using a 24-hour clock).
For example, if you want the service executions to start on May 3, 2010 at 1:00:00 p.m., specify 2010/05/03 for Start Date and 13:00:00 for Start Time. If you omit the Start Date, the first execution occurs on the first date as indicated by the Run Mask parameters. If you omit Start Time, the server uses the current time.
*End Date and End Time. The date and time of the last execution.
For End Date, use the format YYYY/MM/DD. For the End Time, use the format HH:MM:SS (using a 24-hour clock).
For example, if you want the service executions to stop on June 4, 2010 at 2:00:00 a.m., specify 2010/06/04 for End Date and 02:00:00 for End Time. Omitting End Date indicates that you want this service to execute for an indefinite period of time. If you omit End Time, the server uses the current time.
*Run Mask. Specific months, dates (1-31), days of the week (Sunday-Monday), hours, minutes, and seconds when you want a task to run. You can select one or more items from each category. To select multiple items, press the Ctrl key while making your selections. If you do not select any items from a category, Integration Server assumes all items for the selection.
*Repeat after completion. Whether to 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, Integration Server will start the next execution even though the previous one has not yet completed.
If you check the Repeat after completion box, the 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 running are delayed.
For more information about using the Complex Repeating options see Complex Repeating Option.
Note: Integration Server does not skip or repeat the scheduled tasks because of transitions to and from Daylight Saving Time. For more information about how Integration Server handles transitioning to and from Daylight Saving Time, see How Transitioning to or from Daylight Savings Time Affects Scheduled Tasks.
7. Click Save Tasks.
Copyright © 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release