Tibco EMS

Routing with TIBCO EMS Messaging

TIBCO EMS is a messaging (a core M.O.M.) product by TIBCO based on Java Message Service
(JMS) specification. It is quite robust, very popular messaging product of choice in enterprise circles
for messaging needs especially in integrations developed on TIBCO platform.
Routing
Routing feature of EMS will be needed when more than one EMS servers are deployed in an enterprise
architecture. Routing is basically the ability to send message from one EMS server to the next. A route
is a named connection between two EMS servers. A route once established can forward messages from
one EMS server to corresponding destinations (JMS topics and queues) in another EMS server. Two
destinations correspond when they have the same name and are of the same type (queues vs topics).
Routing will work between two EMS servers if the destination on server 1 has same name, and
type as that on server 2 and both have property GLOBAL set to true.
Here's a general structure of a route:
Zones & Hops
Zone is a name that can be assigned as a property to a set of routes between EMS servers that are active
in an enterprise network.
Hops designate the forwarding behavior of a zone. Messages arriving on a server that is in a
multi-hop zone will forward them to ALL severs on that zone while those in single-hop zone will
forward it to nearest only.
Here's how EMS servers that are in a multi-hop zone can be represented:
In above configuration, a message publised on EMS server B, will be forwarded even to server
E on the far end given that it is a multi-hop zone.
Creating & Administering Routes
The routes can be created using EMS Administrator CLI. A typical command will look like this:
The syntax of the command for creating routes is:
examples:
Routes can be viewed using show routes commad:
The routes are stored in routes.conf file.