| Affinity Domains [message #22024] |
Fri, 03 November 2006 15:51  |
Eclipse User |
|
|
|
Hi,
At the meeting in Chicago discussing the HIMSS participation there was a bit
of talk about there being several different affinity domains. Does anyone
know what the requirements are regarding affinity domain for both the MESA
test (if there are any), Connectathon, and HIMSS demonstration?
Does anyone know what type of functionality we need to implement to support
this? Would be just as simple as doing the same queries/actions over
multiple RHIOs (as far as looking for documents is concerned).
I am just trying to get an idea as to what the requirements are, and how we
can go about supporting it.
|
|
|
| Re: Affinity Domains [message #22212 is a reply to message #22024] |
Fri, 03 November 2006 20:09  |
| Eclipse User |
|
|
|
Hi Corey,
Your suspicion is correct. For connectathion you will have to do every
transaction you complete fro MESA test with 3 separate vendors. So for
document query, you will have to sucessfully query against 3 different
registries. For MESA testing your PIX/PDQ tests will al be done against
the MESA PC and your XDS tests against the NIST server. So essentially
the MESA PC and the NIST server act as a single Affinity Domain for MESA
tests.
THe OHF bridge is your proxy to all Affinity Domains/ RHIOS. For MESA
testing ... we have essentially created a test RHIO jsut for you that
includes your MESA PC and the NIST server IP information. Come
connectathon and HIMSS we will work together to load all the different
testing configurations into the OHF bridge. Then switching between RHIOs
will be a simple selection for you (choose a different session context).
Hope this clarifies,
Sarah
Corey Spears wrote:
> Hi,
>
> At the meeting in Chicago discussing the HIMSS participation there was a bit
> of talk about there being several different affinity domains. Does anyone
> know what the requirements are regarding affinity domain for both the MESA
> test (if there are any), Connectathon, and HIMSS demonstration?
> Does anyone know what type of functionality we need to implement to support
> this? Would be just as simple as doing the same queries/actions over
> multiple RHIOs (as far as looking for documents is concerned).
>
> I am just trying to get an idea as to what the requirements are, and how we
> can go about supporting it.
>
>
|
|
|
| Re: Affinity Domains [message #572046 is a reply to message #22024] |
Fri, 03 November 2006 20:09 |
| Eclipse User |
|
|
|
Hi Corey,
Your suspicion is correct. For connectathion you will have to do every
transaction you complete fro MESA test with 3 separate vendors. So for
document query, you will have to sucessfully query against 3 different
registries. For MESA testing your PIX/PDQ tests will al be done against
the MESA PC and your XDS tests against the NIST server. So essentially
the MESA PC and the NIST server act as a single Affinity Domain for MESA
tests.
THe OHF bridge is your proxy to all Affinity Domains/ RHIOS. For MESA
testing ... we have essentially created a test RHIO jsut for you that
includes your MESA PC and the NIST server IP information. Come
connectathon and HIMSS we will work together to load all the different
testing configurations into the OHF bridge. Then switching between RHIOs
will be a simple selection for you (choose a different session context).
Hope this clarifies,
Sarah
Corey Spears wrote:
> Hi,
>
> At the meeting in Chicago discussing the HIMSS participation there was a bit
> of talk about there being several different affinity domains. Does anyone
> know what the requirements are regarding affinity domain for both the MESA
> test (if there are any), Connectathon, and HIMSS demonstration?
> Does anyone know what type of functionality we need to implement to support
> this? Would be just as simple as doing the same queries/actions over
> multiple RHIOs (as far as looking for documents is concerned).
>
> I am just trying to get an idea as to what the requirements are, and how we
> can go about supporting it.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.05437 seconds
Home