Tuning Websphere Commerce Schedulers

As of WCS 7, fix pack 2, we have few additional options to fine tune the scheduler jobs.

you can define a custom transaction timeout for scheduler Jobs which will be independent of your WAS level setting for global transaction timeout.

a. Disabling Scheduler in WCS instance

follow these steps If you have a need to not run any scheduler jobs from a given WCS instance,

Edit the wc-server.xml file of a given instance and edit the value enabled=false, this configuration will disable scheduler jobs from running on this instance.

 It is important to note that by doing this you are disabling the ability of this JVM to run any Broadcast event Jobs as well.

        <component

            compClassName="com.ibm.commerce.scheduler.SchedulerComm"

            enable="false" name="Scheduler">

            <property autoClean="off" broadcastExpireTime="1800"

                contextSetName="Authoring" cycleTime="600" display="false"/>

        </component>

b. Defining transaction timeout for Scheduler Jobs

Here are the steps which is part of APAR IZ02770, which explains how to specify the         

scheduler-specific transaction timeout settings:                       

                                                                        

Update the WC_installdir/instances/instanceName/xml/instanceName.xml

to include the new transactionTimeout field. Set the value in seconds  

for your desired transaction timeout for scheduled jobs                

                                                                       

<component                                                             

compClassName="com.ibm.commerce.scheduler.SchedulerComm"               

enable="true" name="Scheduler">                                         

<property autoClean="off"                                              

broadcastExpireTime="1800"                                             

transactionTimeout="1800"                                               

contextSetName="Authoring"                                             

cycleTime="600"                                                        

display="false">                                                       

</property>                                                             

</component>                                                           

                                                                       

Restart the application and test your scenario

2. Defining dedicated Container threads for Jobs

This setting might be useful if you are using WCS JVM to serve external traffic and also run some of the Scheduler jobs, the configuration defines maximum threads for various Jobs.

<component                                                             

compClassName="com.ibm.commerce.scheduler.SchedulerComm"               

enable="true" name="Scheduler">                                         

<property autoClean="off"                                              

broadcastExpireTime="1800"                                             

transactionTimeout="1800"                                              

contextSetName="Authoring"                                             

cycleTime="600"                                                        

display="false"> 

<applicationType applicationName="default" maxNumofThreads="10"/>      

<applicationType applicationName="broadcast" maxNumofThreads="10"/>    

<applicationType applicationName="auction" maxNumofThreads="10"/>      

<applicationType applicationName="inventory" maxNumofThreads="10"/>    

</property>                                                             

</component>

Refer following link for more details

http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/topic/com.ibm.commerce.admin.doc/concepts/cjsconfig.htm

 

More Reading

Maintaining Scheduler
http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/index.jsp?topic=/com.ibm.commerce.admin.doc/tasks/tjsmaint.htm

Websphere Commerce Scheduler Mustgather 
https://www-304.ibm.com/support/docview.wss?uid=swg21454411

Use following trace component for troubleshooting and scheduler related issues.
*=info: enable.trace.log.*=all: com.ibm.websphere.commerce.WC_THREAD=all: com.ibm.websphere.commerce.WC_SERVER=all

Maintaining the WebSphere Commerce Scheduler tables
https://www-304.ibm.com/support/docview.wss?uid=swg21397348