2 Replies Latest reply on Feb 21, 2007 11:27 AM by 452012

    CBR issue

      We have en interface that publishes messages to 4 receiving applications.
      All applications want to receive a certain subset of the data based on different content-checks.

      If we publish a messages that does not fit any of the 4 applications we get an error in the publishing adapter. In fact there is no error, only nobody wants to receive this specific message. IC should therefore drop the message, but it logs an error and places the message in the error-resubmission-queue.

      Anybody has some comments/tips/answer/solution to this case?

      Below is (all) the error detail from the adapter (loglevel=trace)

      regards, Ton

      /* Error:
      Mon Jan 15 16:36:57 CET 2007: Could not give the message to the hub because there is no routing information specified for this message. Please enter valid routing information for this message either in the Message Capability Matrix (under the Deploy tabb panel) or using the Content Based Routing feature in iStudio.
        • 1. Re: CBR issue
          Simply ignore it.

          You see, InterConnect is TRANSPORT solution, it's like a pipe.
          So if one put message in a pipe, another should take it, otherwise do'nt put it.

          If to say more realistically, your may need some business logis layer, wich implemented natively in Workflow or more modern - in BPEL.
          In this case you always publish message from source application to Workflow (BPEL) and there inside business process you decede whether to publish forwards or simply NULL the message.
          This decide point even could be implemented in Business Rules in case of using BPEL as business logic layer - so you could dynamically on the fly change the condition of receiveing message by one or another application or temporarilly disconect one of the receiving applications...
          • 2. Re: CBR issue

            You can try and adopt of the following 2 paradigms:

            1)     If using a DB adapter, restrict the data before publishing the massage and then use the CBR to filter the message to the other 4 other subscribing Applications as designed – this will help to eliminate the above error or .
            2)     Create an adapter and point it locally/internally and use the CBR to redirect any messages that do not satisfy any of the 4 other 4 other subscribing Applications to the internal Adapter.