Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOS Design 198553"
(→Applications of WS-RC in COSMOS) |
|||
Line 1: | Line 1: | ||
− | |||
− | |||
== Design Considerations == | == Design Considerations == | ||
Line 17: | Line 15: | ||
== Applications of WS-RC in COSMOS == | == Applications of WS-RC in COSMOS == | ||
* Management Domain | * Management Domain | ||
− | * | + | * Data Broker |
− | + | ** The remote APIs will be WS-RC APIs | |
== Use Cases == | == Use Cases == | ||
* Mohammad to enumerate | * Mohammad to enumerate |
Revision as of 13:05, 7 August 2007
Design Considerations
- We would like to have clean layers in the design. The web services layer needs to be distinct from the actual implementation of the catalog itself.
- We would like to be able to "bind" to different underlying implementations. For COSMOS in open source, can we use a simple flat file or do we need a relational DB?
- In the case of COSMOS and CMDBf, we would NOT choose to expose the MDR via WS-RC.
- What is the mapping of SML onto the schema of the RC?
- If this is a simple mapping, e.g. <EntryRef> = <SMLRef>, <ResourceRef> = <SMLRef w/EPR>, or something like that, can we simply use the existing SML repository that we have now and expose WS APIs that exchange RC entries via an XSLT? SML to WSRC Mapping
- The WS-RC spec talks about the use of WS-R
Applications of WS-RC in COSMOS
- Management Domain
- Data Broker
- The remote APIs will be WS-RC APIs
Use Cases
- Mohammad to enumerate