For workload or debugging purpose, you might want to use
specific servers for scheduled quick publish jobs. You can configure
the WebSphere Commerce scheduler to run quick publish jobs on the
specific WebSphere Commerce instances or cluster members that you
define.
About this task
To isolate a scheduled job to a particular instance or cluster
member:
- Modify the Application Servers using the WebSphere Commerce instance
to give the scheduler a unique identifier.
- Modify the content management resource container file and add
the unique identifier into the quick publish configuration section.
Procedure
- Uniquely identify the server process where
you want the quick publish task to run.
Follow the steps
that are provided in
Configuring the scheduler to run a job on an instance or cluster member.
To
uniquely identify each server process that runs WebSphere Commerce,
you must enter the following JVM parameter in the
Name field:
com.ibm.commerce.scheduler.SchedulerHostName
and provide a value for the parameter in the
Value field.
Make note of value that you specify; you need to use the same value
for the
jvmName
parameter in
Step 2.
- Update the value of the quick publish JVM
name attribute in the wc-resource-containers.xml file.
- Open the WC_profiledir\installedApps\cell_name\WCServer_enterprise_archive\xml\content-management\wc-resource-containers.xml file
for editing.
- Locate the
<wc:QuickPublishConfiguration>
element,
and add the jvmName
parameter
as shown:<wc:QuickPublishConfiguration>
<wc:Publisher className="com.ibm.commerce.context.content.resources.publish.DefaultJDBCContentPublisherImpl"
initParameters=[other-parameters] jvmName="QPHostname" [other-parameters]/ >
</wc:QuickPublishConfiguration>
The value of the
jvmName
parameter
must match the value that you specified for the
com.ibm.commerce.scheduler.SchedulerHostName
parameter
in
Step 1.