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.  Broker - Lexical operator issue

    Posted Tue October 06, 2015 05:11 AM

    Hi All,

    I was unable to see subscription filter on the broker client even after setting lexical operator on the trigger.

    Condition set on trigger: %header/processName% L_EQUALS “XXX”
    doc structure: attached
    trigger processing is Concurrent

    but

    I have created another trigger with similar condition in my local folder …then will be able to see the subscription filter in broker client… condition: %Doc/Name% L_EQUALS “xxxx”

    both of these triggers created in same environment ( one is production trigger & another is created for testing)

    Can somebody please suggest why it is working for one and why not for other…please suggest


    #Universal-Messaging-Broker
    #broker
    #Integration-Server-and-ESB
    #webMethods


  • 2.  RE: Broker - Lexical operator issue

    Posted Tue October 06, 2015 01:01 PM

    Hello sreekanth,

    Could you Please try once by giving full qualified name of IS document in trigger.

    Thanks,
    Prem


    #Universal-Messaging-Broker
    #broker
    #Integration-Server-and-ESB
    #webMethods


  • 3.  RE: Broker - Lexical operator issue

    Posted Tue October 06, 2015 02:38 PM

    Hi Sreekanth,

    I agree with Prem.

    To do so, copy the doc type in package navigator and paste in the right location in the condition.

    Remember that the Input-Document of the triggered service must have the fully qualified name as well.
    Otherwise the document will not reach the service.

    Regards,
    Holger


    #broker
    #Universal-Messaging-Broker
    #webMethods
    #Integration-Server-and-ESB


  • 4.  RE: Broker - Lexical operator issue

    Posted Wed October 14, 2015 07:08 AM

    Thanks a lot for the inputs.

    field “processName” is not in synch with broker not sure how it is missed out but the issue is fixed after synch.

    Thanks again.

    -Sreekanth


    #Universal-Messaging-Broker
    #broker
    #webMethods
    #Integration-Server-and-ESB