Dynamic Routing to multiple host, site and threads

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Dynamic Routing to multiple host, site and threads

  • Creator
    Topic
  • #54249
    sameer desai
    Participant

      Scenario:

      One WSA thread receiving data from API.

      Need to route messages to different threads which are different sites than WSA thread. sometimes on completely different host.

      Current Solution:

      1 file thread which routes to  destination for inet-site thread.

      we change SOURCECONN dynamically based on message values.

      Desired Solution:

      Remove need for file thread.

      Best Solution:

      Direct routing to a thread on different site.

      Problems Faced.

      We were able to send message to a thread on different site directly through WSA thread by updating DESTCONN to threadName:host:port but this establishes a connection between WSA thread and Public thread in other site which makes it impossible to establish new connection with different thread

      Does any one knows how this can be solved. We are on CL 5.8.6

    Viewing 2 reply threads
    • Author
      Replies
      • #80723
        Charlie Bursell
        Participant

          Have you tried inter-site routing?

        • #80724
          Brandon Grudt
          Participant

            To elaborate, it depends on what type of thread you want to send to.  

            If you want to send to a client (outbound thread) you must set the inter-site routing port on the client you want to receive the data.  Then, you must create a new destination (instead of a new thread) and point it to the client that has the inter-site routing port.

            If you simply want to get the information from one server (inbound thread) to another, you can create a client that points to localhost and the port of the second server thread, creating a loop back into the server.

          • #80725
            sameer desai
            Participant

              Inter-site – routing- yes our current appraoch is to do it with inte-rsite routing.

              the problem is that one WSA thread might have to cater over 150+ intersite threads in future. so we do not want to create 150+ destiantion and put a physical route in WSA thread for each destiantion.

              We have created public threads in target sites and want to send the data to these public threads directly from WSA using TCL.

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