1 karl 1.1 <html>
2 <body bgcolor="#CCCCCC">
3 <table width="100%">
4 <tr>
|
5 karl 1.3 <td width="50%" align="bottom"><h1>Enumerate NameSpaces</h1><td>
|
6 karl 1.1 <td width="50%" align="right">
7 <img border=1 src="/pegasus/icons/OpenGroupLogo.gif">
8 </td>
9 </tr>
10 </table>
11 <hr>
12 <form METHOD=GET ACTION="/pegasus/cgi-bin/CGIClient">
|
13 karl 1.3 <INPUT TYPE="hidden" NAME="Operation" VALUE="EnumerateNameSpaces">
|
14 karl 1.1 <p>
|
15 karl 1.3 <a name="TOP"></a>
16 This request enumerates the namespaces defined in the repository. This is not a CIM intrinsic method but uses CIM enumerateInstance.
17 <p><b><a href="#NameSpace">NameSpace</a></b>
|
18 karl 1.1 <INPUT TYPE="text" NAME="NameSpace" SIZE=30 VALUE="root">
|
19 karl 1.3 Defines the root namespace where the __Namespace class is defined. (DO NOT CHANGE)
20 <p><b><a href="#ClassName">ClassName</a></b> <INPUT TYPE="text" NAME="ClassName" SIZE=30 VALUE="__Namespace">
21 Defines the __Namespace class within the repository. (DO NOT CHANGE)<p><b>DO
22 NOT CHANGE THE ABOVE. THE FIELDS ARE PROVIDED FOR INFORMATION ONLY</b>
|
23 karl 1.1 <p><INPUT TYPE="submit" VALUE="Submit Request">
|
24 karl 1.3 <INPUT TYPE="reset" VALUE="Reset">
|
25 karl 1.1
26 <hr>
|
27 karl 1.3 <hr>
|
28 karl 1.4 </form>
29 <h2>Return Results</h2>
30 If successful, the method returns zero or more named
31 Instances that meet the required criteria.
32
33 If unsuccessful, one of the following status codes MUST be returned
34 by this method, where the first applicable error in the list (starting
35 with the first element of the list, and working down) is the error
36 returned. Any additional method-specific interpretation of the error in
37 is given in parentheses.
38
39 <UL>
40 <LI>CIM_ERR_ACCESS_DENIED
41 <LI>CIM_ERR_NOT_SUPPORTED
42 <LI>CIM_ERR_INVALID_NAMESPACE
43 <LI>CIM_ERR_INVALID_PARAMETER (including missing,
44 duplicate, unrecognized or otherwise incorrect parameters)
45 <LI>CIM_ERR_INVALID_CLASS (the CIM Class that is the
46 basis for this enumeration does not exist)
47 <LI>CIM_ERR_FAILED (some other unspecified error occurred)</LI>
48 </UL>
49 karl 1.4 <p> </p>
|
50 karl 1.3 <h2>Additional Information on the Fields</h2>
51 <p><a name="NameSpace"><b>NameSpace</b></a> - The NameSpace parameter is a string that defines the
52 target namespace
53
54 <p><a name="className"><b>ClassName</b></a> - The <TT>ClassName</TT> input parameter defines the Class
55 that is the basis for the enumeration. Note that the class named is not
56 retrieved as part of the enumeration. Thus, if there are no subclasses to
57 the named class, zero classe names are returned.
58 <p><b>Definition of the Namespace -</b> An object that defines a scope within which object keys must be unique. Multiple namespaces typically indicate the presence
59 of multiple management spaces or multiple devices.
60
61 The namespace pragma
62 <PRE> #pragma namespace( )</PRE>
63 This pragma is used to specify a Namespace path. The syntax
64 needs to conform to the following:
65 <PRE> <namespacetype>://<namespacehandle></PRE>
66 <P>The contents of a MOF file are loaded into a namespace that provides a domain (in other words, a container), in which the instances of the classes are guaranteed to be unique per the KEY qualifier definitions. The term namespace is used to refer to an implementation that provides such a domain.
67 Namespaces can be used to:
68 <UL>
69 <LI>Define chunks of management information (objects and associations) to limit implementation resource requirements, such as database size.
70 <LI>Define views on the model for applications managing only specific objects, such as hubs.
71 karl 1.3 <LI>Pre-structure groups of objects for optimized query speed.
72 </UL>
73 <p><b>Implementation of Namespace Manipulation - </b>Today the namespace manipulation defined in CIM Operations over HTTP
74 (Section 2.5) is
75 proprietary in nature. It is based on a class named __Namespace
76 which creates an instance for each namespace defined for the CIMOM. The
77 only required property in the __namespace class is the name.
78 <p>Within Pegasus, the namespace manipulation based on the __namespace
79 class can be executed through this HTML page or through the <a href="EnumerateInstanceNames.html">enumerateInstanceNames</a>
80 operation with the classname = __namespace and the namespace
81 parameter = root. While it has not been formally defined
82 within the specification,
83 Pegasus today maintains the __namespace class in the root namespace.</p>
84 <p style="line-height: 100%; margin-top: 0; margin-bottom: 0">Operations
85 on the __NameSpace class are handled within Pegasus by a special provider
86 that manipulates the instances of the class and also creates and deletes
87 namespaces.</p>
|
88 karl 1.4 <hr><p style="margin-top: 0; margin-bottom: 0"> <font size="2">Demonstration
89 Prepared by the OpenGroup Manageability Work Group Pegasus Development Team</font>
90
91 <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>)
92 for more information on Pegasus</font>
93
|
94 karl 1.3 <p style="line-height: 100%; margin-top: 0; margin-bottom: 0"><font size="1">Last
95 Modified <!--webbot bot="Timestamp" S-Type="EDITED"
|
96 karl 1.4 S-Format="%A, %B %d, %Y %I:%M:%S %p" startspan -->Monday, March 26, 2001 02:37:32 PM<!--webbot bot="Timestamp" i-CheckSum="50314" endspan -->
97 Copyright @ The Open Group 2001 </font>
|
98 karl 1.2 <p>
|
99 karl 1.1 </body>
100 </html>
|
Return to
enumeratenamespaces.html
CVS log
Up to [Pegasus] / pegasus / cgi / htdocs