Schedule a site-level job

Schedule a site-level job

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

About this task
We can configure the Administration Console to schedule a job for all of the 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
Open the Administration Console, and select Site on the Administration Console Site/Store Selection page.
Click Configuration > Scheduler. A list of jobs that are scheduled to run is displayed.
Click New. The Schedule Job window opens.
From the Job command list, select the type of job we want to run.
Note: 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
Type the parameters of the command we 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.The parameter maxThreads can be used to limit the number threads 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.
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." 
To restore the previous behavior, we can set the maxThreads parameter to a value less than or equal to 0. Alternatively, we 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.
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.
Click OK. Your job is now listed on the Scheduler Status Display page and runs at the specified start time.
Deleting a scheduled job
Use the Administration Console to delete a scheduled job and stop it from running for the site.
Editing the configuration for a scheduled job
Use the Administration Console to edit the configuration for a scheduled job.
Removing job status records from the SCHSTATUS table
Use the Administration Console to remove job status records from the SCHSTATUS table.
Scheduling a broadcast job
Use the Administration Console to schedule a broadcast job to run for the site.
Scheduled job states
The SCHACTIVE table contains the list of jobs that are scheduled to run, and the execution time for each scheduled job. The execution history for each scheduled job is kept in the SCHSTATUS table.
Viewing scheduled jobs
Use the Administration Console to view a list of jobs scheduled to run for the site.
Configure the scheduler to run a job on an instance or cluster member
We can configure the WebSphere Commerce scheduler to run a job on a particular WebSphere Commerce instance or cluster member. This can be useful to devote one server for scheduled jobs.
Setting up the scheduler to process subscriptions and recurring orders
The SubscriptionSchedulerCmd job processes subscriptions and recurring orders. In this task you create a new job to monitor all active subscriptions and recurring orders to process their child orders on an hourly basis.

Related concepts
Jobs

Option	Description
Job command	Select the URL-based command to run.
Job parameters	Type the parameters of the command we 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.The parameter maxThreads can be used to limit the number threads 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. 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." To restore the previous behavior, we can set the maxThreads parameter to a value less than or equal to 0. Alternatively, we 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. 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.