1 kamal.locahana 1.1.2.1 //%2006////////////////////////////////////////////////////////////////////////
2 //
3 // Copyright (c) 2000, 2001, 2002 BMC Software; Hewlett-Packard Development
4 // Company, L.P.; IBM Corp.; The Open Group; Tivoli Systems.
5 // Copyright (c) 2003 BMC Software; Hewlett-Packard Development Company, L.P.;
6 // IBM Corp.; EMC Corporation, The Open Group.
7 // Copyright (c) 2004 BMC Software; Hewlett-Packard Development Company, L.P.;
8 // IBM Corp.; EMC Corporation; VERITAS Software Corporation; The Open Group.
9 // Copyright (c) 2005 Hewlett-Packard Development Company, L.P.; IBM Corp.;
10 // EMC Corporation; VERITAS Software Corporation; The Open Group.
11 // Copyright (c) 2006 Hewlett-Packard Development Company, L.P.; IBM Corp.;
12 // EMC Corporation; Symantec Corporation; The Open Group.
13 // Copyright (c) 2007 Hewlett-Packard Development Company, L.P.; IBM Corp.;
14 // EMC Corporation; Symantec Corporation; The Open Group.
15 //
16 // Permission is hereby granted, free of charge, to any person obtaining a copy
17 // of this software and associated documentation files (the "Software"), to
18 // deal in the Software without restriction, including without limitation the
19 // rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
20 // sell copies of the Software, and to permit persons to whom the Software is
21 // furnished to do so, subject to the following conditions:
22 kamal.locahana 1.1.2.1 //
23 // THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED IN
24 // ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE SOFTWARE IS PROVIDED
25 // "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
26 // LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
27 // PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
28 // HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
29 // ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
30 // WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
31 //
32 //==============================================================================
33
34 Direct Access CIM readme
35 ========================
36
37 Filename: readme.directaccessCIM
38 Authors: Ed Boden
39 Date: 1 May 2007
40
41 PEPs 273 & 274 describe the direct access CIM (also referred to as
42 'CIM API'). This is the ability to access all local CIM information
43 kamal.locahana 1.1.2.1 (classes, qualifieres, instances, associations, properties, etc.)
44 via the normal CIM operations, without going through a CIM server
45 (the CIM server need not be running).
46
47 Direct access CIM uses the existing CIMClient.h API with no changes.
48 The full CIMClient.h API is supported to the same level its supported
49 when used to access a CIM server.
50
51 Direct access CIM supports all existing OpenPegasus provider types,
52 transparently.
53
54 Direct access indications; direct access CIM adds a few additional
55 APIs and function function related to CIM indications. This is
56 in addition to the existing CIM server indication functions. The
57 key feature of direct access indications is that they are delivered
58 via callback, where the recieving code is able to do whatever is
59 needed with the indication. See CIMDirectAccess.h for details.
60
61 There are 3 types of direct access CIM builds;
62
63 1) 'integrated dacim' -- uses the local CIM server repository.
64 kamal.locahana 1.1.2.1 May be used with or without the CIM server running. If
65 running, the CIM server will be used for repository updates.
66 If the CIM server is not running, dacim will perform the
67 operation.
68
69 2) 'separate repository dacim' -- has its own repository.
70
71 3) 'stand-alone dacim' -- uses separate repository and separate
72 shared libraries. (The CIM server need not be installed.)
73
74 The initial release of dacim supports integrated dacim. (See PEP 274
75 for more specifics about the 3 builds.)
76
77
78
79 Building direct access CIM
80 ===================================================================
81
82 Direct access CIM is built by setting the environment variable
83 PEGASUS_USE_DIRECTACCESS_FOR_LOCAL to 'true', and then run
84 make as usual.
85 kamal.locahana 1.1.2.1
86
87
88 Testing direct access CIM
89 =====================================================================
90
91 If OpenPegasus has been built with direct access CIM capability (check
92 --version on some command), the existing test targets will run
93 direct access CIM tests.
94
95 Example; make servertests
96
97
98
99 Runtime switching of direct access CIM
100 ===========================================================
101
102 Direct access CIM may be switched on and off at runtime by
103 setting PEGASUS_USE_DIRECTACCESS_FOR_LOCAL_RT 'true' or
104 'false' (see 'pegasus/toggledacim').
105
106 kamal.locahana 1.1.2.1
107
108 ==========================================================================
109 For additional information refer to PEP273, 274. To determine what build
110 of OpenPgasus you have, enter one of the commands with '--version'.
111
|