webMethods

webMethods

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
Expand all | Collapse all

Issue in EXIT flow step

  • 1.  Issue in EXIT flow step

    Posted Mon June 20, 2016 08:28 AM

    Hi all,

    There is an issue in try/catch implementation.

    I have configured the EXIT step as below in try block.

    EXIT from - $parent

    Signal - Failure

    Failure Message - Error occurred.

    But in catch block, i could not get the error by using get last error. The LastError doc is missing.

    Can anyone suggest on this.

    Regards,
    Jacob B
    EXIT issue.PNG


    #Integration-Server-and-ESB
    #webMethods


  • 2.  RE: Issue in EXIT flow step

    Posted Mon June 20, 2016 08:31 AM

    Hi Jacob,

    please share the “Exit on” settings for the different sequences.
    Might be that on of them has a wrong the setting for the Try/Catch-Senario.

    Regards,
    Holger


    #webMethods
    #Integration-Server-and-ESB


  • 3.  RE: Issue in EXIT flow step

    Posted Mon June 20, 2016 08:47 AM

    Hi Holger,

    Below are the EXIT ON details.

    Seq (main) - Success
    (try) - failure
    (catch) - done

    Regards,
    Jacob B


    #Integration-Server-and-ESB
    #webMethods


  • 4.  RE: Issue in EXIT flow step

    Posted Mon June 20, 2016 09:09 AM

    Use Exit on flow or Exit on loop instead of parent…

    Exit on parent works little different, and you need to understand… If you use it inside the loop, it will work like, skip the current execution and continue with the next record in the loop.

    -Senthil


    #webMethods
    #Integration-Server-and-ESB


  • 5.  RE: Issue in EXIT flow step

    Posted Mon June 20, 2016 09:24 AM

    Hi Senthil,

    Thanks for the details. Below is my understanding of code.

    Seq - (Exit on success)
    Seq - ( Try - Exit on Failure)
    MAP
    Exit $parent and signal FAILURE (Error message)
    MAP
    Seq - (Catch - Exit on Done)
    getLastError

    So, when the control passes from Exit $ parent step, it should be coming to Catch block with the error details. Bu the IS is not considering it as an error and LastError doc is not present in pipeline.

    Can you explain this behaviour?

    Regards,
    Jacob B


    #Integration-Server-and-ESB
    #webMethods


  • 6.  RE: Issue in EXIT flow step

    Posted Mon June 20, 2016 09:33 AM

    Jacob,

    Instead of
    Exit $parent and signal FAILURE (Error message)

    Set it as
    Exit $flow and signal FAILURE (Error message)

    You will see the way it works as expected by you.

    -Senthil


    #webMethods
    #Integration-Server-and-ESB


  • 7.  RE: Issue in EXIT flow step

    Posted Mon June 20, 2016 09:40 AM

    Senthil,

    Yes, EXIT $flow works. I just want to analyse when exactly EXIT $parent to be used.

    Below is my observation.

    Only when you want exit from a flow step without exception.

    Also, getLastError will not catch the user defined exceptions in same flow service.

    Regards,
    Jacob B


    #webMethods
    #Integration-Server-and-ESB


  • 8.  RE: Issue in EXIT flow step

    Posted Mon June 20, 2016 10:01 AM

    Jacob,
    I will send you a working sample tomorrow when I get online again.

    -Senthil


    #webMethods
    #Integration-Server-and-ESB


  • 9.  RE: Issue in EXIT flow step

    Posted Tue June 21, 2016 09:02 AM

    Hello Senthil,

    Also, I observed that the “Timeout” property in flow step is not working as expected.

    Can you share some working sample for timeout property in the flow steps please.

    Regards,
    Jacob B


    #webMethods
    #Integration-Server-and-ESB


  • 10.  RE: Issue in EXIT flow step

    Posted Tue February 28, 2017 04:49 AM

    Hi guys, Im Kevin

    I Also, Have doubted about what exactly going on
    when I observed EXIT flow service with $parent. option.

    look forward to get it clear, help me ~


    #Integration-Server-and-ESB
    #webMethods