| RE: [cosmos-dev] Data Manager and Broker interactions in i9 |
|
Jimmy,
I agree with Hubert's statements about these issues.
Our default configuration today is driven by a desire to
make it as easy as possible to assemble a working configuration of these
components. For COSMOS 1.0 we need to expose a more appropriate mechanism
for customizing their configuration.
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: Monday, February 04, 2008 7:06 PM To: Cosmos Dev Cc: Doma, Srinivas Reddy Subject: [cosmos-dev] Data Manager and Broker interactions in i9 Team, Another series of questions from Srinivas… These are
interesting questions… and we need answers to enable QA to properly scope the i9
testing (ER 216529 Define scope and detail the i9 QA activities).
This is also a continuation of the thread of the Management Domain – Data Broker
– Data Manager being “tightly-coupled”, at least in the current
architecture…. Hubert
/ Sheldon / Mark, Do
you see this change between now and i11? Should we talk about this in the
next Arch call? Thanks, Jimmy Query from Srinivas Doma 2.
Data
Managers
-
During i8
iteration, we saw Data Managers are
registering to default broker automatically? I feel it should ask
for Broker EPR and then register, so that we
can have broker running anywhere (local or remote machine) -
Also
all 4
Data Managers are getting
up instantly with single
command? Can we have some
control over them in bringing up/down of desired data
managers? -
When we bring
down Data Managers, why don’t
it de-registers from broker? So that user cannot
query for data on inactive data
mangers. |