IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Different in BPM status Failed & Failed(Escalated)

    Posted Wed January 16, 2019 02:03 AM

    Hi All,

    We are using wm 9.7 version where we can observe in one environment whenever BPM get failed status is changing to Failed(Escalated) whereas in other server it is Failed. What is the possible reason for status getting changed to Failed(Escalated) because once it get Failed(Escalated) no longer we can re-submit the process any more.

    Thanks!


    #BPM
    #webMethods
    #webMethods-BPMS


  • 2.  RE: Different in BPM status Failed & Failed(Escalated)

    Posted Wed January 16, 2019 04:09 AM

    There has been a change in WmPRT from 9.10 version if I remember correctly and I have faced these issues.

    Use pub.prt.admin:changeProcessStatus to change status and refer BPM_Process_Development_Help.pdf and Monitor_Users_Guide.pdf

    Also in the past, there was a KB article published on the same, have a look at the Empower.


    #BPM
    #webMethods-BPMS
    #webMethods


  • 3.  RE: Different in BPM status Failed & Failed(Escalated)



  • 4.  RE: Different in BPM status Failed & Failed(Escalated)

    Posted Wed January 16, 2019 07:20 AM

    Thanks for posting the link!

    I think due to BPM design change it will have an impact on BPM upgrades which results in an additional task, do you know if this is handled by the migration script?


    #webMethods-BPMS
    #webMethods
    #BPM