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.
COSMOS Design 235898
Contents
Change History
Name: | Date: | Revised Sections: |
---|---|---|
Bill Muldoon | June 27, 2008 |
|
Workload Estimation
Process | Sizing | Names of people doing the work |
---|---|---|
Design | 0.2 | Bill Muldoon |
Code | 0.6 | |
Test | 0.2 | |
Documentation | 0.2 | |
Build and infrastructure | 0 | |
Code review, etc.* | ||
TOTAL | 1.2 |
'* - includes other committer work (e.g. check-in, contribution tracking)
Purpose
Each Data Manager typically has "static" properties (or non-instance data) that can be kept in the Broker.
Need to add additional static data to the COSMOS Broker..
Requirements
The static properties of a Data Manager are:
- The Dialect, represented as a namespace (for example, SML).
- The SOAP version, represented as a namespace.
- The MdrId, a unique identifier of the MDR (this value only applies to MDRs).
- The Security level required by the Data Manager, also represented as a namespace value. Currently we only support basic security.
Note that all of the above properties are optional.
Relevant Use Cases
Query for a list of MDRs and their Meta Data
Design considerations
This change impacts:
- the Broker registration interface must support these new values
- the CLI application
- the COSMOS UI
- display the new properties in the properties view
- use the security information to determine whether to prompt the user for credentials
Related ERs:
233690 Configuring and retrieving data manager configuration values
238298 Integrate with new data collection changes