version 1.3, 2001/06/12 14:32:26
|
version 1.4, 2001/06/30 15:28:09
|
|
|
</td> | </td> |
</tr> | </tr> |
</table> | </table> |
<hr></hr> |
<hr> |
<form name="GetNameSpaces" METHOD=GET ACTION="/pegasus/cgi-bin/CGIClient"> | <form name="GetNameSpaces" METHOD=GET ACTION="/pegasus/cgi-bin/CGIClient"> |
<INPUT TYPE="hidden" NAME="Operation" VALUE="GetNameSpaces"> | <INPUT TYPE="hidden" NAME="Operation" VALUE="GetNameSpaces"> |
<input type="hidden" name="hostip" value="localhost"> |
<INPUT TYPE="hidden" NAME="hostaddress" VALUE="localhost:5988"> |
<input type="hidden" name="portnum" value="5988"> |
<INPUT TYPE="hidden" NAME="debug" VALUE=""> |
Gets a list of all of the existing namespaces on the defined host. |
Gets a list of all of the existing namespaces on the target CIM Server.. |
| |
<p><INPUT TYPE="submit" VALUE="Submit Request"> | <p><INPUT TYPE="submit" VALUE="Submit Request"> |
<p><INPUT TYPE="reset" VALUE="Reset"> | <p><INPUT TYPE="reset" VALUE="Reset"> |
</form> | </form> |
<script> | <script> |
GetNameSpaces.hostip.value = opener.top.hostip; |
document.GetNameSpaces.hostaddress.value = top.hostAddress; |
GetNameSpaces.portnum.value = opener.top.portnum; |
document.GetNameSpaces.debug.value = top.debug; |
|
document.GetNameSpaces.NameSpace.value = top.NameSpace; |
|
|
window.focus(); | window.focus(); |
</script> | </script> |
|
<p>Namespaces define a container within a CIM Server for Classes and |
|
Instances. There may be multiple namespaces in a single CIM Server. |
|
While Namespaces names are defined in a manner that makes them look |
|
hiearchial (/root/cimv2), in fact, they are simply a list of names in the |
|
Pegasus implementation. The CIM specifications leave the defintion of |
|
namespace relationships as an implementation issue and we chose to simply |
|
make them a flat name list. Thus root is a single namespace and |
|
root/cimv2 is a single namespace but there is no implied relationship |
|
between root and root/cimv2. There is no inheritance of |
|
characteristics or classes and no issues of containment.</p> |
|
<p>However, the concept of namespaces is key to understanding CIM |
|
operations. All operations are executed against a namespace. You |
|
will note that the name of the namespace exists in the form screen for all |
|
operations. This is a required field for every CIM operation.</p> |
|
<p>In fact, the only relationships that really exist across namespaces are |
|
those defined by associations.</p> |
|
<p>Only one namespace is clearly defined and required by the CIM |
|
specificaitons, root. All other namespaces including cimv2 are merely |
|
recommendations or examples today.</p> |
|
<p>Normally namespaces are defined and populated as part of the process of |
|
installing CIM classes. The capability exists to create and to delete |
|
namespaces.</p> |
|
<p>These functions are provided in this demonstration simply as a tool to |
|
help you understand what namespaces are and how we access them.</p> |
|
<p>There are today two different techniques for querying an manipulating |
|
namespaces.</p> |
|
<h3>Original Namespace Manipulator</h3> |
|
<p>The original technique defined in the CIM Operations document V1 is based |
|
on the use of a pseudo class __Namespace and execution of operations on the |
|
instances of this pseudo class (enumerate instances, create instance, delete |
|
instance) to query namespaces and to create and delete namespaces. We |
|
call this a pseudo class because it does not really exist in the CIM |
|
schemas. It is implementation dependent and may be defined differently |
|
for each implementation.</p> |
|
<p>In fact, since the properities of this class are implementation dependent |
|
there is really no interoperability in the manipulation of namespaces.</p> |
|
<h3>New Namespace Manipulator</h3> |
|
<p>Effective with CIM 2.6, a new set of classes has been defined for the |
|
query of information about CIM Servers and the namespaces defined in those |
|
CIM servers.</p> |
|
<p>TBD</p> |
|
|
|
<pre> </pre> |
|
<hr><p style="margin-top: 0; margin-bottom: 0"> <font size="2">Demonstration |
|
Prepared by the OpenGroup Manageability Work Group Pegasus Development Team</font> |
|
|
|
<p style="margin-top: 0; margin-bottom: 0"> <font size="2">See (<a href="http://www.opengroup.org/management">http://www.opengroup.org/management</a>) |
|
for more information on Pegasus</font> |
|
|
|
<p style="margin-top: 0; margin-bottom: 0"> <font size="1">Last Modified <!--webbot bot="Timestamp" S-Type="EDITED" |
|
S-Format="%A, %B %d, %Y %I:%M:%S %p" startspan -->Friday, June 29, 2001 06:42:17 PM<!--webbot bot="Timestamp" i-CheckSum="55037" endspan --> |
|
Copyright @ The Open Group 2001 </font> |
|
|
</body> | </body> |
</html> | </html> |