Schedule a site-level job

Administer > Overview of administering a WebSphere Commerce site > Administration Console > Scheduler > Jobs

Schedule a site-level job

Overview

Use the Administration Console to schedule a job to run for the site.
The scheduler polls the SCHACTIVE table to find jobs scheduled to run. Based on the state of a job in the database, the scheduler on each node observes whether a job is running or needs to be executed. Therefore, only one scheduler runs that specific job at any time, and multiples do not run at the same time.

Procedure

Open the Administration Console and select Site on the Administration Console Site/Store Selection page.

Click...

Configuration | Scheduler | New

The Schedule Job window opens.

From the Job command list, select the type of job to run.
Although the ReleasetoFulfillment command displays in this list, it is not supported for site level jobs.

Complete the following fields:

Option Description
Job command Select the URL-based command to run.
Job parameters Parameters of the command to run in the format of a URL query string.
For example, if the scheduled command requires that you specify the order and contract ID, the URL query string representation to specify these parameters would be...

orderId=10023&contractId=1002

All special characters, such as &, =, /, and ?, must be encoded using standard HTML coding. If you use the form provided, the encoding will be done for you.
Start date
Start time Date and time this job should start running.
The time must be entered in the 24 hour clock format.
Associated user User on whose behalf this job is run.
By default, the user ID of the current user is entered in this field. The value of this field should be the same as the value in the LOGONID column of the USERREG database table.
Allowed host Name of the host that should run this job.
If this parameter is omitted, the job can be run by any host. This parameter is only needed if the scheduler is running on multiple hosts and if a job needs to be restricted to one of them. The host name should be in the form:

name.domain

Schedule interval Number of seconds between successive runs of this job. If this parameter is omitted, the job is run only once.
Job attempts
Seconds to retry Number of times the scheduler should retry the job if it fails and the number of seconds before a failed job is retried. Both field must be present to retry a job.
Scheduler policy Policy to be used by the scheduler when the job has failed to run.
Select whether the job is run only once and the next run is scheduled for the future, or whether the job is run as many times as necessary to recover all missed runs.
Job priority Priority of this job.
This value is inserted into the SCCPRIORITY column of the SCHCONFIG table. A greater number indicates a higher priority job.
Application type Select the application schedule pool that the job will be a part of.
The purpose of this field is to constrain resource-intensive jobs to a limited number of threads. The application types, and the rules governing their access to resources, are defined by the user under the WebSphere Administration Console. The default application type is null. See Scheduler configuration parameters for more information on how to add application types by creating a new work manager.

Click OK. Your job is now listed on the Scheduler Status Display page and will run at the specified start time.

From the Job command list, select the job, then complete these fields:

Recommended start time Enter in the 24 hour clock format.
Recommended interval (seconds)
Recommended priority

Click OK. The jobs are now listed on the Scheduler Status Display page and will run at the specified start time.

See also

Delete a scheduled job

Edit the configuration for a scheduled job

Remove job status records from the SCHSTATUS table

Schedule a broadcast job

Scheduled job states

View scheduled jobs

Configure the scheduler to run a job on an instance or cluster member

+
Search Tips | Advanced Search

Option	Description
Job command	Select the URL-based command to run.
Job parameters	Parameters of the command to run in the format of a URL query string. For example, if the scheduled command requires that you specify the order and contract ID, the URL query string representation to specify these parameters would be... orderId=10023&contractId=1002 All special characters, such as &, =, /, and ?, must be encoded using standard HTML coding. If you use the form provided, the encoding will be done for you.
Start date Start time	Date and time this job should start running. The time must be entered in the 24 hour clock format.
Associated user	User on whose behalf this job is run. By default, the user ID of the current user is entered in this field. The value of this field should be the same as the value in the LOGONID column of the USERREG database table.
Allowed host	Name of the host that should run this job. If this parameter is omitted, the job can be run by any host. This parameter is only needed if the scheduler is running on multiple hosts and if a job needs to be restricted to one of them. The host name should be in the form: name.domain
Schedule interval	Number of seconds between successive runs of this job. If this parameter is omitted, the job is run only once.
Job attempts Seconds to retry	Number of times the scheduler should retry the job if it fails and the number of seconds before a failed job is retried. Both field must be present to retry a job.
Scheduler policy	Policy to be used by the scheduler when the job has failed to run. Select whether the job is run only once and the next run is scheduled for the future, or whether the job is run as many times as necessary to recover all missed runs.
Job priority	Priority of this job. This value is inserted into the SCCPRIORITY column of the SCHCONFIG table. A greater number indicates a higher priority job.
Application type	Select the application schedule pool that the job will be a part of. The purpose of this field is to constrain resource-intensive jobs to a limited number of threads. The application types, and the rules governing their access to resources, are defined by the user under the WebSphere Administration Console. The default application type is null. See Scheduler configuration parameters for more information on how to add application types by creating a new work manager.