IBM Support

JR45484: CMVC 225708 - No way to isolate the quick publish scheduler job to run on a particular Commerce instance or cluster member.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For workload or debugging purposes, you might want to use
    specific servers for scheduled quick publish jobs.
    

Local fix

Problem summary

  • USERS AFFECTED:
    Websphere Commerce users on v7.0 who use the workspace function
    and want to isolate the quick publish scheduler job on a
    particular instance or cluster member.
    
    PROBLEM ABSTRACT:
    There is no way to isolate the quick publish scheduler job to
    run on a particular WebSphere Commerce instance or cluster
    member.
    
    BUSINESS IMPACT:
    Improve the management of workload or for debugging purposes
    
    RECOMMENDATION:
    

Problem conclusion

  • This ifix will enable the configuration of the WebSphere
    Commerce scheduler to run quick publish jobs on specific
    WebSphere Commerce instances or cluster members that you define.
    
    A code enhancement has been added in this ifix for configuring
    the Websphere Commerce scheduler to run quick publish jobs on a
    specific WebSphere Commerce instance or cluster member. After
    applying the ifix you will need to follow this procedure in
    order to use this function:
    
    1. Uniquely identify the server process where you want the quick
    publish task to run. Follow the steps that are provided in
    Information Center  topic "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.
    
    2. Update the value of the quick publish JVM name attribute in
    the wc-resource-containers.xml file.
    a.Open the
    WC_profiledir\installedApps\cell_name\WCServer_enterprise_archiv
    e\xml\content-management\wc-resource-containers.xml file for
    editing.
    b.Locate the <wc:QuickPublishConfiguration> element, and add the
    jvmName parameter as shown:
    <wc:QuickPublishConfiguration>
                  <wc:Publisher
    className="com.ibm.commerce.context.content.resources.publish.De
    faultJDBCContentPublisherImpl"
                  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 in Step 1.
    -------------------------------------------------------------
    The latest available maintenance information can be obtained
    from the Recommended Fixes for WebSphere Commerce technote:
    http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR45484

  • Reported component name

    WC BUS EDITION

  • Reported component ID

    5724I3800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-22

  • Closed date

    2013-06-16

  • Last modified date

    2013-06-24

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WC BUS EDITION

  • Fixed component ID

    5724I3800

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSYL","label":"WebSphere Commerce Enterprise"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
24 June 2013