This chapter is from the book
This chapter is from the book
This chapter is from the book
6.3 Fixed Router
A fixed router, one where a single channel is a source of messages and a single channel is a destination, is the most trivial form of a Message Router. You would typically configure the connectivity map source and destination to configure a fixed router. If necessary, however, a Java Collaboration or a Business Process can be constructed to explicitly choose a destination if that destination is a JMS Destination.
Given the connectivity map shown in Figure 6-2, we would expect that the Java Collaboration publishes messages to the JMS Destination (queue) qDummyDestination.
)
Figure 6-2 Connectivity map of an implicit fixed router
Inspection of the collaboration source, shown in Figure 6-3, reveals that it is the JMS Destination (queue) qNewQueue that is the actual destination of messages. This destination is hardcoded in the fixed router.
)
Figure 6-3 Hardcoded JMS queue name in a fixed router, which uses a sendTo() OTD method
The same effect could be achieved by explicit assignment of the destination queue name prior to sending the message, as shown in Figure 6-4.
)
Figure 6-4 Hardcoded JMS queue name in a fixed router using a "destination" OTD node
Given the connectivity map shown in Figure 6-5, we would again expect the queue qDummyDestination to be the destination of messages.
)
Figure 6-5 Implicit fixed router connectivity map
Inspecting the business rules embedded in the eInsight Business Process, shown in Figure 6-6, reveals this to not be the case.
)
Figure 6-6 Explicit JMS queue assignment in a Business Process
In this example, an explicit assignment of a JMS Destination name to the destination node of the JMS OTD results in messages being explicitly routed to a JMS Destination (queue) qNewJMSDestination.