IBM Support

JR55412: BPMMANAGEAPPLICATIONS FAILS WITH CANNOT FIND PROFILE IF PROFILEREGISTRY.XML IS NOT LOCATED AT DEFAULT LOCATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Running the BPMManageApplications script with the
    profileRegistry.xml not located in the default location causes
    the following error:
    $ ./BPMManageApplications.sh -autoStart false -source
    -propertiesFile
    /optware/wascfg/migration/migration.properties
    CWMCO1036I: BPM migration logs are saved under
    /opt/WAS/v85bpm/ESUITE/logs/migration.
    CWMCO1039E: Failed to detect if current source environment is
    augmented
    with IBM Business Monitor with exception:
    com.ibm.wsspi.profile.WSProfileException: Cannot find the
    bamwps_dmgr01
    profile.
    The default location of the profileRegistry.xml file can be
    customized,
    Customer porfileRegistry.xml file is not located under
    <WASROOT>/properties directory
    It is located at a custom location defined in the
    <WASROOT>/properties/wasprofile.properties  file
    #---------------------------------------------------------------
    --------
    --
    # The profile registry property determines the path to the XML
    file that
    # contains information about all registered profiles.
    #
    # The default path for this file is:
    # <install location>/properties/profileRegistry.xml
    #---------------------------------------------------------------
    --------
    --
    WS_PROFILE_REGISTRY=${was.install.root}/properties/profileRegist
    ry.xml
    

Local fix

  • &#216;
    Use default location for profileRegistry.xml.
    

Problem summary

  • Fixed in BPM857CF
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR55412

  • 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-02-27

  • Closed date

    2016-04-15

  • Last modified date

    2016-04-15

  • 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:
15 April 2016