(file) Return to readme.txt CVS log (file) (dir) Up to [Pegasus] / pegasus / Attic

Diff for /pegasus/Attic/readme.txt between version 1.10.6.1 and 1.15.2.1

version 1.10.6.1, 2003/08/13 19:39:49 version 1.15.2.1, 2004/01/16 16:50:18
Line 6 
Line 6 
 Tagline: OpenPegasus is an object manager for DMTF CIM objects written in C++ Tagline: OpenPegasus is an object manager for DMTF CIM objects written in C++
          and supported by The Open Group          and supported by The Open Group
  
 STATUS: Revised June 2003 to match Pegasus release 2.2  STATUS: Revised October 2003 to match Pegasus release 2.3
   
   NOTE: Obsolete. See readme.html
 Contents: Contents:
 ========= =========
  
Line 26 
Line 28 
 14. Development with Pegasus and Pegasus Tools 14. Development with Pegasus and Pegasus Tools
 15. Commands 15. Commands
 16. Creating SSL certifications. 16. Creating SSL certifications.
 17. Documentation  17. Testing with ICU enabled
 18. Participate  18. Documentation
   19. Participate
  
  
  
Line 157 
Line 160 
  
 1.  GNUMAKE - To simplify the building of Pegasus across multiple platforms we 1.  GNUMAKE - To simplify the building of Pegasus across multiple platforms we
     have standardized on a set of build tools including: GNUMAKE. We are using     have standardized on a set of build tools including: GNUMAKE. We are using
     GNUMAKE 4.79.1 successfully both in Windows and Linux environments.      GNUMAKE 3.79.1 successfully both in Windows and Linux environments.
  
     GNUMAKE is available from     GNUMAKE is available from
  
