IBM Support

JR46225: AUGMENTING AN EXISTING WAS DEPLOYMENT MANAGER PROFILE WITH FEDERATED CUSTOM NODES FAILS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When augmenting a WAS deployment manager that already has one
    or more custom nodes federated to it with the BPM profile
    template, the command fails and the following is logged in
    
    <install_root>/logs/manageprofiles/<profileName>/dmgr.procctr.ws
    admin.log (or dmgr.procsvr.wsadmin.log):
    
    
    [2/25/13 21:34:30:415 EST] 00000000 AbstractShell E
    WASX7120E: Diagnostic information from exception with text
    "com.ibm.wbi.utils.configservice.WBIConfigException:
    com.ibm.wbi.utils.configservice.WBIConfigException:
    com.ibm.websphere.management.cmdframework.InvalidParameterValueE
    xception: ADMF0003E: Invalid parameter value null for parameter
    serverName for command setJVMInitialHeapSize.
    " follows:
    
    com.ibm.wbi.utils.configservice.WBIConfigException:
    com.ibm.websphere.management.cmdframework.InvalidParameterValueE
    xception: ADMF0003E: Invalid parameter value null for parameter
    serverName for command setJVMInitialHeapSize.
        at
    com.ibm.wbi.utils.configservice.WBIAdminCmdUtil.invokeAdminCmd(W
    BIAdminCmdUtil.java:167)
        at
    com.ibm.wbi.utils.configservice.WBIAdminCmdUtil.invokeAdminCmd(W
    BIAdminCmdUtil.java:39)
        at
    com.ibm.bpm.config.admintasks.CustomizeBPMServerConfigurationCom
    mand.setJVMInitialHeapSize(CustomizeBPMServerConfigurationComman
    d.java:274)
        at
    com.ibm.bpm.config.admintasks.CustomizeBPMServerConfigurationCom
    mand.configureServer(CustomizeBPMServerConfigurationCommand.java
    :156)
        at
    com.ibm.bpm.config.admintasks.CustomizeBPMServerConfigurationCom
    mand.execute(CustomizeBPMServerConfigurationCommand.java:89)
        at
    com.ibm.websphere.management.async.client.AsyncCommandClient.exe
    cute(AsyncCommandClient.java:177)
        at
    com.ibm.ws.scripting.adminCommand.AdminCmdController.executeCmd(
    AdminCmdController.java:1876)
        at
    com.ibm.ws.scripting.adminCommand.AdminCmdController.processCmd(
    AdminCmdController.java:317)
        at
    com.ibm.ws.scripting.adminCommand.AdminCmdProxyHandler.invoke(Ad
    minCmdProxyHandler.java:92)
        at
    com.ibm.ws.scripting.adminCommand.AdminCmdProxyBase.__method3(Ad
    minCmdProxyBase.java:53)
        at
    com.ibm.ws.scripting.adminCommand.AdminTask.customizeBPMServerCo
    nfiguration(Unknown Source)
    

Local fix

  • The tempororay work around is , if possible, unfederate/remove
    the existing custom nodes that are federated to the dmgr
    profile under consideration and then augment it using the
    desired BPM template.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Business Process Manager Version8.0         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Faild to augmenting a WAS deployment    *
    *                      manager                                 *
    ****************************************************************
    * RECOMMENDATION:  When augmenting a WAS deployment manager    *
    *                  that already has one or more custom nodes   *
    *                  federated to it with the BPM                *
    *                  profile template, augmentation fails.       *
    ****************************************************************
    The issue will be fixed in upcoming releases.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR46225

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    800

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-02

  • Closed date

    2013-07-10

  • Last modified date

    2013-07-10

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

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

Fix information

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
10 July 2013