Configuring for unidirectional routing.
Article ID: KB0088184
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
==========
Configure one direction route
Environment:
==========
All
Solution:
=======
You can use message selectors on the route to achieve this. That is, set a selector which never can be satisfied. For more information, please refer to EMS User's Guide -> Chapter 19 Working With Routes -> Routed Topic Messages -> Selectors for Routing Topic Messages.
There are certain restrictions to the selector you can set. These restrictions are documented in EMS Java API Doc. For your reference please see the EMS User's Guide -> Java API -> Interface Message -> Message Selector.
You should not use ACL to achieve a one direction route as the messages will be accumulated in the upstream server and potentially cause an out of memory condition on the upstream server.
Description:
==========
Configure one direction route
Environment:
==========
All
Solution:
=======
You can use message selectors on the route to achieve this. That is, set a selector which never can be satisfied. For more information, please refer to EMS User's Guide -> Chapter 19 Working With Routes -> Routed Topic Messages -> Selectors for Routing Topic Messages.
There are certain restrictions to the selector you can set. These restrictions are documented in EMS Java API Doc. For your reference please see the EMS User's Guide -> Java API -> Interface Message -> Message Selector.
You should not use ACL to achieve a one direction route as the messages will be accumulated in the upstream server and potentially cause an out of memory condition on the upstream server.
Issue/Introduction
Configuring for unidirectional routing.
Feedback
Yes
No
Powered by
