Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOS Design 198553"
| Line 1: | Line 1: | ||
| − | |||
| Line 19: | Line 18: | ||
* Management Domain | * Management Domain | ||
* "Broker"/"Service Broker" | * "Broker"/"Service Broker" | ||
| + | |||
| + | |||
| + | == Use Cases == | ||
| + | * Mohammad to enumerate | ||
Revision as of 12:55, 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
- "Broker"/"Service Broker"
Use Cases
- Mohammad to enumerate