1 karl  1.1 /*

 2 karl  1.2 	$Log: interfaces.dxx,v $

 3 karl  1.4 	Revision 1.3  2001/02/06 17:02:13  karl
 4           	rearrange documentation for interfaces
 5           	

 6 karl  1.3 	Revision 1.2  2001/02/02 18:48:20  karl
 7           	Doc++ expansion
 8           	

 9 karl  1.2 	Revision 1.1  2001/01/24 14:18:49  karl
10           	import Dev Doc Files
11           	
12           	$Author: karl $

13 karl  1.1 */

14 karl  1.4 /** @name Pegasus Interfaces

15 karl  1.2 The Pegasus MSB interfaces with several different entities:

16 karl  1.1 
17           <UL> <LI> Providers

18 karl  1.2      <LI> Services (Including respositories and other services)

19 karl  1.1      <LI  Clients which may be either connectors or application consumers

20 karl  1.4      <LI> Repository

21 karl  1.1 </UL>
22           
23           Further, it includes both the APIs and the definitions of CIM data that are
24           required by the broker.
25           
26           Pegasus has effectivly implemented the same operations and data defintions across all of these interfaces with minor differences because of the special characteristics of each interface.

27 karl  1.2 

28 karl  1.4 <B>CIM Operations over HTTP</B>

29 karl  1.3 The core operations implemented in Pegasus are based entirely on the CIM operations over HTTP definitions by the DMTF in CIM Operations over HTTP specificaiton.
30           
31           The creation of all Pegasus interfaces is based on this core was a key objective in the design of Pegasus. These operations provide the creation, deletion, manipulation of CIM classes and objects and their components.
32           
33           Pegasus implements these operations as methods in the Pegasus class Operations The interfaces for this class and methods is defined in the header file operations.h.
34           

35 karl  1.2 <B>Client Interface</B>

36 karl  1.3 In Pegasus the client is a separate component that can communicate with the Pegasus server either through the WBEM CIM/XML protocol or directly through the Pegasus Client C++ Interfaces.

37 karl  1.2 

38 karl  1.3 The Client interfaces are an extension of the Pegasus Operations interfaces with some specific methods added for client/server communication control.

39 karl  1.2 

40 karl  1.4 <B>Provider Interfaces</B>

41 karl  1.2 
42           In Pegasus, the provider is a separate executable that accesses the
43           managed resources and is used by the CIMOM to provide access to
44           data. Providers forward this information to the CIMOM for
45           integration and interpretation. When the CIMOM receives a
46           request from a management application for data that is not available from the
47           CIMOM Repository, it forwards the request to a provider. The
48           CIMOM Repository only contains static data.
49           Providers implement a provider interface that supports the type of service
50           specific to their role. In order to implement the interface, a provider class
51           must first declare the interface in an implements clause, and then it must
52           provide an implementation (a body) for all of the abstract methods of
53           the.interface.
54           
55           

56 karl  1.4 <Services Interfaces</B>

57 karl  1.2 
58           ATTN: Need to put something here.
59           

60 karl  1.4 <B>Repository Interfaces</B>

61 karl  1.2 
62           The repository interface isused by the CIMOM to  interface with implementations of the repository thatstore and
63           retrieve provide persistence for class and instance information. 
64           
65           A prototype implementation of both a class and instance provider is provided with Pegasus (ATTN: SEE ALSO). However, it is expected that this will be replaced in many installations.
66           .

67 karl  1.1 */
68