Configure quick publish to run on specific instances or cluster members

For workload or debugging purpose, we can use specific servers for scheduled quick publish jobs. We can configure the WebSphere Commerce scheduler to run quick publish jobs on the specific WebSphere Commerce instances or cluster members that we define.

Task info

To isolate a scheduled job to an instance or cluster member:

• Change the application servers that use the WebSphere Commerce instance to give the scheduler a unique identifier.

• Change the content management resource container file and add the unique identifier into the quick publish configuration section.

Procedure

1. Change the configuration files below before building the application package with the WebSphere Commerce Build tool.

2. Uniquely identify the server process where we want the quick publish task to run.

   Option	Description
   Name	com.ibm.commerce.scheduler.SchedulerHostName
   Value	Make note of the value that specified. Use the same value for the jvmName parameter.

3. Update the value of the quick publish JVM name attribute in the wc-resource-containers.xml file.

   1. Edit...

      WC_profiledir\installedApps\cell_name\WCServer_enterprise_archive\xml\content-management\wc-resource-containers.xml

   2. 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 specified for the com.ibm.commerce.scheduler.SchedulerHostName parameter

Related tasks
Updating the quick publish target