IBM Support

JR56484: YOU RECEIVE THE CWMCB0046E ERROR WHEN YOU AUGMENT AN IBM WEBSPHERE APPLICATION SERVER DMGR PROFILE WITH IBM BPM

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When you create an IBM WebSphere Application Server profile and
    change the default WebSphere VMM user registry to a stand-alone
    LDAP user registry, augmenting the WebSphere Application Server
    profile with IBM Business Process Manager (BPM), you get the
    following error in the
    logs/manageprofiles/<profileName>_augment.log file:
    
    com.ibm.bpm.config.util.ConfigException: CWMCB0046E: The
    'setAdminActiveSecuritySettings' command failed: null
     at
    com.ibm.bpm.config.util.ConfigHelper.invokeAdminCommand(ConfigHe
    lper.java:2475)
     at
    com.ibm.bpm.config.util.ConfigHelper.invokeAdminCommand(ConfigHe
    lper.java:1993)
     at
    com.ibm.bpm.config.profile.impl.SecurityHelper.configureSecurity
    (SecurityHelper.java:141)
     at
    com.ibm.bpm.config.profile.impl.ProfileBpmDmgr.configureProfile(
    ProfileBpmDmgr.java:96)
     at
    com.ibm.bpm.config.profile.ProfileFactory.main(ProfileFactory.ja
    va:90)
    :
    Caused by: java.lang.NullPointerException
     at
    com.ibm.ws.security.admintask.securityDomain.SecConfigTaskHelper
    .isGoodServerId(SecConfigTaskHelper.java:335)
     at
    com.ibm.ws.security.admintask.securityDomain.SecConfigTaskHelper
    .authenticateUser(SecConfigTaskHelper.java:255)
     at
    com.ibm.ws.security.admintask.securityDomain.SecConfigTaskHelper
    .isRegGood(SecConfigTaskHelper.java:625)
     at
    com.ibm.ws.security.admintask.securityDomain.SecConfigTaskHelper
    .isRegistryGood(SecConfigTaskHelper.java:564)
     at
    com.ibm.ws.security.admintask.securityDomain.SecurityConfigProvi
    derHelper.validateRegistryObject(SecurityConfigProviderHelper.ja
    va:109)
     at
    com.ibm.ws.security.admintask.securityDomain.SecurityConfigProvi
    der.setAdminActiveSecuritySettings(SecurityConfigProvider.java:2
    425)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:95)
     at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:56)
     at java.lang.reflect.Method.invoke(Method.java:620)
     at
    com.ibm.websphere.management.cmdframework.provider.SimpleCommand
    Provider.executeReal(SimpleCommandProvider.java:156)
     at
    com.ibm.websphere.management.cmdframework.provider.SimpleCommand
    Provider.execute(SimpleCommandProvider.java:142)
     at
    com.ibm.websphere.management.cmdframework.provider.SimpleAdminCo
    mmand.execute(SimpleAdminCommand.java:57)
     at
    com.ibm.bpm.config.util.ConfigHelper.invokeAdminCommand(ConfigHe
    lper.java:2421)
     ... 55 more
    
    
    PRODUCTS AFFECTED
    IBM BPM Advanced
    IBM BPM Standard
    IBM BPM Express
    

Local fix

  • To work around this, switch the user registry to stand-alone
    LDAP only after the profile has been augmented with BPM
    

Problem summary

  • As documented in "Augmenting deployment manager profiles using
    the manageprofiles command-line utility"
    (https://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.6/com.ib
    m.wbpm.imuc.ebpm.doc/topics/mp_dm_aug_lin_orcl.html), augmenting
     the IBM BPM profile requires the default WebSphere VMM user
    registry to be configured. However, the IBM BPM profile
    augmentation code does not check the user registry type, which
    results in a NullPointerException if the default WebSphere VMM
    user registry is not configured.
    
    A fix that adds a check to the IBM BPM profile augmentation will
     be included in IBM BPM V8.5.7 cumulative fix 2016.09. With this
     fix installed, you will see a more explanatory error message
    when trying to augment a WebSphere Application Server profile
    with IBM BPM when the default WebSphere VMM user registry was
    changed to something else.
    
    To determine whether the cumulative fix is available and
    download it if it is, complete the following steps on Fix
    Central:
    
    1. On the Select product tab, select WebSphere as the product
    group, IBM Business Process Manager with your edition from the
    WebSphere options, All as the installed version, and All as the
    platform, and then click Continue.
    2. In the Text field, enter "cumulative fix?, and click
    Continue.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR56484

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    856

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-12

  • Closed date

    2016-09-06

  • Last modified date

    2016-09-06

  • 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

  • R856 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":"856","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
06 September 2016