Configuring the scheduler to run a job on an instance or cluster member
You can configure the HCL Commerce scheduler to run a job on a particular HCL Commerce instance or cluster member. This can be useful if you want to devote one server for scheduled jobs.
About this task
- Modify the Application Servers running the HCL Commerce instance to give the scheduler a unique identifier.
- Create or update a scheduled job to run on a unique HCL Commerce instance.
To uniquely identify each server process running HCL Commerce, the following
JVM parameter is required:
com.ibm.commerce.scheduler.SchedulerHostName
The value should be unique across all servers running your HCL Commerce instance. This will allow you to created a scheduled job that runs on a particular server in your cluster. A recommended value would be: node name. server name. This will be unique across your Cell.
This value can be specified using the WebSphere Application Server Administrative Console and specifying this system property in the JVM settings of the HCL Commerce application:
To create a job to run on a particular host, when calling the AddJob command to create the new schedule job, specify the host parameter and use the value that uniquely identifies the scheduler process that should execute the scheduled job.
If you want to manually change an existing job, update the SCCHOST column in the SCHCONFIG table for the job you want to run on a particular instance. When changing the SCCHOST column, ensure that the value is specified in lowercase characters. Because of performance reasons, the scheduler assumes that the host parameter will be specified in lowercase. The AddJob command makes the host value lowercase automatically but there is nothing in place at the database to maintain this restriction.