IBM Support

JR56159: IBM PROCESS CENTER REPORTS INCONSISTENT IBM PROCESS PORTAL VERSION DEPLOYED ON IBM PROCESS SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • After you upgrade IBM Process Center to IBM Business Process
    Manager (BPM) V8.5.0.2 and creating an online IBM Process Server
    environment, Process Center shows that the V8.5.0.1 snapshot of
    Heritage Process Portal (TWP) is deployed on the V8.5.0.2
    process server. However, there is no V8.5.0.1 snapshot of
    Heritage Process Portal (TWP) deployed on the process server.
    Instead, the version should be the 8.5.0.2 snapshot of Heritage
    Process Portal (TWP).
    
    You see the same symptom in a Process Center that was upgraded
    from IBM BPM V8.5.6.x to IBM BPM 8.5.7.x.
    

Local fix

Problem summary

  • When the Process Portal snapshot was updated, its resource
    bundle group snapshot was not updated accordingly. Instead, it
    remained on the previous version, causing the inconsistency.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR56159

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    850

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-20

  • Closed date

    2017-01-17

  • Last modified date

    2017-01-17

  • 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

  • R850 PSY

       UP

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

Document Information

Modified date:
17 January 2017