| Author |
JMS broker
|
Lin Sun
Greenhorn
Joined: Mar 23, 2012
Posts: 16
|
|
When SuD sends JMS message to external/destination system, do you include a JMS broker (i.e. Apache ActiveMQ) in component diagram? If so, is it a component in SuD? Or is it considered to be an external component in between SuD and destination system (kind of like a Email Server)?
Reason to call for a JMS broker is to uncouple SuD and external/destination system. Routing logic can be configured in the JMS broker.
Otherwise, without it in place, I'd have to design SuD to include JMS endpoint for each destination.
|
 |
Paul Balm
Ranch Hand
Joined: Dec 13, 2008
Posts: 63
|
|
I'm not sure I understand completely what you're saying, but I have not included the JMS Broker in the component diagram, I've included several queues. I would show the JMS configuration at that level: Queues and Topics.
As to your final remark, if I remember correctly, the external systems should appear in the component diagram. You don't have to detail their internals, because the fact that they're external means you don't know & don't care. But you do need to deal with their interface, so they must appear in your component diagram.
I should get paid by Cade and Sheil for recommending their book so much, but it's well worth the money:
http://www.amazon.com/Certified-Enterprise-Architect-Study-Guide/dp/0131482033/ref=sr_1_1?s=books&ie=UTF8&qid=1343337367&sr=1-1&keywords=cade+sheil
If you just don't have the money, there is also a presentation on the web that is informative, see this post:
http://www.coderanch.com/t/508367/java-Architect-SCEA/certification/Where-find-powerpoint-presentation-Humprey
Cheers-
|
SCJP 1.4 -- SCJD Java 2 -- OCM JEA 5
|
 |
 |
|
|
subject: JMS broker
|
|
|