| RE: [cosmos-dev] FW: 216387 - Broker and domain on different machines |
|
I agree. It isn't a requirement for i8, but it is
definitely a COSMOS 1.0 requirement to easily configure multiple brokers
within a single domain.
Don The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Mohsin,
Jimmy
Sent: Friday, January 25, 2008 9:59 AM To: Cosmos Dev Subject: [cosmos-dev] FW: 216387 - Broker and domain on different machines Adding the dev
list. Thanks, Jimmy
Mohsin Cell
+1-609-635-1703 From: Devine, John T
I’m definitely not
concerned about this for i8. In the longer run since we allow
multiple brokers it would make sense to support having them on multiple machines
since some of the reasons for having multiple brokers (redundancy, load
distribution) are more useful with separate pieces of
hardware. Jack From: Mohsin, Jimmy
Bill, OK … so my questions
stand…. Team, Any comments?? Is this even a
viable test? If yes, how does the client determine which instance of the Domain
/ Broker to use? Thanks, Jimmy
Mohsin Cell
+1-609-635-1703 From: Muldoon, William H
Jimmy
I stand corrected; the domain and broker are packaged together. So as you
stated, there are two sets of domain-broker pairs, one on each
machine. Regards Bill From: Muldoon, William H
Jimmy
My interpretation of the setup is that Shivy deployed a single domain in tomcat
on machine 1 and a single broker in tomcat on machine 2. We can confirm this
configuration when she sends the registry (or just ask
her). The client can be deployed anywhere but it
only knows the EPR of the domain on machine 1. Regards Bill From: Mohsin, Jimmy
Bill, OK cool.. I guess I learnt
something new… In this case, if we have multiple instances of COSMOS running
EACH having the Domain / Broker, what do we do to ensure that only ONE Domain
functions and only ONE Broker function? Additionally, in this scenario, who
manages the EPRs? The client? And since we have multiple EPRs for a
single component (e.g. we have multiple Brokers), how does the client know which
EPR to use? Thanks, Jimmy
Mohsin Cell
+1-609-635-1703 From: Muldoon, William H
Jimmy
Yes I think it’s valid because any COSMOS component (domain, broker, data
managers, UI) may be deployed on any node in the network. The domain knows the
EPR of the broker because Shivy specified the domain EPR in step
3: 3. client app on machine 2; broker register command executed with domain EPRreflecting machine 1; Broker registered successfully message displayed Regards Bill From: Mohsin, Jimmy
Gents, I have a FUNDAMENTAL question about this defect… Is this even
a valid deployment of COSMOS? If I understand Shivvy right, she was
running TWO different instances of COSMOS… In that case, HOW would instance #1
Management Domain even know about the instance #2 Broker? Or do we have
some sort of an overarching EPR management or registration that can cross
instances???? Thanks, Jimmy
Mohsin Cell
+1-609-635-1703 |