1 karl  1.3 //%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           //
 14           // Permission is hereby granted, free of charge, to any person obtaining a copy
 15           // of this software and associated documentation files (the "Software"), to
 16           // deal in the Software without restriction, including without limitation the
 17           // rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
 18           // sell copies of the Software, and to permit persons to whom the Software is
 19           // furnished to do so, subject to the following conditions:
 20           // 
 21           // THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED IN
 22 karl  1.3 // ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE SOFTWARE IS PROVIDED
 23           // "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
 24           // LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
 25           // PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
 26           // HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
 27           // ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
 28           // WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 29           //
 30           //==============================================================================

 31 schuur 1.1 /------------------------------\
 32            | Remote CMPI Extension README |
 33            \------------------------------/
 34            
 35            
 36            Abstract:
 37            ---------
 38            
 39            Remote CMPI enables providers to be run on remote systems without the need
 40            for an extra CIMOM. It uses a special proxying provider to relay requests
 41            to a remote location using so-called communication layers. The remote
 42            side has to start a CMPIRDaemon process, which accepts remote requests and
 43            passes them on to CMPI style providers.
 44            
 45            Remote providers are fully binary compatible and need not to be recompiled.
 46            Currently there are two types of remote provider available: out-of-process
 47            providers and TCP/IP providers using a separate daemon program.
 48            
 49            Remote CMPI support is now integrated in OpenPegasus.
 50            
 51            This implementation uses remote location routing based on namespace names.
 52 schuur 1.1 CIM requests issued against namespaces designated as remote namespaces will
 53            be routed automatically to remote locations.
 54            
 55            See CMPIR/tools/README for creating remote namespaces.
 56            
 57            Installation instructions:
 58            --------------------------
 59            
 60            1) Use the Pegasus build support to build Remote CMPI.
 61               Export the ENABLE_REMOTE_CMPI=1 environment variable prior to issuing make.
 62            
 63            2) Update the provider registration by editing the MOF files to state that
 64               certain providers are to be driven remotely. See CMPIR/tools/README for

 65 r.kieninger 1.2    tools to modify existig registration mof files.

 66 schuur      1.1 
 67                    Remote CMPI support is automatically invoked when CIM requests are issued
 68                    against remote namspaces. See CMPIR/tools/README for defining remote namespaces.
 69                 
 70                    For testing purposes we recommend to use the SBLM base provider suite,
 71                    see http://www-124.ibm.com/sblim/ for details.
 72                 
 73                    Use the following CMPIR/tools commands to prepare the remote CMPI facilites:
 74                 
 75                         sh CreateExtNs.sh -n root/local -p root/cimv2 -l localhost
 76                 
 77                    This will create a shared read-only remote namespace.
 78                 
 79                 	sh AppendNs.sh root/local $SBLIM_HOME/cmpi-base/mof/Linux_BaseRegistration.mof
 80                 	    > new-Linux_base.mof
 81                 
 82                    Use the new-Linux_base.mof file to register the sblim base providers.
 83                 

 84 venkat.puvvada 1.5    CreateExtNS2 program:
 85                    
 86                            CreateExtNS2 program can be used to create the remote namespaces. This program uses
 87                            CIMRepository interface directly to create the remote namespaces and remote namespce
 88                            creation is independent of underlying persistence store. Unlike other RCMPI 
 89                            tools/programs/libraries this program uses pegasus libraries. However dynamic creation
 90                            of remote namespaces are not supported.    
 91                    

 92 schuur         1.1 2) Install the Remode CMPI Daemon at the remote location. For the moment only
 93                       Linux systems are supported as remote locations. Copy the following files
 94                       to the remote system:
 95                    
 96                          $PEGASUS_HOME/bin/CMPIRDaemn
 97                          $PEGASUS_HOME/lib/libCMPIRNative.so
 98                          $PEGASUS_HOME/lib/libCMPIRTCPCommRemote.so
 99                    
100                       Copy required CMPI style providers to the remote location(s) as well.
101                    
102                       Setup the PATH and LD_LIBRARY_PATH environment variable accordingly.
103                    
104                    3) Start CMPIRDaemon at the remote location(s) by issuing CMPIRDaemon at a comand
105                       line prompt. Remote CMPI uses port 9001.
106                    
107                    4) Issue requests against CIMOM to see if its working, for example
108                    

109 thilo.boehm    1.4         cimcli -n root/local ni Linux_ComputerSystem

110 schuur         1.1 
111                       All commands against root/local will be routed to the CMPIRDaemon.
112                    
113                    
114                    Debugging:
115                    ----------
116                    
117                    To enable debugging output export RCMPI_DEBUG with one of the following values:
118                    - critical
119                    - normal
120                    - info
121                    - verbose
122                    
123                    This should give you detailed description about the actions performed within
124                    remote CMPI, both for the daemon process and the CIMOM.
125                    
126                    
127                    -----------------------------------------------------------------------------
128                    Origial Author: Frank Scheffler (frank.scheffler@gmx.net)
129                    Modified by Adrian Schuur (schuur@de.ibm.com)