Non-typical routing

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Non-typical routing

  • Creator
    Topic
  • #52659
    Anonymous

      Hi folks,

      Typically, we do routing by message type. That is, recipient system would pre-determine which of the source system’s message types are to be routed to them.

      What if the source system is to ‘inform’ Cloverleaf which recipient systems is supposed to receive a copy of the message based on a list of specified recipients in the message itself?

      How would you go about implementing this?

      Sorry if this isn’t clear as I am trying to just present the problem rather than the solution that immediately pops into mind, as I’d like to hear what other solutions there may be…..

      TIA!

    Viewing 1 reply thread
    • Author
      Replies
      • #75037
        Rehman Masood
        Participant

          Based on the information u have given, I would use a trxid with wildcard matching.

        • #75038
          David Harrison
          Participant

            If the inbound message contains a list of recipients, why not set up routes to all outbound systems and, for each TrxId, filter using a tcl proc pre-Xlate.

        Viewing 1 reply thread
        • The forum ‘Cloverleaf’ is closed to new topics and replies.