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 233690"
(→Purpose) |
(→Requirements) |
||
Line 56: | Line 56: | ||
=Requirements= | =Requirements= | ||
+ | ==Identifier of a data manager== | ||
+ | The current implementation (as of i10) uses the Axis2 service group name and hostname together to uniquely identify a data manager. | ||
+ | |||
+ | CMDBf an important use case for data managers. That is, a data manager can be an MDR or a federating CMDB. The CMDBf specification has the notion of a "MDR ID", which is a URI that can uniquely identify a MDR. The MDR ID is also used to locate configuration items and relationships. The goal is the consolidate the approach for identifying an MDR and a data manager so that we don't need multiple ways to identify a data manager. | ||
+ | |||
+ | ==Descriptions of the data manager== | ||
+ | There are attributes about a data manager that provide information about the services it provides. These values can be displayed by the UI or used programmatically by a client application. These values include the display name, description, and other application specific name-value pairs. One requirement about these values is that they may be locale specific. | ||
+ | |||
+ | ==SOAP version of web services== | ||
+ | Axis2 supports web services using SOAP 1.1 or 1.2. While it is possible to deduce the SOAP version by getting the whole WSDL from the server, it is more efficient to get the SOAP version from the server without transfering the whole WSDL to the client. | ||
+ | |||
=Design= | =Design= | ||
=Open Issues/Questions= | =Open Issues/Questions= |
Revision as of 16:02, 20 June 2008
Configuring and retrieving data manager configuration values
Contents
Change History
Name: | Date: | Revised Sections: |
---|---|---|
Hubert Leung | June 19, 2008 |
|
Workload Estimation
Process | Sizing | Names of people doing the work |
---|---|---|
Design | 0 | Hubert Leung |
Code | 0 | Hubert Leung |
Test | 0 | Hubert Leung |
Documentation | 0 | Hubert Leung |
Build and infrastructure | 0 | Saurabh Dravid |
Code review, etc.* | ||
TOTAL | 0 |
'* - includes other committer work (e.g. check-in, contribution tracking)
Purpose
Each data manager have configuration values that can be used as identifiers, or attributes that indicate their functions. This enhancement is to provide the mechanism to configure these values at deployment time, and expose these values through web services.
Requirements
Identifier of a data manager
The current implementation (as of i10) uses the Axis2 service group name and hostname together to uniquely identify a data manager.
CMDBf an important use case for data managers. That is, a data manager can be an MDR or a federating CMDB. The CMDBf specification has the notion of a "MDR ID", which is a URI that can uniquely identify a MDR. The MDR ID is also used to locate configuration items and relationships. The goal is the consolidate the approach for identifying an MDR and a data manager so that we don't need multiple ways to identify a data manager.
Descriptions of the data manager
There are attributes about a data manager that provide information about the services it provides. These values can be displayed by the UI or used programmatically by a client application. These values include the display name, description, and other application specific name-value pairs. One requirement about these values is that they may be locale specific.
SOAP version of web services
Axis2 supports web services using SOAP 1.1 or 1.2. While it is possible to deduce the SOAP version by getting the whole WSDL from the server, it is more efficient to get the SOAP version from the server without transfering the whole WSDL to the client.