Line 214 
Line 217 
     DevManual               Source and build files for developers' manual     DevManual               Source and build files for developers' manual
     mak                     General make files (used by other makes)     mak                     General make files (used by other makes)
     src                     All Pegasus Source Files     src                     All Pegasus Source Files
         ACEExample          Test directrory with examples of the use of ACE          ACEExample          Test directrory with examples of the use of ACE (obsolete).
         Clients             Source for various test clients and client SDK         Clients             Source for various test clients and client SDK
             CGICLIENT       Pegasus test client that uses a WEB browser             CGICLIENT       Pegasus test client that uses a WEB browser
           JAVA                Java Client support modules
         Pegasus         Pegasus
             Client          Pegasus Client API Tests             Client          Pegasus Client API Tests
                 depends                 depends
                 tests                 tests
             Common          Pegasus Common Functions (C++ source and headers             Common          Pegasus Common Functions (C++ source and headers
                 tests       Test programs for the common functions                 tests       Test programs for the common functions
               Compiler        Pegasus MOF compiler
               Config          TBD
               Consumer        TBD
               ControlProvidersImplementation of Pegasus internal providers
               ExportClient    TBD
               ExportServer    TBD
               Handler         TBD
               HandlerService  TBD
               IndicationService TBD
               Listener        TBD
             Protocol        Pegasus Client HTTP/XML Protocol Modules             Protocol        Pegasus Client HTTP/XML Protocol Modules
                 depends                 depends
             Provider        Pegasus Provider interface functions             Provider        Pegasus Provider interface functions
               ProviderManager Provider Manager service that manages providers
               ProviderManager2Pluggable Provider Manager service
             Repository      Pegasus Repository Interfaces and Simple Repository             Repository      Pegasus Repository Interfaces and Simple Repository
                 tests       Tests for Repository Functions                 tests       Tests for Repository Functions
               Security        TBD
             Server          Pegasus Server Modules             Server          Pegasus Server Modules
               WQL             TBD
         Providers           Pegasus test and required providers         Providers           Pegasus test and required providers
               generic         TBD this and following
         Utils              IndicationConsumer
               Linux
               ManaedSystem
               slp
               statistic
               sample
               testproviders
   
           Server              Pegasus executable build
           slp
           StandardIncludes
           tools               MU and other utilities written for Pegasus support
           Unsupported         Code that is made available but is not supported or included
                               in the normal make.
           WMIMapper           Pegasus implementation that implements mapping to Microsoft
                               WMI objects.
  
 Runtime Directories Runtime Directories
      $PEGASUS_HOME$         Home directory for runtime.  All compiler, linker      $PEGASUS_HOME$         Home directory for runtime.  All compiler, linker
Line 507 
Line 540 
 EMAIL="test@email.address" EMAIL="test@email.address"
 HOSTNAME=`uname -n` HOSTNAME=`uname -n`
 sed -e "s/$CN/$HOSTNAME/"  \ sed -e "s/$CN/$HOSTNAME/"  \
     -e "s/$EMAIL/root@$HOSTNAME/" $PEGASUS_ROOT/ssl.cnf \      -e "s/$EMAIL/root@$HOSTNAME/" $PEGASUS_ROOT/src/Server/ssl.cnf \
     > $PEGASUS_HOME/ssl.cnf     > $PEGASUS_HOME/ssl.cnf
 chmod 644 $PEGASUS_HOME/ssl.cnf chmod 644 $PEGASUS_HOME/ssl.cnf
 chown bin $PEGASUS_HOME/ssl.cnf chown bin $PEGASUS_HOME/ssl.cnf
Line 518 
Line 551 
    -keyout $PEGASUS_HOME/key.pem -out $PEGASUS_HOME/cert.pem    -keyout $PEGASUS_HOME/key.pem -out $PEGASUS_HOME/cert.pem
  
 cat $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem > $PEGASUS_HOME/server.pem cat $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem > $PEGASUS_HOME/server.pem
 rm $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem  
 cp $PEGASUS_HOME/cert.pem $PEGASUS_HOME/client.pem cp $PEGASUS_HOME/cert.pem $PEGASUS_HOME/client.pem
   rm $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem
   
   17. Testing with ICU enabled:
   ==============================
  
   ICU (International Compoments for Unicode) refers to the set of libraries that
   Pegasus uses to run globalized.  For example: these libraries are used to
   load messages in different languages, format currency and numbers according to
   a specific locale etc.  In order to enable globalization in Pegasus, Pegasus
   must be built with ICU enabled, ie. the right environment variables must be
   set prior to running "make". Refer to the GlobalizationHOWTO.htm in the docs
   directory for details.  That said, when users run "make poststarttests"
   to verify the integrity of a Pegasus download, a series of tests are run that
   require the cimserver to be running. These tests currently depend on specific
   messages returned from the server. When ICU is enabled, all messages come
   from the resource bundles and these usually do not match the hardcoded
   default messages within Pegasus.  These hardcoded default messages
   are what the various test programs expect in order to complete
   successfully.  If the ICU enabled server is started without
   disabling message loading from the bundles, "make poststartests" will fail.
   In order to run "make poststarttests" successfully with ICU enabled, an
   environment variable called PEGASUS_USE_DEFAULT_MESSAGES must exist prior to
   starting the server.  Once this is defined, when the cimserver starts, all
   messages generated will be the default hardcoded messages.  This will enable
   "make poststarttests" to complete successfully.  Once "make poststarttests" is
   complete, you should stop the cimserver and then undefine PEGASUS_USE_DEFAULT_MESSAGES.
   If this variable is left defined, Pegasus will not be able to load messages
   using ICU resource bundles.
  
 17. Documentation:  18. Documentation:
 =================== ===================
  
 The documentation is currently in preperation. The preliminary documentation The documentation is currently in preperation. The preliminary documentation
Line 536 
Line 595 
 design documentation. design documentation.
  
  
 18. Participate!  19. Participate!
 ================= =================
  
 We are looking for people who want to join the Pegasus work group and We are looking for people who want to join the Pegasus work group and


Legend:
Removed from v.1.10.6.1  
changed lines
  Added in v.1.15.2.1

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2