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.  Trigger condition is not updated at broker level

    Posted Tue July 26, 2016 09:50 AM

    Hi Guys,

    I made few changes to a trigger condition and trying to test it.

    New trigger condition present in integration trigger level.

    ((%PO_CANONICAL/PO_LINE_INFO/PO_LINE[0]/REQUISITION_ID% == /MAXPN/ || %PO_CANONICAL/PO_LINE_INFO/PO_LINE[0]/REQUISITION_ID% == /MAXBA/ || %PO_CANONICAL/PO_LINE_INFO/PO_LINE[0]/REQUISITION_ID% == /MAXGR/ || %PO_CANONICAL/PO_LINE_INFO/PO_LINE[0]/REQUISITION_ID% == /MAXSC/ || %PO_CANONICAL/PO_LINE_INFO/PO_LINE/PO_LINE[0]/DISTRIBUTION_INFO/DISTRIBUTION/DISTRIBUTION[0]/DELIVER_TO_LOCATION_CODE% == /FLUS059/) && ((%PO_CANONICAL/TARGET_SYSTEM% L_EQUALS ‘GEPW-PGP-US’) || (%PO_CANONICAL/TARGET_SYSTEM% L_EQUALS ‘GEPW-WIND-US’)) && (%PO_CANONICAL/SOURCE_SYSTEM% = ‘SSP5R12’)) || ((%PO_CANONICAL/TARGET_SYSTEM% L_EQUALS ‘GEPW-PGP-US’) && (%PO_CANONICAL/SOURCE_SYSTEM% L_EQUALS ‘SSP5R12’))

    where as at the mws client level I could see this, ((((regexpMatch(PO_CANONICAL.PO_LINE_INFO.PO_LINE[0].REQUISITION_ID,“MAXPN”) || regexpMatch(PO_CANONICAL.PO_LINE_INFO.PO_LINE[0].REQUISITION_ID,“MAXBA”)) || regexpMatch(PO_CANONICAL.PO_LINE_INFO.PO_LINE[0].REQUISITION_ID,“MAXGR”)) || regexpMatch(PO_CANONICAL.PO_LINE_INFO.PO_LINE[0].REQUISITION_ID,“MAXSC”)) && ((PO_CANONICAL.TARGET_SYSTEM == “GEPW-PGP-US”) || (PO_CANONICAL.TARGET_SYSTEM == “GEPW-WIND-US”)))

    Can any one let me know how can we fix this, get the correct trigger condition in sync at mws level too.

    Thanks all.

    Regards,
    Sandeep


    #Integration-Server-and-ESB
    #webMethods
    #webMethods-General


  • 2.  RE: Trigger condition is not updated at broker level

    Posted Tue July 26, 2016 10:33 AM

    You can try the below options:

    1> Disable/Enable the trigger in trigger properties, check if the filter condition on broker via MWS gets updated
    2> Remove the filter condition from tigger save it and then add the condition and save it again.
    3> Delete and re-create the trigger manually


    #webMethods-General
    #webMethods
    #Integration-Server-and-ESB


  • 3.  RE: Trigger condition is not updated at broker level

    Posted Tue July 26, 2016 10:41 AM


  • 4.  RE: Trigger condition is not updated at broker level

    Posted Tue July 26, 2016 12:46 PM

    Recreating the trigger must it. Can you again share the client screen from MWS shot showing the full screen as I suspect the full filter condition must exists there.

    Other alternative way to check and test it publish document with data which satisfies the filter condition and check if subscriber services gets called.


    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods


  • 5.  RE: Trigger condition is not updated at broker level

    Posted Tue July 26, 2016 02:13 PM

    Hi Sandeep,

    you will have to delete the trigger (under Clients) from Boker and then recreate it from Designer.

    Where there any changes on trigger type or thread count?
    These sometimes can cause reconnection errors.

    Regards,
    Holger


    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods


  • 6.  RE: Trigger condition is not updated at broker level

    Posted Tue July 26, 2016 02:19 PM

    Addendum:

    Is this a trigger related BPM (Process Model) or is this native IS-Trigger?

    Additionally this format of the subscriptions can not be evaluated on broker level, but will be evaluated on IntegrationServer side.

    Regards,
    Holger


    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods


  • 7.  RE: Trigger condition is not updated at broker level

    Posted Thu July 28, 2016 03:36 AM


  • 8.  RE: Trigger condition is not updated at broker level

    Posted Thu July 28, 2016 03:39 AM

    Its a Native IS trigger.

    Issue resolved now, until the regexp was correct at IS level, it was not reflected at Mws level.

    Also for matching regexp please keep the string Name from target IS, rather than source published Canonical.

    Now trigger works fine …Thank u all for your suggestions.

    correct trigger condition:

    ((%PO_CANONICAL/PO_LINE_INFO/PO_LINE[0]/REQUISITION_ID% == /MAXPN/ || %PO_CANONICAL/PO_LINE_INFO/PO_LINE[0]/REQUISITION_ID% == /MAXBA/ || %PO_CANONICAL/PO_LINE_INFO/PO_LINE[0]/REQUISITION_ID% == /MAXGR/ || %PO_CANONICAL/PO_LINE_INFO/PO_LINE[0]/REQUISITION_ID% == /MAXSC/ || %PO_CANONICAL/PO_LINE_INFO/PO_LINE[0]/DISTRIBUTION_INFO/DISTRIBUTION[0]/DELIVER_TO_LOCATION_CODE% == /GEE_FLUS059/) && ((%PO_CANONICAL/TARGET_SYSTEM% L_EQUALS ‘GEPW-PGP-US’) || (%PO_CANONICAL/TARGET_SYSTEM% L_EQUALS ‘GEPW-WIND-US’)) && (%PO_CANONICAL/SOURCE_SYSTEM% = ‘SSP5R12’)) || ((%PO_CANONICAL/TARGET_SYSTEM% L_EQUALS ‘GEPW-PGP-US’) && (%PO_CANONICAL/SOURCE_SYSTEM% L_EQUALS ‘SSP5R12’))

    Subscription filter in mws:

    ((((((regexpMatch(PO_CANONICAL.PO_LINE_INFO.PO_LINE[0].REQUISITION_ID,“MAXPN”) || regexpMatch(PO_CANONICAL.PO_LINE_INFO.PO_LINE[0].REQUISITION_ID,“MAXBA”)) || regexpMatch(PO_CANONICAL.PO_LINE_INFO.PO_LINE[0].REQUISITION_ID,“MAXGR”)) || regexpMatch(PO_CANONICAL.PO_LINE_INFO.PO_LINE[0].REQUISITION_ID,“MAXSC”)) || regexpMatch(PO_CANONICAL.PO_LINE_INFO.PO_LINE[0].DISTRIBUTION_INFO.DISTRIBUTION[0].DELIVER_TO_LOCATION_CODE,“GEE_FLUS059”)) && ((PO_CANONICAL.TARGET_SYSTEM == “GEPW-PGP-US”) || (PO_CANONICAL.TARGET_SYSTEM == “GEPW-WIND-US”))) || ((PO_CANONICAL.TARGET_SYSTEM == “GEPW-PGP-US”) && (PO_CANONICAL.SOURCE_SYSTEM == “SSP5R12”)))


    #webMethods-General
    #webMethods
    #Integration-Server-and-ESB