Inter-Site Routing

[Femina Jaffer]

Hello,

I was wondering if anyone has recent experience with the Inter_site Routing Port configuration?  I have a feed in our Production server (different host /IP) and I need to send the feed to the test server (different host/ip).  This is a pure RAW feed.  This would be a similar setup to a site to site with the exception of different HOST/IP.  Would it be a good idea in this scenario to use inter-site routing?  The inbound thread is a heavy volume of messages.  What are the benefits of inter-site routing?

Thanks,

FJ

Topic

[Brandon Grudt]

What were you looking to find out, specifically?  I use both loops (regular clients that point to localhost) and inter-site routing, depending on what I am trying to do.  

Typically, I use the inter-site routing method when I want to merge client feeds.  I use a loop when I want an client to send messages to a server.

To use the inter-site routing, create a Destination instead of a Thread.  Set a Host, site, thread, and port.  Route your data to it.  On the thread that you want to receive the data, set the inter-site routing port to the same port you just put on the Destination.

[David Barr]

For me the main benefit of intersite routing is the preservation of message metadata.

We use message metadata for a lot of things: retaining values of fields that have been blanked out for most systems, filenames on file based interfaces, message priorities, storing field values that will be accessed several times for message routing in different threads or storing values that will be used by a common SENDOK proc that gets input from many sources.

[Author]

Replies