Scheduling a site-level job

Use the Administration Console to schedule a job on the site level.

About this task

You can configure the Administration Console to schedule a job for all of your stores. The job scheduler runs everything that is in the scope for the site. Any controller commands that are disclosed to the site administrator can be scheduled as a site-level scheduler job.

Procedure

  1. Open the Administration Console, and select Site on the Administration Console Site/Store Selection page.
  2. Click Configuration > Scheduler. A list of jobs that are scheduled to run is displayed.
  3. Click New. The Schedule Job window opens.
  4. From the Job command list, select the type of job you want to run.
    Note: Although the ReleasetoFulfillment command displays in this list, it is not supported for site level jobs.
  5. Complete the following fields:
    OptionDescription
    Job command Select the URL-based command that you want to run.
    Job parameters Type the parameters of the command you want 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 by using standard HTML coding. If you use the form that is provided, the encoding is done for you.
    WebSphere Commerce Version 7.0.0.8 or laterThe parameter maxThreads can be used to limit the number threads that are used by a job. There is not a default value for this parameter. If the maxThreads parameter is not configured, it is treated as 0 and there is no restriction. This property can be applied to any job type. For example, maxThreads=1 limits a job to use a single thread. If your site is clustered and you use this parameter, you are restricting the number of threads for a job across the entire cluster, not just within a single JVM.
    Note: When a job cannot start because the maxThreads limit is reached, the status for the job that cannot start is set as CF in the SCHSTATUS database table. This status means that the job is finished running, but that it failed to run successfully. No further processing occurs for the job. The following exception is also recorded for the job in the SCHERRORLOG database table:
    "Running instances exceed configured maxThreads:"+maxThreads+". This attempt is canceled." 
    If you want to restore the previous behavior, you can set the maxThreads parameter to a value less than or equal to 0. Alternatively, you can update the scheduler to remove the parameter.
    Start date and Start time Provide the date and time this job starts running. The time must be entered in the 24-hour clock format.
    Associated user Type the user on whose behalf this job is run. By default, the user ID of the current user is entered in this field. Set the value of this field to be the same as the value in the LOGONID column of the USERREG database table.
    Allowed host Type the name of the host that runs 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 must be restricted to one of them. Use the following form to specify the host name: name.domain.
    Schedule interval Type the number of seconds between successive runs of this job. If this parameter is omitted, the job is run only 1 time.

    WebSphere Commerce Version 7.0.0.9Apply APAR JR53939 to run the job scheduler daily at a fixed time. Click the Fixed Time check box, and leave the Schedule interval field blank. Enabling Fixed Time ensures a job runs at a specified time, even with Daylight Saving Time changes.

    Job attempts and Seconds to retry Type the number of times the scheduler is to 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 Specify the policy to be used by the scheduler when the job fails to run. Select whether the job is run one time and the next run is occurs in the future, or whether the job runs as many times as necessary to recover all missed runs.
    Job priority Type a number to be associated with the 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 is 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 that govern their access to resources, are defined by the user under the WebSphere Commerce Administration Console. The default application type is null.
  6. Click OK. Your job is now listed on the Scheduler Status Display page and runs at the specified start time.